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

I2288

A task is on the mesh while it works

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
1
Waiting on
I2734
Holds back
I2289
Behind it in all
2
Evidence
0 of 1
In the waySubjectDetail
issueI2734I2734 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 I2288

majordomus plan verify I2288

majordomus plan done I2288

What it is

Objective
majordomus start claims the task's scope on the checkout's running server as an advisory claim of the mesh session task-<id>, with the task's title as intent and its issue, and keeps the key on the task record; finish closes that session.
Why
The owner asked on 2026-10-10, and again on 2026-10-15, that every LLM session use the mesh automatically. A task's scope lived in the checkout's task record and on this machine's board; another machine saw it only if the worker remembered to claim it. The 2026-10-10 implementation (branch feature/a-task-is-on-the-mesh) never reached a pull request; this is its port onto master, after I2734 put the provider session itself on the mesh.
Now
majordomus start reports overlaps with the local board and claims nothing on the mesh.
Wanted
After majordomus start the task's scope is an advisory claim of task-<id> on every linked runtime; after finish the session is closed and its claims end with it; with no server or no running mesh nothing is claimed and nothing fails.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • After majordomus start the task's scope is a live claim on every linked runtime
  • After finish the claim is released
  • Without a server start records no claim and does not fail
Validation
bin/majordomus plan validatebash test/run.sh 3067_a_task_is_claimed_on_the_mesh 04_start_check 06_finish
Evidence required
case_3067
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
lib/common.shlib/start.shlib/finish.shtest/cases/3067_a_task_is_claimed_on_the_mesh.shdocs/MESH.md
Not
unknown: the record declares no `non_scope`
Depends on
I2734
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.