Skip to content

Coordination

Every worker declares the paths it will touch, sees who else is working and where, and hears about a collision before it is committed.

The failure it answers

Agents collide. Parallel workers edit the same paths, or build the same thing twice, without knowing about each other.

Several workers on one repository at once: the scope a task claims, the board every attached session announces itself on, the worktree each branch lives in, the plan whose status is derived rather than stored, the machines that share one repository, and the models and advisors a worker is routed to. A claim is information and a collision is reported; what refuses a change is the task's own scope, at check and at finish.

Not in this domain: what the work must satisfy, which is governance; and when it counts as finished, 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.

  • Coordination

    Every worker declares the paths it may touch, every session can see who else is attached and what they announced, and a collision is reported before it is committed.

    5 of 5 claims guaranteed with a named test · 2 use cases

  • Worktrees

    A branch's worktree is where git says it is, never where somebody chose to put it, and a misplaced one is a diagnostic with a remedy rather than a mystery.

    3 of 3 claims guaranteed with a named test · 2 use cases

  • Mesh

    Majordomus runtimes of one repository — on one machine or several — discover each other, link through a signed handshake, and share sessions, claims, handovers and reviews through one replicated journal that survives disconnects, crashes and partitions.

    9 of 9 claims guaranteed with a named test

  • Models

    One declared catalogue of vendors and models — capabilities, context, lifecycle, no fabricated facts — and a routing answer that names why every candidate was chosen or excluded.

    3 of 3 claims guaranteed with a named test

  • Reasoning

    Material uncertainty becomes an evidence-backed decision — reviewed by whichever optional advisors are available, decided locally when none are, and carried to the next session as a record.

    7 of 7 claims guaranteed with a named test

  • Planning

    An issue records what happened to it and the engine derives whether it is blocked, ready, active, verifying or done from the dependency graph, so the roadmap cannot disagree with the plan.

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

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 (17)

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.

41 claims, 40 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.