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

I2709

A red on the trunk has one named carrier, and nobody else may land until it is paid

Where it stands

devtask.issue

Readiness: ready no dependency and no gate holds it; nobody has started it
Status: READY
Can start: startable
Milestone: M004
Milestone status: ACTIVE
Wave: 1
Waiting on: none
Holds back: none
Behind it in all: 0
Evidence: 0 of 1

Moves

plan.transition

What it is

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.
Now: 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.
Wanted: 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.
Done when: unknown: the record declares no `completion`
Risk: unknown: the record declares no `risk`

Acceptance

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 present: unknown: the record carries no `evidence` entries

Scope

Touches: apps/majordomus-cli/src/meshapps/majordomus-cli/src/capability/builtindocs/INTEGRATION.md.ai/repo/rules/project/an-expedited-landing-is-the-owners-word.v1.mdtest/cases
Not: Cancelling runs, which I2664 delivered
Depends on: I2664
Priority: p1
Profile: implementation
Parallel safe: true
Owner: unknown: the record declares no `owner`

The work so far

Branches: none
Merged: none
Commits: 0
Trunk: master
Sessions: none
Created: 2026-10-14
Updated: 2026-10-14
Started: unknown: the record declares no `started_at`
Verified: unknown: the record declares no `verified_at`
Completed: unknown: the record declares no `completed_at`

Synchronisation

Adapter: scripts/github-sync
Repository: unknown: the derived plan's header carries no repository
External issue: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.