Skip to content

The Cockpit shows every intent with its derived stage at /cockpit/intents, and one intent's criteria, evidence, serving issues and realising work at /cockpit/intents/<id>

The intent model has a view in the Cockpit. /cockpit/intents lists every intent with its stage, the criteria with current evidence, the providers realising it and its findings. /cockpit/intents/<id> shows one intent: each criterion with its evidence state, linked to the test object it names and to the issues serving it, the command that reproduces it, and every unit of work realising it with the provenance of its link.

declared statusdeclared status: guaranteed Declared deterministic and blocking, implemented, and naming the behavioural test that is to prove it. Whether a recorded run supports it is the evidence verdict, shown beside it.

recorded evidencerecorded evidence: stale Declared guaranteed, and not supported by a recorded run: the test is named, and no passing run of the current inputs is recorded. how evidence is recorded

Both pages render the intent-realization capabilities and decide nothing themselves. Each criterion links the test object it names and the issue serving it, the realising work carries its providers and the provenance of its link, and an intent the repository does not hold is a 404.

What it means

The intent model has a view in the Cockpit. /cockpit/intents lists every intent with its stage, the criteria with current evidence, the providers realising it and its findings. /cockpit/intents/<id> shows one intent: each criterion with its evidence state, linked to the test object it names and to the issues serving it, the command that reproduces it, and every unit of work realising it with the provenance of its link.

How it works

apps/majordomus-cli/src/cockpit/intents.rs renders the intent_realization capabilities and decides nothing itself, so the pages cannot disagree with majordomus intent realization or intent explain. An intent the repository does not hold is a 404.

How to see it

majordomus serve          # then open /cockpit/intents

What it does not cover

The pages read; they change nothing. Writing an intent, a gap or a critique stays a file edit.

Why it exists

A derivation that only a command line can show is one a reviewer does not look at. The page puts the criterion, its test and the work beside each other, one click from each.

Detail rendered from docs/claims/intent-cockpit-pages.md.

From the statement to the proof

  1. 1 · the public statement

    The Cockpit shows every intent with its derived stage at /cockpit/intents, and one intent's criteria, evidence, serving issues and realising work at /cockpit/intents/<id>

    Made on Planning, Plan.

  2. 2 · the canonical claim

    intent-cockpit-pagesdeclared status: guaranteed in docs/CLAIMS.yaml

    Defined in read it on this site · docs/COCKPIT.md

  3. 3 · the implementation

    apps/majordomus-cli/src/cockpit/intents.rs

  4. 4 · the test and the scenarios

    Test: apps/majordomus-cli/tests/intent_realization.rs

  5. 5 · the recorded runs

    recorded evidence: stale how evidence is recorded

Verify it yourself

The test runs in a disposable temporary repository and asserts the behaviour, not a string in the source.

from a clone of the repository
bash test/run.sh apps/majordomus-cli/tests/intent_realization.rs

Where this claim is used

responsibilities it covers

Searches the titles and descriptions of every page this site publishes.