I2289 — A task built off the mesh is refused

○READY wave 2 · p0 · implementation profile · runs alone

Part of every-session-joins-the-mesh — Every LLM session joins the Majordomus mesh at start, told the mesh as work.

Objective

Rule majordomus.task-on-the-mesh, dispatched by check and finish: on a repository whose tracked mesh declaration is enabled, a completed finish of a task whose scope was never claimed on the mesh is refused and recorded; finish claims the scope again before it judges; partial and the other outcomes are not refused.

Why

The owner asked on 2026-10-10, and again on 2026-10-15, why taking part in the mesh is not enforced. After I2734 and I2288 a session and a task reach the mesh when a server answers; nothing made a missing claim a finding, so a task started with no server stayed invisible to every other machine and was completed as if it had not been.

Current state

No validator reads mesh_claim; finish completes a task whose scope was never on the mesh.

Desired state

check reports an unclaimed scope on an enabled mesh under mesh; finish --outcome completed refuses it with task.refused naming majordomus.task-on-the-mesh; finish re-claims first; a repository with no enabled mesh is not judged.

Scope

• lib/common.sh
• lib/finish.sh
• share/standard/majordomus/rules/task-on-the-mesh.v1.md
• share/standard/majordomus/manifest.yaml
• .ai/repo/rules/vendor/majordomus
• test/cases/3068_a_task_off_the_mesh_is_refused.sh
• docs/MESH.md

Dependencies

• I2288✓DONE A task is on the mesh while it works

What waits on this

• I2735✕BLOCKED An edit no claim covers is refused

Acceptance criteria

• finish refuses a task whose scope was never claimed while the mesh was enabled
• A disabled mesh refuses nothing
• partial is not refused for the mesh
• finish claims the scope once a server answers, and the rule passes

Validation

• bin/majordomus plan validate
• bash test/run.sh 3068_a_task_off_the_mesh_is_refused 3067_a_task_is_claimed_on_the_mesh 18_doctrine_wiring 3022_the_rule_package_is_stamped_and_adopter_neutral

Evidence required

• case_3068

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