Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I1105

The repository is discovered once, into one model

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
two-folder-integration
Milestone status
ACTIVE
Wave
1
Waiting on
I1101
Holds back
I1106
Behind it in all
18
Evidence
0 of 2
In the waySubjectDetail
issueI1101I1101 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I1105

majordomus plan verify I1105

majordomus plan done I1105

What it is

Objective
Build the one typed model of a repository — identity, structure, capabilities, the layer's registries, workflows, environments, providers, services and version-control state — discovered once and read by every consumer.
Why
The CLI, the environment entry, the documentation and the server each discover the repository their own way today, which is four answers to one question and four places to fix when it is wrong. One model is the spine the rest of this milestone hangs from.
Now
An index of the layer exists and a capability registry exists. Repository facts beyond them — the environment, the providers, the workspace, the services — are read where they are needed, each time.
Wanted
One discovery produces one typed value; consumers hold it rather than the filesystem.
Done when
unknown: the record declares no `completion`
Risk
A model that knows everything is discovered slowly, and the environment entry pays that cost on every directory change. Its cost is measured in the same issue that makes it mandatory, not later.

Acceptance

  • One typed value carries what a consumer needs to know about a repository, composed from the registries that already own their parts
  • Discovery happens once per process, and a second consumer pays nothing for it
  • Nothing in the model requires a configuration file to state what inspection can establish
  • No consumer reads the filesystem for a fact the model already carries, proved by a check rather than by review
Validation
cargo test --workspace --all-featuresmajordomus perf
Evidence required
one_modeldiscovered_once
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
apps/majordomus-cli/src/repository.rsapps/majordomus-cli/src/discovery
Not
A second index beside the one that exists; this composes itDiscovery that reaches the network or builds anything
Depends on
I1101
Priority
p0
Profile
deep-work
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-06
Updated
2026-09-06
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.