Skip to content

Governance

The rules are written once, in the repository, projected into every tool's instructions, and a blocking rule stops the command instead of advising it.

The failure it answers

Rules drift. Each tool keeps its own instruction file, and a rule nobody wired into enforcement is only a suggestion.

What must hold while work is done: the one policy every provider's instruction file is generated from, the rules and the doctrine that says which of them a machine decides and enforces, and the commit policy every message is judged against. A rule is blocking or advisory, and the difference is a fact the tool reports rather than a word in a document.

Not in this domain: what proves a statement about the product, which is evidence; and the contract a task is finished against, which is completion.

The features filed under it

Each feature names this domain in its own file; the domain lists none of them. A feature added with this domain is on this page at the next build, and one removed is gone.

  • Doctrine

    A rule is enforced when a validator decides it, a command runs it, a test proves it and CI blocks on it; anything less is documentation, and the tool knows the difference.

    12 of 12 claims guaranteed with a named test · 4 use cases

  • Policy

    Every provider the tool declares — an agent, an orchestrator that runs agents, any tool that reads AGENTS.md — gets the same rules from the same place, because their instruction files are generated from one policy and never written by hand; the providers are the table in docs/generated/providers.md.

    10 of 14 claims guaranteed with a named test · 3 use cases

  • Commits

    The commit message has one grammar, one policy and one verdict; the scope it is written under is learned from the repository's own history rather than kept in a table, and a message that does not satisfy the policy is refused while it is still being written.

    3 of 3 claims guaranteed with a named test · 1 use case

The failure modes its features answer

Operational moments from the Why catalogue that name a rule, a command, a capability or a claim of a feature in this domain. Nothing here was assigned.

Every failure mode it answers (33)

What is claimed

Every claim a feature of this domain names, once, with the status it declares — guaranteed, advisory, planned or rejected — and the test that settles it. Whether a recorded run supports a claim is its own page's verdict.

29 claims, 25 guaranteed with a named test

Executable use cases

Scenarios the tool runs against itself every time this site is built.

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