Skip to content
Cockpit0.29.0
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

I2289

A task built off the mesh is refused

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
every-session-joins-the-mesh
Milestone status
PLANNED
Wave
2
Waiting on
I2288
Holds back
I2735
Behind it in all
1
Evidence
0 of 1
In the waySubjectDetail
issueI2288I2288 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2289

majordomus plan verify I2289

majordomus plan done I2289

What it is

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.
Now
No validator reads mesh_claim; finish completes a task whose scope was never on the mesh.
Wanted
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.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

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

Scope

Touches
lib/common.shlib/finish.shshare/standard/majordomus/rules/task-on-the-mesh.v1.mdshare/standard/majordomus/manifest.yaml.ai/repo/rules/vendor/majordomustest/cases/3068_a_task_off_the_mesh_is_refused.shdocs/MESH.md
Not
unknown: the record declares no `non_scope`
Depends on
I2288
Priority
p0
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-10
Updated
2026-10-15
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.