I4005 — Proceed.step answers one idempotent work order

✕BLOCKED wave 3 · p1 · implementation profile · runs alone

Part of a-session-proceeds-through-the-mesh — A session proceeds through the mesh: it finds the work, claims it once, runs it watched and stops when the intent is met.

Objective

proceed.step derives one step from intent_realization and the claim-aware plan.next into a work order (do, fan_out, report, next_due_at); the /proceed skill is generated from its .skill() declaration. It builds on the pushed stack feature/proceed-names-the-next-admissible-work (I2972-I2976, I3040, ADR 0177) and writes no second body.

Why

/proceed names work but does not claim it, fan it out, report it or schedule the next step, and a hand-written skill drifts from the capability.

Current state

Not built: this issue is planned by the milestone a-session-proceeds-through-the-mesh and nothing of it exists.

Desired state

The acceptance criteria below hold and case 4005 proves them.

Scope

• apps/majordomus-cli/src/capability/builtin
• share/skills
• docs/PROCEED.md
• test/cases/4005_proceed_step_is_one_idempotent_work_order.sh
• .ai/repo/project/issues/I4005.yaml

Dependencies

• I4003✕BLOCKED Devtask.implement runs readiness, preflight, claim, worktree and one execution

What waits on this

• I4009✕BLOCKED /watchdog reads liveness and runs wake, handover, reap

Acceptance criteria

• Repeating the step at the same state answers the same work order
• An intent whose realisation is met answers done and schedules nothing (it-stops-when-the-intent-is-met)
• The /proceed skill of every provider is generated and a hand edit fails generate --check
• The stack I2972-I2976 and I3040 is extended, not duplicated

Validation

• env -u MAJORDOMUS_SHARE -u MAJORDOMUS_HTTP_HOST -u MJ_ROOT bash test/run.sh 4005_proceed_step_is_one_idempotent_work_order

Evidence required

• case_4005_proceed_step_is_one_idempotent_work_order

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