shapeup-sdlc-plugin AGENTS.md

Shape Up SDLC Local Harness

Enforcement model

A three-phase Shape Up loop orchestrated by /tech-lead. Invariants live in the runtime, not this file — expect hook denials, not arguments.

Skills and commands are named short throughout this file; every one of them resolves only under the plugin's namespace — Skill(shapeup-sdlc-plugin:orient), /shapeup-sdlc-plugin:ship. A bare name is not a typo you get a warning for: an unknown skill name is rejected upstream of the hook layer, so the dispatch fires no hook, leaves no decision row, and is answered by improvisation.

• Hook-denied: dispatching a worker without a schema-valid WorkOrder, writing outside the scope's substrate, stopping a run with no receipt (the run's first act writes one).
• Attested, not assumed: a dispatch leaves a receipt naming the skill that ran, and ingest refuses an orchestrated result that has none. A dispatch that fails is answered by the sub-agent improvising the craft, which every other check accepts — so "the artifact exists" is not evidence that the shipped skill produced it. --no-receipt-check is the way through when the receipt channel itself fails.
• GATE L2 is advisory — warns when EVAL runs over unfinished tasks, permits the call (per-machine board, operator asked; ADR-0001) — a signal, not a bug.
• Sign-off is a file: each gate resolves from the answer set (ci/guarded/interactive) — cross, stop for the PO, or abort; the decision's source is ledgered.
• Your scope cut decides your concurrency, not the dial. Two scopes that both declare a write to one path never build at the same time: shared substrate is the sanctioned escape from disjointness, and an edit is read-modify-write, so concurrent writers silently drop each other's work. An entry point listed as writable by five scopes therefore builds five scopes one at a time whatever --parallel-scopes says. The run states the ceiling its contracts actually permit before dispatching anything, as a BUILD-order line — a peak below that ceiling is a dispatch problem, a ceiling below the dial is a scope-cut problem, and only the second is fixable by re-cutting. The fix is a cut where exactly one scope owns each entry point. Note the ceiling is narrated, not gated: it does not travel in the ⏸ L1b block, so an unattended run carries it only in its log.
• The build+eval loop breaks only three ways ✦: EVAL PASS → QA → Ship; outer round_budget exhausted; opt-in wall_clock_budget_s tripped (the wall-clock axis event counters miss). Budget trips route to GATE H — ship what's green, never kill the run from outside. A scope exhausting its per-scope attempt_budget (T0 attempts) queues a GATE H proposal, never blocks the round.