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

I2703

The mesh cooperation rule lists the hello checks in the order the code runs them, and a test names that order

Where it stands

devtask.issue

Readiness: blocked 1 of its dependencies is not DONE
Status: BLOCKED
Can start: not now
Milestone: runtime-trust
Milestone status: ACTIVE
Wave: 1
Waiting on: I2132
Holds back: none
Behind it in all: 0
Evidence: 0 of 1

In the way	Subject	Detail
issue	`I2132`	I2132 is not DONE

Moves

plan.transition

What it is

Objective: Bring rule project.mesh-cooperation-is-authenticated to the check order accept_hello runs, with the nonce cache last and the recipient check before it, as a new version of the blocking rule, and hold the code to it with a test.
Why: Split from I2132 on 2026-10-14. I2132 bound each hello to its recipient and made docs/MESH.md state the order the code checks in, and its desired_state said 'Not done here' of the rule, which still lists the nonce fourth; correcting it is a version bump of a blocking rule that scripts/ci/mesh-check and case 301 name by file. Its acceptance criteria still required rule and code to agree, so it could never close. Baseline audit of 2026-10-09 at master 1fb8d6be44, mesh drift 1.
Now: .ai/repo/rules/project/mesh-cooperation-is-authenticated.v1.md says the answerer verifies 'in order' signature, timestamp, nonce, protocol, self, repository, trust, and has no recipient check. docs/MESH.md lists the ten checks in the code's order, with the recipient (misaddressed) seventh and the nonce cache last, while its diagram still reads 'signature · freshness · nonce · protocol · self · repository · trust'. scripts/ci/mesh-check and test/cases/301_the_mesh_stays_one_subsystem.sh name the v1 rule file. No test names the order Cooperation::accept_hello (apps/majordomus-cli/src/mesh/cooperation.rs) checks in.
Wanted: A new version of the rule states the order accept_hello checks in, the recipient check included and the nonce cache last with its reason; scripts/ci/mesh-check, case 301 and the docs/MESH.md diagram follow the new version; a test sends hellos that fail two checks at once and asserts the refusal of the earlier one, for each adjacent pair the rule orders.
Done when: unknown: the record declares no `completion`
Risk: unknown: the record declares no `risk`

Acceptance

The rule's check order and the code's check order are the same, and a test names the order

Validation: bin/majordomus plan validatecargo test --lib mesh::cooperationscripts/ci/mesh-checkMJ_TEST_JOBS=4 bash test/run.sh 301_the_mesh_stays_one_subsystem
Evidence required: hello_check_order_test
Evidence present: unknown: the record carries no `evidence` entries

Scope

Touches: .ai/repo/rules/projectscripts/ci/mesh-checktest/cases/301_the_mesh_stays_one_subsystem.shapps/majordomus-cli/src/mesh/cooperation.rsapps/majordomus-cli/tests/mesh_cooperation.rsdocs/MESH.md
Not: The recipient field of a hello and the misaddressed refusal, which I2132 delivered
Depends on: I2132
Priority: p1
Profile: implementation
Parallel safe: false
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.