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

I1026

The architecture explains itself, from inside itself

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
capability-graph
Milestone status
ACTIVE
Wave
4
Waiting on
I1012
Holds back
I1030
Behind it in all
1
Evidence
0 of 2
In the waySubjectDetail
issueI1012I1012 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 I1026

majordomus plan verify I1026

majordomus plan done I1026

What it is

Objective
Document the graph, its sources, its relation model, its two projections and the contributor workflow, and let the interface say how it was generated and from what.
Why
The whole promise is that a contributor registers a capability in one place and everything follows. That promise is only usable if the one place is written down, and the interface itself is the most reliable location for its own provenance.
Now
The Cockpit has a document. The composed graph, the relation model and the contributor workflow have none.
Wanted
One architecture document, reachable from the places a reader starts, and an interface that states its own mode, sources and revision.
Done when
unknown: the record declares no `completion`
Risk
A document explaining a derivation goes stale faster than the derivation. Every value it states about the current repository is generated rather than typed.

Acceptance

  • The document explains the sources, the relation model, both projections, the conditional exposure of runtime surfaces, how a new capability appears without an edit, the rules, the skill and how to debug a missing node
  • The interface states its own mode, its sources, its schema version and its build revision from safe metadata
  • It is reachable from the root document, the architecture documents and the interface itself, through existing cross-linking rather than a hand-written list
  • Any new directory this milestone creates carries its context document per the directory contract
Validation
bash test/run.shbin/majordomus doctor
Evidence required
architecture_documentedself_documenting
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
docs/COCKPIT.md
Not
Duplicating the ADR's reasoning in proseRepeating full instructions in every directory document instead of composing them
Depends on
I1012I1025
Priority
p1
Profile
implementation
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.