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
claim
247 of the 247 object(s) of kind claim. Each has an address of its own, derived from its identity.
| Identity | Title | Source |
|---|---|---|
| a-candidate-is-routed-by-what-it-is-about | Every candidate derived from an observation carries a route — platform, enforcement, generator, documentation or project — derived from its subject's structure and never from its wording, and in a repository that adopted the tool its own share/ routes project | docs/CLAIMS.yaml |
| a-diagram-is-named-linked-and-addressable | Every Mermaid diagram of the built site gets an id (diagram-<name>), the list of its nodes, the viewer's controls and a link for each node that is the identity of an object the site has a page for, all derived at build; a link to | docs/CLAIMS.yaml |
| a-finding-names-how-to-see-it-again | Every finding a command reports names the command that reproduces it | docs/CLAIMS.yaml |
| a-session-records-what-it-observed | knowledge observe records one observation.recorded ledger line with its kind, subject, statement and typed evidence references, inside an open episode, inside a task or outside one, and refuses any other shape, or the absence of an episode, without writing | docs/CLAIMS.yaml |
| a-skipped-case-is-not-a-proof | A test case that declines to run is reported as a skip and recorded as one, so the evidence ledger can never read a case that asserted nothing as the proof of the claim it names | docs/CLAIMS.yaml |
| adr-catalogue | An architecture decision is one file under the layer's adrs section, validated against the decision contract, with an identity nothing else claims, reciprocal supersession, and every reference it makes resolving | docs/CLAIMS.yaml |
| adr-propose | majordomus adr propose writes a decision with status proposed and refuses to write any other status, allocates its identity under a lock so concurrent workers never collide, and records what the decision was derived from | docs/CLAIMS.yaml |
| adr-traceability | A decision states what it put in force as typed references, each one validated, and the reverse direction — what a rule, a document, an implementation or a case was decided by — is read from the knowledge graph rather than written down a second time | docs/CLAIMS.yaml |
| advertised-install-command-works | The install command this project advertises is fetched and run from the published site every night and on request, and the run that asked for it is red while it does not install a working tool | docs/CLAIMS.yaml |
| advice-is-weighed-not-counted | Advisors that disagree never decide by count: a conclusion is refused while a disagreement on its assessment is unsettled, a resolution needs evidence, and every answer received must be weighed | docs/CLAIMS.yaml |
| advisor-failure-is-recorded-and-recovers | An advisor that times out, is rate limited, refuses its credential or answers malformed is recorded as exactly that, never blocks the work, opens a circuit that closes again after its cooldown, and never fails the session | docs/CLAIMS.yaml |
| advisor-transports-share-one-contract | Every advisor transport is held to one contract — typed failures, deadlines, cancellation, normalised answers, reported usage, redacted secrets — proven against fakes with no network, model or credential | docs/CLAIMS.yaml |
| advisors-are-declared-once | Advisors are declared once, in share/advisors.yaml, by reference to the provider table and the model catalogue; a new advisor reaches the command line, the policy, HTTP, OpenAPI, MCP and the Cockpit with no consumer edited | docs/CLAIMS.yaml |
| ai-layer-manifest | The repository's AI layer is one directory whose manifest names every section, readable without the tool | docs/CLAIMS.yaml |
| an-observation-becomes-a-grouped-candidate | Each observation an episode recorded becomes, at that episode's end and with no model, a candidate of its own that says what it is about, and knowledge candidates groups the records about one subject with the episodes behind them; an episode that observed nothing records that it found nothing | docs/CLAIMS.yaml |
| archive-fidelity | An archive that lost the file modes fails rather than travelling | docs/CLAIMS.yaml |
| authored-files-are-english | Every authored file in this repository is spelled in English, and a proper noun, a test fixture or a published translation that is not carries its reason beside the check | docs/CLAIMS.yaml |
| benchmark-coverage-derived | Every externally callable operation of the Rust executable is a benchmark target with a denominator generated from the registry, and a missing case fails the structural check | docs/CLAIMS.yaml |
| blocker-store | An entry in the questions store that does not parse blocks acceptance exactly as an unresolved question does | docs/CLAIMS.yaml |
| blocker-survives-handover | A blocking question keeps blocking after the work is handed to a new task | docs/CLAIMS.yaml |
| bootstrap-chain | Provider instruction files are thin bootstraps that point at the AI layer and carry no rule of their own | docs/CLAIMS.yaml |
| briefing-names-candidates | The start briefing names the candidates awaiting review on this branch, count and ids, bounded and within the briefing budget, and prints their absence rather than omitting it | docs/CLAIMS.yaml |
| candidates-reviewed-not-accumulated | More candidates than the policy cap, or a candidate older than the policy age, is an advisory doctor finding that names them; both numbers are declared once in the policy | docs/CLAIMS.yaml |
| capability-class | A profile names a capability class rather than a vendor model | docs/CLAIMS.yaml |
| capability-modules | A capability of the Rust executable is declared once and composed into its module, the root composes modules, and the registry refuses a capability outside its module's namespace | docs/CLAIMS.yaml |
| capability-registry | Every capability of the Rust executable is defined once, and the registry refuses a duplicate id or a colliding projection name, naming both parties | docs/CLAIMS.yaml |
| catalogue-resolves | A use case or application cannot name a command, doctrine or claim that does not exist, and the two catalogues cannot disagree about which applies to which | docs/CLAIMS.yaml |
| checkpoint-interval | A profile sets how often a worker should checkpoint, and a stale task is reported | docs/CLAIMS.yaml |
| checkpoint-record | A checkpoint is a capped progress record with computed identity, and a body over the cap is refused rather than truncated | docs/CLAIMS.yaml |
| ci-planned-gates | A change runs the gates its paths can affect, decided by one model of what affects what, and a change to the pipeline itself or a path the model does not know runs every gate | docs/CLAIMS.yaml |
| ci-verdict | The verdict status is green only when planning succeeded and every gate the plan selected ran in a job that succeeded; a failed or cancelled job, a selected gate whose job was skipped, or a plan that selected nothing is red | docs/CLAIMS.yaml |
| ci-verdict-is-required | No pull request can be merged into the default branch while the verdict status is red, because a branch rule requires it | docs/CLAIMS.yaml |
| cli-documentation-executable | Every command of the Rust executable's command line carries a summary, help on every argument and, where it runs, at least one example, the root carries a long description, and every example shown to a reader is executed against the built executable | docs/CLAIMS.yaml |
| cockpit-is-a-projection-of-the-registry | A capability added to the registry appears in the Cockpit's listing, navigation and search and on a page of its own with a form generated from its schema, without one line of the Cockpit being edited | docs/CLAIMS.yaml |
| command-coverage | Every public command has a behavioural test and a negative test, computed rather than remembered | docs/CLAIMS.yaml |
| command-surface | The public command surface is declared, and reconciled against the dispatcher | docs/CLAIMS.yaml |
| commit-message-is-judged | A commit message that does not satisfy the repository's declared commit policy is refused at the moment it is written, and the history's existing debt is recorded and may not grow | docs/CLAIMS.yaml |
| commit-plan-is-refusable | A commit plan carries a fingerprint of the repository, the worktree, HEAD and the exact change set it was derived from, so a plan acted on after the tree moved is refused with the reason rather than applied | docs/CLAIMS.yaml |
| commit-scopes-are-learned | The scope vocabulary a commit is judged against is learned from this repository's own history rather than kept in a table, so a subsystem committed today is in the vocabulary today and a scope outside it is a warning rather than a refusal | docs/CLAIMS.yaml |
| connection-episode | A client with no provider hooks gets an execution episode from the MCP connection, resumes its own after a crash, and never has its prompt claimed to be captured | docs/CLAIMS.yaml |
| consistency-check | check reports whether state, scope, blockers and checkpoint age are consistent right now | docs/CLAIMS.yaml |
| context-assembly | The context a worker is given is assembled from durable state in authority order, and what a profile excludes is excluded | docs/CLAIMS.yaml |
| context-budget | The always-loaded instruction file has a line budget with a failing check | docs/CLAIMS.yaml |
| context-coverage | Every directory of the layer carries a context document, the exemption is declared by the contract that governs the subtree, and a descendant may narrow that requirement but never weaken it | docs/CLAIMS.yaml |
| context-documents | The context that applies to a path is composed from the layer's scoped documents, root to target, in one deterministic order with provenance, and a tree that does not validate resolves nothing | docs/CLAIMS.yaml |
| context-impact | The impact of a change set on the scoped context is reported from git — the documents, the scopes below them, moves with their ancestry, tracked sources to review, and stale projections — and an unrelated change reports nothing | docs/CLAIMS.yaml |
| context-selection-budget | The assembled context obeys a line budget, and every section it drops is named with its reason | docs/CLAIMS.yaml |
| context-selection-counted | What the context compiler selects, out of what it judged relevant, is counted in tokens of a named tokenizer and recorded, never estimated | docs/CLAIMS.yaml |
| continuity-reachable | Every continuity store is proven reachable through its own command, not merely present on disk | docs/CLAIMS.yaml |
| cost-per-outcome | Cost per accepted outcome will be reported from measured data only | docs/CLAIMS.yaml |