I2709 — A red on the trunk has one named carrier, and nobody else may land until it is paid
Make the trunk's red the first thing every lander knows about and the one thing that may land: a carrier is named on the board within the minute the red is read, and the landing claim is refused to anyone else until the fix is on master.
READY wave 1 · p1 · implementation profile · parallel safe
Part of M004 — Performance is executable evidence, and the hot path does no canonical work twice.
Ready. Every dependency is done, so majordomus plan start I2709 will be accepted.
Objective
Make the trunk's red the first thing every lander knows about and the one thing that may land: a carrier is named on the board within the minute the red is read, and the landing claim is refused to anyone else until the fix is on master.
Why
Split from I2664 on 2026-10-14: its first three criteria are delivered (a failed branch run cancels itself, the expedited-landing rule says which lanes each kind of change owes, a structure gate refuses an unnamed active skill); its fourth, about the board and the landing claim, is a different mechanism. On the night of 2026-10-13 the trunk was red three times in turn, and each time the carrier was named by hand on the board and other landings were held only because the release seat asked for it.
Current state
The landing claim is an exclusive mesh claim on campaign/majordomus-autonomous-convergence/landing; mesh.claim refuses a second exclusive claim but knows nothing of the trunk's verdict. A red on the trunk is read from the validate run by whoever looks; nothing names a carrier or holds the claim for one.
Desired state
When the trunk's validate run has a failed job, the board carries a red-trunk entry naming the failing job, the commit and its carrier once one announces it, and mesh.claim refuses the landing scope to any session but the carrier until a later trunk commit's run is green or the carrier releases it with a reason.
Scope
- apps/majordomus-cli/src/mesh
- apps/majordomus-cli/src/capability/builtin
- docs/INTEGRATION.md
- .ai/repo/rules/project/an-expedited-landing-is-the-owners-word.v1.md
- test/cases
Out of scope
- Cancelling runs, which I2664 delivered
Dependencies
What waits on this
Acceptance criteria
- A red on the trunk has a named carrier on the board within the minute it is read, and the landing claim is refused to anyone else until the fix lands
Validation
- bin/majordomus plan validate
Evidence required
- red_trunk_holds_the_landing_claim_test
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
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/I2709.yaml. Read it back with majordomus plan show I2709.