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

I1027

A synthetic capability proves the architecture instead of describing it

Where it stands

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

majordomus plan verify I1027

majordomus plan done I1027

What it is

Objective
Register a synthetic capability at its authoritative source alone, and prove it reaches the graph, the interface, the search, the navigation and the static projection with no other edit — and that omitting its required evidence fails enforcement.
Why
Every claim in this milestone reduces to one: adding something requires no edit to any surface. That is either demonstrable or it is marketing, and the demonstration is cheap.
Now
Nothing proves the loop end to end.
Wanted
One test registers a synthetic capability, generates, and asserts its appearance everywhere it should appear — and asserts the failure when its required evidence is missing.
Done when
unknown: the record declares no `completion`
Risk
A fixture that the implementation learns to recognise proves nothing. It has to be ordinary in every respect.

Acceptance

  • The capability is registered only at its authoritative source, and no surface is edited
  • After generation it appears in the graph, the interface, the search, the navigation and the static projection
  • Omitting its required documentation or verification fails enforcement with a message naming what is missing
  • Supplying the evidence makes every check pass
  • The fixture is removed afterwards, or kept only where test fixtures belong
Validation
bash test/run.sh
Evidence required
synthetic_flows_throughenforcement_fires
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
test/cases
Not
Leaving the synthetic fixture in the repository as if it were a real capabilitySpecial-casing the fixture anywhere in the implementation
Depends on
I1018I1019
Priority
p0
Profile
deep-work
Parallel safe
false
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.