I3199 — An assignment names the execution profile it needs, and a peer whose envelope does not satisfy it is refused

✕BLOCKED wave 2 · p3 · implementation profile · parallel safe

Part of mesh-peers-execute-assigned-work — Work is offered to a peer by capability under a fenced lease, and runs there as an execution.

Objective

Carry the effective profile limits (write, deploy, tests required) on an assignment, compare them with each candidate peer's declared envelope, refuse an unsatisfying peer by the missing limit, and refuse an implementer as its own verifier.

Why

The 09-20 profiles talk: roles that exist only in a prompt are roleplay; separation of duties must be runtime behaviour. runtime-adapters derives the limits (I0201-I0206). Proposed in ADR 0205 (What a runtime can do is a set of separately evidenced facts, and detection never authorises) (proposed; it carries no authority until the owner accepts it). Sources: chatgpt-majordomus:c160#3, chatgpt-majordomus:c082#10.

Current state

Verified: I0201 READY, I0202-I0206 BLOCKED (majordomus plan show, 2026-10-18); no peer envelope exists.

Desired state

assignment.offer checks the envelope; the plan surface shows the refusal.

Scope

• apps/majordomus-cli/src/mesh/cooperation.rs
• .ai/repo/profiles

Out of scope

• Choosing models

Dependencies

• I3198✕BLOCKED A peer is offered an assignment by capability under a fenced lease, and accepts or refuses it with a reason
• I0202✕BLOCKED Resolve a task's effective limits and print them as data

Acceptance criteria

• The scheduler refuses a peer that does not satisfy the profile and names why
• Implementer and verifier of one issue differ

Validation

• majordomus plan validate
• cargo test --lib mesh::cooperation

Evidence required

• test_a_profile_picks_the_peer

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/I3199.yaml. Read it back with majordomus plan show I3199.