I1027 — A synthetic capability proves the architecture instead of describing it
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.
BLOCKED wave 5 · p0 · deep-work profile · runs alone
Blocked. This issue cannot start until I1018, I1019 are done. The status is derived from that, not declared.
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.
Current state
Nothing proves the loop end to end.
Desired state
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.
Scope
- test/cases
Out of scope
- Leaving the synthetic fixture in the repository as if it were a real capability
- Special-casing the fixture anywhere in the implementation
Dependencies
- I1018BLOCKED The surface rules exist as checks, proved by making them fail
- I1019BLOCKED One skill runs the whole loop, and is itself in the graph
What waits on this
Acceptance criteria
- 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_through
- enforcement_fires
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Risk
A fixture that the implementation learns to recognise proves nothing. It has to be ordinary in every respect.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I1027.yaml. Read it back with majordomus plan show I1027.