@warnyin/sdlc 0.1.2 → 0.2.0

package/payload/playbook/context.md

@@ -1,26 +1,26 @@
-# Context engineering
-
-Six context types: instructions, knowledge, memory, examples, tools, guardrails.
-The design decision is WHERE each lives: static (always loaded, expensive) vs
-dynamic (loaded on demand, cheap). That boundary is versioned code, reviewed in PRs.
-
-## Static (injected every session by the SessionStart hook, hard cap 60 lines total)
-- `sdlc/context/constitution.md` (≤30) — hard rules + stack facts only.
-- `sdlc/context/steering/*.md` with `inclusion: always` — should be rare.
-- One pointer line to the active change.
-
-## Dynamic (loaded only when needed)
-- `inclusion: paths` steering — the PostToolUse hook emits a POINTER when an edited
-  file matches `pathMatch`; you then read the file. Pointers cost ~1 line, not 40.
-- `inclusion: manual` — read only when a playbook or user names it.
-- `inclusion: agent` — subagents load it themselves; the main loop never pays for it.
-- Living specs — read the `## Purpose` header first; open the full spec only for
-  capabilities your change touches.
-- Playbooks — each command reads exactly one playbook file.
-
-## Budget rules
-- Always-budget (constitution + always-steering) ≤ 60 lines. Validator-enforced.
-- Adding an always rule requires removing one, or demoting something to `paths`.
-- `/sdlc:observe` reports steering that never fires — expire or demote it.
-- A `compact` event in the journal means context overflowed: treat as a defect,
-  find the resident artifact that caused it.
+# Context engineering
+
+Six context types: instructions, knowledge, memory, examples, tools, guardrails.
+The design decision is WHERE each lives: static (always loaded, expensive) vs
+dynamic (loaded on demand, cheap). That boundary is versioned code, reviewed in PRs.
+
+## Static (injected every session by the SessionStart hook, hard cap 60 lines total)
+- `sdlc/context/constitution.md` (≤30) — hard rules + stack facts only.
+- `sdlc/context/steering/*.md` with `inclusion: always` — should be rare.
+- One pointer line to the active change.
+
+## Dynamic (loaded only when needed)
+- `inclusion: paths` steering — the PostToolUse hook emits a POINTER when an edited
+  file matches `pathMatch`; you then read the file. Pointers cost ~1 line, not 40.
+- `inclusion: manual` — read only when a playbook or user names it.
+- `inclusion: agent` — subagents load it themselves; the main loop never pays for it.
+- Living specs — read the `## Purpose` header first; open the full spec only for
+  capabilities your change touches.
+- Playbooks — each command reads exactly one playbook file.
+
+## Budget rules
+- Always-budget (constitution + always-steering) ≤ 60 lines. Validator-enforced.
+- Adding an always rule requires removing one, or demoting something to `paths`.
+- `/sdlc:observe` reports steering that never fires — expire or demote it.
+- A `compact` event in the journal means context overflowed: treat as a defect,
+  find the resident artifact that caused it.

package/payload/playbook/contract.md

@@ -1,23 +1,23 @@
-# /sdlc:contract <id> — tests + evals before code
-
-The contract IS the handshake. Nothing in `## Tasks` may be implemented while
-status is `new`.
-
-1. From the Delta scenarios, write `contract/tests.md` (≤60 lines): one row per
-   behavior — Given/When/Then, kind, mapped requirement. List what is explicitly
-   out of scope and why.
-2. Deep tier (standard optional): write `contract/evals.md` (≤40 lines) — the
-   trajectory + quality rubric the sdlc-evaluator will score.
-3. Generate failing tests: delegate to the `sdlc-contractor` agent (cheap tier)
-   with ONLY tests.md + the delta + the project's test conventions. Run the test
-   command from `sdlc/harness.md` — every new test must FAIL (red) now; a test
-   that passes before implementation tests nothing.
-4. Adversarial check instead of human approval: ask the `sdlc-quality` agent to
-   attack the contract — uncovered scenarios, untestable rows, missing edge
-   cases vs the delta. Fix findings; one round is usually enough, two max.
-5. `npx @warnyin/sdlc validate <id>` clean → set frontmatter `status: contracted`
-   and `node sdlc/.hooks/journal.mjs note contract tests=<n>`.
-
-Escalate only if the delta itself turns out ambiguous (back to /sdlc:new step 5).
-
-Next: /sdlc:build.
+# /sdlc:contract <id> — tests + evals before code
+
+The contract IS the handshake. Nothing in `## Tasks` may be implemented while
+status is `new`.
+
+1. From the Delta scenarios, write `contract/tests.md` (≤60 lines): one row per
+   behavior — Given/When/Then, kind, mapped requirement. List what is explicitly
+   out of scope and why.
+2. Deep tier (standard optional): write `contract/evals.md` (≤40 lines) — the
+   trajectory + quality rubric the sdlc-evaluator will score.
+3. Generate failing tests: delegate to the `sdlc-contractor` agent (cheap tier)
+   with ONLY tests.md + the delta + the project's test conventions. Run the test
+   command from `sdlc/harness.md` — every new test must FAIL (red) now; a test
+   that passes before implementation tests nothing.
+4. Adversarial check instead of human approval: ask the `sdlc-quality` agent to
+   attack the contract — uncovered scenarios, untestable rows, missing edge
+   cases vs the delta. Fix findings; one round is usually enough, two max.
+5. `npx @warnyin/sdlc validate <id>` clean → set frontmatter `status: contracted`
+   and `node sdlc/.hooks/journal.mjs note contract tests=<n>`.
+
+Escalate only if the delta itself turns out ambiguous (back to /sdlc:new step 5).
+
+Next: /sdlc:build.

package/payload/playbook/converge.md

@@ -1,19 +1,19 @@
-# /sdlc:converge [capability] — spec ↔ code drift (Maintenance)
-
-Living specs are only useful while they are true. Converge closes the gap.
-
-1. Scope: the named capability, or the ones `/sdlc:observe` flagged.
-2. For each requirement in `sdlc/specs/<capability>/spec.md`, check the code
-   actually behaves that way (read the relevant code; run targeted tests where
-   cheap). Three outcomes per requirement:
-   - **true** — nothing to do.
-   - **code drifted** — behavior no longer matches the spec.
-   - **spec stale** — the spec describes behavior nobody wants anymore.
-3. Report the diff table in chat (requirement · outcome · evidence file:line).
-4. For every drift/stale finding the user wants fixed, open ONE change via
-   /sdlc:new whose Delta uses MODIFIED/REMOVED against the exact requirement
-   names — converge itself NEVER edits specs or code directly.
-5. If a recent rule/playbook edit correlates with worse flywheel metrics
-   (observe shows it), propose the revert here as a change too.
-
-Read-only except for creating proposed change folders.
+# /sdlc:converge [capability] — spec ↔ code drift (Maintenance)
+
+Living specs are only useful while they are true. Converge closes the gap.
+
+1. Scope: the named capability, or the ones `/sdlc:observe` flagged.
+2. For each requirement in `sdlc/specs/<capability>/spec.md`, check the code
+   actually behaves that way (read the relevant code; run targeted tests where
+   cheap). Three outcomes per requirement:
+   - **true** — nothing to do.
+   - **code drifted** — behavior no longer matches the spec.
+   - **spec stale** — the spec describes behavior nobody wants anymore.
+3. Report the diff table in chat (requirement · outcome · evidence file:line).
+4. For every drift/stale finding the user wants fixed, open ONE change via
+   /sdlc:new whose Delta uses MODIFIED/REMOVED against the exact requirement
+   names — converge itself NEVER edits specs or code directly.
+5. If a recent rule/playbook edit correlates with worse flywheel metrics
+   (observe shows it), propose the revert here as a change too.
+
+Read-only except for creating proposed change folders.

package/payload/playbook/design.md

@@ -1,20 +1,20 @@
-# /sdlc:design <id> — decisions & trade-offs (deep tier, or on signal)
-
-Run only when: tier is deep, OR the change needs an architectural decision
-(new dependency, schema change, cross-capability contract). Otherwise skip —
-an empty Design section is garbage.
-
-1. Read `change.md`, the full spec of every touched capability, and any steering
-   whose scope matches. Nothing else by default.
-2. Gather in parallel, judge serially: fan out read-only subagents for research
-   (one per question: prior art in this repo, external constraint, data shape).
-   The DECISION is made in the main loop — never delegated, never parallel.
-3. Fill `## Design` with decision lines only:
-   `- decision: <what> · alternatives: <a/b> · because: <why>`
-   Never restate the delta. Respect the tier cap (deep total ≤150).
-4. Escalate to the human ONLY for decisions listed in
-   `sdlc/harness.md § Autonomy policy` (irreversible or hard-floor). Everything
-   else: decide, record, move on.
-5. `npx @warnyin/sdlc validate <id>`.
-
-Next: /sdlc:contract.
+# /sdlc:design <id> — decisions & trade-offs (deep tier, or on signal)
+
+Run only when: tier is deep, OR the change needs an architectural decision
+(new dependency, schema change, cross-capability contract). Otherwise skip —
+an empty Design section is garbage.
+
+1. Read `change.md`, the full spec of every touched capability, and any steering
+   whose scope matches. Nothing else by default.
+2. Gather in parallel, judge serially: fan out read-only subagents for research
+   (one per question: prior art in this repo, external constraint, data shape).
+   The DECISION is made in the main loop — never delegated, never parallel.
+3. Fill `## Design` with decision lines only:
+   `- decision: <what> · alternatives: <a/b> · because: <why>`
+   Never restate the delta. Respect the tier cap (deep total ≤150).
+4. Escalate to the human ONLY for decisions listed in
+   `sdlc/harness.md § Autonomy policy` (irreversible or hard-floor). Everything
+   else: decide, record, move on.
+5. `npx @warnyin/sdlc validate <id>`.
+
+Next: /sdlc:contract.

package/payload/playbook/init.md

@@ -1,22 +1,22 @@
-# /sdlc:init — configure the harness (run once per project)
-
-The only planned blocking human gate in the framework: the human approves the
-policy the AI will then drive under.
-
-1. Read `sdlc/config.yaml`, the repo README, manifest files (package.json etc.),
-   and skim the top-level structure. Do NOT deep-read the codebase.
-2. Interview the user briefly (≤6 questions): what the project is, hard rules the
-   agent must never break, test command, risk areas (security/payments/data-loss),
-   and how autonomous shipping should be (adjusts `## Autonomy policy`).
-3. Open the gate: `node sdlc/.hooks/journal.mjs open-steer`, then write:
-   - `sdlc/context/constitution.md` — replace template placeholders; ≤30 lines;
-     SHALL/SHALL NOT rules only, stack facts ≤3 lines.
-   - `sdlc/harness.md` — fill tools, test command, sandbox notes; adjust the
-     routing, triage, and Autonomy policy tables to this project.
-   - 0–3 steering seeds in `sdlc/context/steering/` for areas with real
-     conventions (prefer `inclusion: paths`; `always` needs strong justification).
-4. Run `npx @warnyin/sdlc validate` — fix every error.
-5. Show the user constitution + harness verbatim; iterate until approved.
-6. Close the gate: `node sdlc/.hooks/journal.mjs close`.
-
-Output: approved constitution + harness. No change folder is created here.
+# /sdlc:init — configure the harness (run once per project)
+
+The only planned blocking human gate in the framework: the human approves the
+policy the AI will then drive under.
+
+1. Read `sdlc/config.yaml`, the repo README, manifest files (package.json etc.),
+   and skim the top-level structure. Do NOT deep-read the codebase.
+2. Interview the user briefly (≤6 questions): what the project is, hard rules the
+   agent must never break, test command, risk areas (security/payments/data-loss),
+   and how autonomous shipping should be (adjusts `## Autonomy policy`).
+3. Open the gate: `node sdlc/.hooks/journal.mjs open-steer`, then write:
+   - `sdlc/context/constitution.md` — replace template placeholders; ≤30 lines;
+     SHALL/SHALL NOT rules only, stack facts ≤3 lines.
+   - `sdlc/harness.md` — fill tools, test command, sandbox notes; adjust the
+     routing, triage, and Autonomy policy tables to this project.
+   - 0–3 steering seeds in `sdlc/context/steering/` for areas with real
+     conventions (prefer `inclusion: paths`; `always` needs strong justification).
+4. Run `npx @warnyin/sdlc validate` — fix every error.
+5. Show the user constitution + harness verbatim; iterate until approved.
+6. Close the gate: `node sdlc/.hooks/journal.mjs close`.
+
+Output: approved constitution + harness. No change folder is created here.

package/payload/playbook/new.md

@@ -1,22 +1,22 @@
-# /sdlc:new <title> — open a change (Requirements)
-
-1. Triage the tier with `sdlc/harness.md § Tier triage`. Hard-floor surface
-   (security, payments, data-loss, irreversible) forces `deep` — no override
-   without an explicit user instruction (record it in Assumptions).
-2. Create `sdlc/changes/<kebab-id>/change.md` from the tier's template at
-   `sdlc/.playbook/templates/change-{vibe|standard|deep}.md` — copy the
-   structure exactly, respect the cap comment.
-3. Ground the delta: grep `## Purpose` of every `sdlc/specs/*/spec.md`; open the
-   FULL spec only for capabilities this change touches. Name each `## Delta:`
-   after an existing capability, or a new kebab-case capability.
-4. Write Why (≤5 lines, no solutioning) and the Delta requirements
-   (`ADDED/MODIFIED/REMOVED Requirement` + WHEN/THEN scenarios — grammar in the
-   delta-spec-format skill). Then Tasks with `[P]` and `[tier:x]` markers.
-5. Ambiguity policy (AI-driven): make the safest assumption and record it under
-   `## Assumptions` with why it is safe. Use `[NEEDS CLARIFICATION: q]` ONLY for
-   facts you cannot obtain or safely assume — then ask the user those questions
-   now, in one batch, and resolve every marker.
-6. `node sdlc/.hooks/journal.mjs set-active <id>` then
-   `npx @warnyin/sdlc validate <id>` — fix errors. Status stays `new`.
-
-Next: deep tier or risky decision → /sdlc:design; otherwise /sdlc:contract.
+# /sdlc:new <title> — open a change (Requirements)
+
+1. Triage the tier with `sdlc/harness.md § Tier triage`. Hard-floor surface
+   (security, payments, data-loss, irreversible) forces `deep` — no override
+   without an explicit user instruction (record it in Assumptions).
+2. Create `sdlc/changes/<kebab-id>/change.md` from the tier's template at
+   `sdlc/.playbook/templates/change-{vibe|standard|deep}.md` — copy the
+   structure exactly, respect the cap comment.
+3. Ground the delta: grep `## Purpose` of every `sdlc/specs/*/spec.md`; open the
+   FULL spec only for capabilities this change touches. Name each `## Delta:`
+   after an existing capability, or a new kebab-case capability.
+4. Write Why (≤5 lines, no solutioning) and the Delta requirements
+   (`ADDED/MODIFIED/REMOVED Requirement` + WHEN/THEN scenarios — grammar in the
+   delta-spec-format skill). Then Tasks with `[P]` and `[tier:x]` markers.
+5. Ambiguity policy (AI-driven): make the safest assumption and record it under
+   `## Assumptions` with why it is safe. Use `[NEEDS CLARIFICATION: q]` ONLY for
+   facts you cannot obtain or safely assume — then ask the user those questions
+   now, in one batch, and resolve every marker.
+6. `node sdlc/.hooks/journal.mjs set-active <id>` then
+   `npx @warnyin/sdlc validate <id>` — fix errors. Status stays `new`.
+
+Next: deep tier or risky decision → /sdlc:design; otherwise /sdlc:contract.

package/payload/playbook/next.md

@@ -1,12 +1,12 @@
-# /sdlc:next — where am I, what now (read-only)
-
-1. Run `npx @warnyin/sdlc status`.
-2. For each active change map status → next command:
-   - `new` + markers unresolved → resolve questions (playbook new.md §5)
-   - `new` (clean) → /sdlc:design (deep/signal) or /sdlc:contract
-   - `contracted` → /sdlc:build
-   - `building` → /sdlc:build (finish open tasks)
-   - `verified` → /sdlc:review (if signals) or /sdlc:ship
-3. If nothing is active: suggest /sdlc:new, or /sdlc:observe if archived changes
-   have unread digests.
-4. Answer in ≤5 lines. Create or modify nothing.
+# /sdlc:next — where am I, what now (read-only)
+
+1. Run `npx @warnyin/sdlc status`.
+2. For each active change map status → next command:
+   - `new` + markers unresolved → resolve questions (playbook new.md §5)
+   - `new` (clean) → /sdlc:design (deep/signal) or /sdlc:contract
+   - `contracted` → /sdlc:build
+   - `building` → /sdlc:build (finish open tasks)
+   - `verified` → /sdlc:review (if signals) or /sdlc:ship
+3. If nothing is active: suggest /sdlc:new, or /sdlc:observe if archived changes
+   have unread digests.
+4. Answer in ≤5 lines. Create or modify nothing.

package/payload/playbook/observe.md

@@ -1,20 +1,20 @@
-# /sdlc:observe — cost, flow, and drift report
-
-1. Run `npx @warnyin/sdlc observe --json` and render it for the human. Do not
-   recompute anything the CLI already computed.
-2. Report, in this order (skip empty sections):
-   - **Pending digests** — archived changes whose digest the human has not been
-     shown yet (learner proposals awaiting a decision).
-   - **Cost** — tokens/cost per active + recent change; retry waste (tokens spent
-     after the first verify fail).
-   - **Flow** — lead time per shipped change and per-phase breakdown (created →
-     contracted → built → verified → shipped timestamps from the journal);
-     AI-time vs wait-time; first-pass success trend.
-   - **Residency** — always-loaded lines vs the 60 budget.
-   - **Drift flags** — steering never hit by a pointer, rules never triggering a
-     guard event, `compact` events (context overflow = a defect), specs touched
-     by many changes (converge candidates).
-3. For each flag, offer the one-line fix (`/sdlc:steer` demotion, `/sdlc:converge`
-   on a capability, cap adjustment) — recommend, never auto-apply here.
-
-Read-only: this command changes nothing.
+# /sdlc:observe — cost, flow, and drift report
+
+1. Run `npx @warnyin/sdlc observe --json` and render it for the human. Do not
+   recompute anything the CLI already computed.
+2. Report, in this order (skip empty sections):
+   - **Pending digests** — archived changes whose digest the human has not been
+     shown yet (learner proposals awaiting a decision).
+   - **Cost** — tokens/cost per active + recent change; retry waste (tokens spent
+     after the first verify fail).
+   - **Flow** — lead time per shipped change and per-phase breakdown (created →
+     contracted → built → verified → shipped timestamps from the journal);
+     AI-time vs wait-time; first-pass success trend.
+   - **Residency** — always-loaded lines vs the 60 budget.
+   - **Drift flags** — steering never hit by a pointer, rules never triggering a
+     guard event, `compact` events (context overflow = a defect), specs touched
+     by many changes (converge candidates).
+3. For each flag, offer the one-line fix (`/sdlc:steer` demotion, `/sdlc:converge`
+   on a capability, cap adjustment) — recommend, never auto-apply here.
+
+Read-only: this command changes nothing.

package/payload/playbook/principles.md

@@ -1,28 +1,28 @@
-# Principles
-
-## Factory model
-Your output is the system that produces code — specs, contracts, gates, feedback loops,
-guardrails — not the code itself. Give agents success criteria, not step-by-step
-instructions, then let them iterate. Humans set policy once (`/sdlc:init`) and read
-ship digests asynchronously; they are interrupted only by policy-listed exceptions.
-
-## Economics (CapEx / OpEx)
-Configuration (constitution, harness, steering, contracts) is CapEx: paid once, reviewed
-like code. Every resident line of context is OpEx paid in every turn. Therefore:
-- Every mandatory artifact has a stated reason and a line cap (see template comments).
-- No artifact may restate another; deltas are merged mechanically, never re-narrated.
-- Retry loops are the expensive failure mode — contracts up front buy first-pass success.
-
-## Anti-garbage rules
-- Optional artifacts (design section, evals for standard tier) exist only on signal.
-- If a section would be empty, delete the section — never keep placeholder prose.
-- The learner may only ADD an always-loaded rule by displacing an old one (fixed budget).
-- Machine data (journals, state, learning stats) never lives in prose files.
-
-## Verification stance
-Tests verify the deterministic; evals verify trajectory and quality. Both are written
-before code — together they are the contract with the AI. "Seems to work" is not a gate.
-
-## Minimalism
-Prefer: do nothing → stdlib → existing dependency → smallest new code. Never cut:
-trust-boundary validation, data-loss handling, security controls, the contract itself.
+# Principles
+
+## Factory model
+Your output is the system that produces code — specs, contracts, gates, feedback loops,
+guardrails — not the code itself. Give agents success criteria, not step-by-step
+instructions, then let them iterate. Humans set policy once (`/sdlc:init`) and read
+ship digests asynchronously; they are interrupted only by policy-listed exceptions.
+
+## Economics (CapEx / OpEx)
+Configuration (constitution, harness, steering, contracts) is CapEx: paid once, reviewed
+like code. Every resident line of context is OpEx paid in every turn. Therefore:
+- Every mandatory artifact has a stated reason and a line cap (see template comments).
+- No artifact may restate another; deltas are merged mechanically, never re-narrated.
+- Retry loops are the expensive failure mode — contracts up front buy first-pass success.
+
+## Anti-garbage rules
+- Optional artifacts (design section, evals for standard tier) exist only on signal.
+- If a section would be empty, delete the section — never keep placeholder prose.
+- The learner may only ADD an always-loaded rule by displacing an old one (fixed budget).
+- Machine data (journals, state, learning stats) never lives in prose files.
+
+## Verification stance
+Tests verify the deterministic; evals verify trajectory and quality. Both are written
+before code — together they are the contract with the AI. "Seems to work" is not a gate.
+
+## Minimalism
+Prefer: do nothing → stdlib → existing dependency → smallest new code. Never cut:
+trust-boundary validation, data-loss handling, security controls, the contract itself.

package/payload/playbook/review.md

@@ -1,17 +1,17 @@
-# /sdlc:review <id> — agent panel (signal-triggered)
-
-Run when: tier deep, OR the diff touches auth/payments/data handling, OR >10
-files changed. Otherwise skip silently — a ceremonial review is garbage.
-
-1. Fan out in parallel, all read-only, each with the diff + change.md only:
-   - `sdlc-architect` (deepest): design integrity, coupling, contract drift.
-   - `sdlc-security` (balanced): injection, authz, secrets, unsafe deps.
-   - `sdlc-quality` (cheap): contract coverage gaps, edge cases, dead code.
-   - `sdlc-ops` (cheap): config, migrations, rollback, observability impact.
-2. Merge findings in the main loop. Classify: blocker | improvement | note.
-3. Blockers → append as fix tasks and route back to /sdlc:build (counts toward
-   the same 3-round budget as verify). Improvements: apply if ≤5 min each,
-   otherwise record one line in the change for the digest.
-4. `node sdlc/.hooks/journal.mjs note review blockers=<n>`.
-
-Pass condition: zero open blockers. Next: /sdlc:ship.
+# /sdlc:review <id> — agent panel (signal-triggered)
+
+Run when: tier deep, OR the diff touches auth/payments/data handling, OR >10
+files changed. Otherwise skip silently — a ceremonial review is garbage.
+
+1. Fan out in parallel, all read-only, each with the diff + change.md only:
+   - `sdlc-architect` (deepest): design integrity, coupling, contract drift.
+   - `sdlc-security` (balanced): injection, authz, secrets, unsafe deps.
+   - `sdlc-quality` (cheap): contract coverage gaps, edge cases, dead code.
+   - `sdlc-ops` (cheap): config, migrations, rollback, observability impact.
+2. Merge findings in the main loop. Classify: blocker | improvement | note.
+3. Blockers → append as fix tasks and route back to /sdlc:build (counts toward
+   the same 3-round budget as verify). Improvements: apply if ≤5 min each,
+   otherwise record one line in the change for the digest.
+4. `node sdlc/.hooks/journal.mjs note review blockers=<n>`.
+
+Pass condition: zero open blockers. Next: /sdlc:ship.

package/payload/playbook/routing.md

@@ -1,19 +1,19 @@
-# Model routing
-
-Generic tiers only — the harness adapter maps them to real models
-(Claude Code agents: cheap→haiku, balanced→sonnet, deepest→opus).
-
-| Task kind | Tier | Why |
-|---|---|---|
-| requirements shaping, architecture, deep design | deepest | judgment-heavy, small volume |
-| standard implementation (sdlc-builder) | balanced | quality/cost sweet spot |
-| test generation (sdlc-contractor) | cheap | mechanical from the contract table |
-| eval judging (sdlc-evaluator) | cheap | rubric scoring, high volume |
-| review panel passes | cheap–balanced | parallel, bounded scope |
-| learning distillation (sdlc-learner) | cheap | summarization over journals |
-
-Rules:
-- Task lines in change.md may carry `[tier:cheap|balanced|deepest]`; default = balanced.
-- Never send a mechanical task to deepest "to be safe" — that is the waste the
-  routing table exists to prevent.
-- Escalate one tier only after a concrete failure at the current tier (journal it).
+# Model routing
+
+Generic tiers only — the harness adapter maps them to real models
+(Claude Code agents: cheap→haiku, balanced→sonnet, deepest→opus).
+
+| Task kind | Tier | Why |
+|---|---|---|
+| requirements shaping, architecture, deep design | deepest | judgment-heavy, small volume |
+| standard implementation (sdlc-builder) | balanced | quality/cost sweet spot |
+| test generation (sdlc-contractor) | cheap | mechanical from the contract table |
+| eval judging (sdlc-evaluator) | cheap | rubric scoring, high volume |
+| review panel passes | cheap–balanced | parallel, bounded scope |
+| learning distillation (sdlc-learner) | cheap | summarization over journals |
+
+Rules:
+- Task lines in change.md may carry `[tier:cheap|balanced|deepest]`; default = balanced.
+- Never send a mechanical task to deepest "to be safe" — that is the waste the
+  routing table exists to prevent.
+- Escalate one tier only after a concrete failure at the current tier (journal it).

package/payload/playbook/rules-card.md

@@ -1,16 +1,16 @@
-# sdlc rules card
-<!-- ≤40 lines · embedded verbatim in non-Claude tool adapters; Claude gets the same rules enforced by hooks. -->
-
-- Work flows through `sdlc/changes/<id>/change.md`: new → [design] → contract → build → verify → [review] → ship.
-- NEVER edit `sdlc/specs/**` or `sdlc/changes/archive/**` by hand. Living specs change only
-  via a change's `## Delta:` section, merged by `npx @warnyin/sdlc archive <id>` at ship.
-- NEVER hand-edit `journal.ndjson` or `sdlc/.state/**` — they are machine-owned.
-- Write tests + evals (`contract/`) BEFORE code. No implementation while status is `new`.
-- Ambiguity: make the safest assumption and record it under `## Assumptions`; use
-  `[NEEDS CLARIFICATION: q]` only for facts you cannot obtain — resolve all before contract.
-- Respect line caps written in each template comment; run `npx @warnyin/sdlc validate <id>`
-  before claiming any gate passed — a red validator means the gate did NOT pass.
-- Constitution edits go through /sdlc:steer only; always-loaded context ≤ 60 lines total.
-- Verify = real test run + eval rubric. Max 3 fix rounds, then escalate to the human.
-- Hard-floor (security, payments, data-loss, irreversible): tier = deep, human approves ship.
-- Before editing an area, read any steering file whose `pathMatch` covers it.
+# sdlc rules card
+<!-- ≤40 lines · embedded verbatim in non-Claude tool adapters; Claude gets the same rules enforced by hooks. -->
+
+- Work flows through `sdlc/changes/<id>/change.md`: new → [design] → contract → build → verify → [review] → ship.
+- NEVER edit `sdlc/specs/**` or `sdlc/changes/archive/**` by hand. Living specs change only
+  via a change's `## Delta:` section, merged by `npx @warnyin/sdlc archive <id>` at ship.
+- NEVER hand-edit `journal.ndjson` or `sdlc/.state/**` — they are machine-owned.
+- Write tests + evals (`contract/`) BEFORE code. No implementation while status is `new`.
+- Ambiguity: make the safest assumption and record it under `## Assumptions`; use
+  `[NEEDS CLARIFICATION: q]` only for facts you cannot obtain — resolve all before contract.
+- Respect line caps written in each template comment; run `npx @warnyin/sdlc validate <id>`
+  before claiming any gate passed — a red validator means the gate did NOT pass.
+- Constitution edits go through /sdlc:steer only; always-loaded context ≤ 60 lines total.
+- Verify = real test run + eval rubric. Max 3 fix rounds, then escalate to the human.
+- Hard-floor (security, payments, data-loss, irreversible): tier = deep, human approves ship.
+- Before editing an area, read any steering file whose `pathMatch` covers it.

package/payload/playbook/ship.md

@@ -1,24 +1,24 @@
-# /sdlc:ship <id> — merge, archive, learn, digest
-
-Precondition: `status: verified` (+ review passed when it ran).
-
-1. **Policy check** (`sdlc/harness.md § Autonomy policy`): if this change is NOT
-   auto-shippable (deep/hard-floor), show the human a 5-line summary (why, delta
-   heads, verify result, cost so far) and wait for approval. Otherwise proceed.
-2. Open the gate and archive mechanically:
-   `node sdlc/.hooks/journal.mjs open-ship <id>`
-   `npx @warnyin/sdlc archive <id>`
-   (validates --strict, merges every Delta into `sdlc/specs/`, promotes evals,
-   stamps `status: shipped`, moves the folder to `changes/archive/<date>-<id>/`).
-3. **Learn** — delegate to `sdlc-learner` (cheap) with the archived change.md +
-   its journal.ndjson. It proposes ≤3 items: add-rule (with evidence pointer) /
-   expire-or-demote (rule or steering that never fired) / harness tweak.
-   Apply reductions and demotions immediately (they always save tokens).
-   Additions to always-loaded context are NOT applied — list them in the digest.
-4. **Digest** — write `sdlc/changes/archive/<date>-<id>/digest.md` (≤15 lines):
-   what shipped, spec deltas merged, assumptions made, verify rounds, tokens/cost
-   (from journal `session` events), learner proposals awaiting the human.
-5. Close the gate: `node sdlc/.hooks/journal.mjs close`. Tell the user in one
-   line: shipped + where the digest is.
-
-The digest is the async human touchpoint — reviewable and revertible later.
+# /sdlc:ship <id> — merge, archive, learn, digest
+
+Precondition: `status: verified` (+ review passed when it ran).
+
+1. **Policy check** (`sdlc/harness.md § Autonomy policy`): if this change is NOT
+   auto-shippable (deep/hard-floor), show the human a 5-line summary (why, delta
+   heads, verify result, cost so far) and wait for approval. Otherwise proceed.
+2. Open the gate and archive mechanically:
+   `node sdlc/.hooks/journal.mjs open-ship <id>`
+   `npx @warnyin/sdlc archive <id>`
+   (validates --strict, merges every Delta into `sdlc/specs/`, promotes evals,
+   stamps `status: shipped`, moves the folder to `changes/archive/<date>-<id>/`).
+3. **Learn** — delegate to `sdlc-learner` (cheap) with the archived change.md +
+   its journal.ndjson. It proposes ≤3 items: add-rule (with evidence pointer) /
+   expire-or-demote (rule or steering that never fired) / harness tweak.
+   Apply reductions and demotions immediately (they always save tokens).
+   Additions to always-loaded context are NOT applied — list them in the digest.
+4. **Digest** — write `sdlc/changes/archive/<date>-<id>/digest.md` (≤15 lines):
+   what shipped, spec deltas merged, assumptions made, verify rounds, tokens/cost
+   (from journal `session` events), learner proposals awaiting the human.
+5. Close the gate: `node sdlc/.hooks/journal.mjs close`. Tell the user in one
+   line: shipped + where the digest is.
+
+The digest is the async human touchpoint — reviewable and revertible later.

package/payload/playbook/steer.md

@@ -1,21 +1,21 @@
-# /sdlc:steer — manage the static/dynamic boundary
-
-The ONLY sanctioned way to edit always-loaded context.
-
-1. `node sdlc/.hooks/journal.mjs open-steer`
-2. Apply the requested edits:
-   - New knowledge → a steering file with the LEAST resident inclusion mode that
-     works: `agent` > `manual` > `paths` > `always` (always needs justification).
-   - Constitution edits: SHALL/SHALL NOT lines only. If the always-budget
-     (60 lines) would overflow, something must be demoted or deleted first —
-     name the displaced line explicitly.
-3. Hygiene pass (do it every time, it is 30 seconds):
-   - `/sdlc:observe` data — steering never pointer-hit across the last N changes
-     → propose demote (`paths`→`manual`) or delete.
-   - Rules with no guard/journal evidence of ever mattering → propose expiry.
-   - Apply what the user agrees to (reductions may be applied without asking).
-4. `npx @warnyin/sdlc validate` — the always-budget check must be green.
-5. `node sdlc/.hooks/journal.mjs close`
-
-Learning direction is one-way by design: content flows from always → paths →
-manual → deleted as evidence accumulates. Getting leaner is the success metric.
+# /sdlc:steer — manage the static/dynamic boundary
+
+The ONLY sanctioned way to edit always-loaded context.
+
+1. `node sdlc/.hooks/journal.mjs open-steer`
+2. Apply the requested edits:
+   - New knowledge → a steering file with the LEAST resident inclusion mode that
+     works: `agent` > `manual` > `paths` > `always` (always needs justification).
+   - Constitution edits: SHALL/SHALL NOT lines only. If the always-budget
+     (60 lines) would overflow, something must be demoted or deleted first —
+     name the displaced line explicitly.
+3. Hygiene pass (do it every time, it is 30 seconds):
+   - `/sdlc:observe` data — steering never pointer-hit across the last N changes
+     → propose demote (`paths`→`manual`) or delete.
+   - Rules with no guard/journal evidence of ever mattering → propose expiry.
+   - Apply what the user agrees to (reductions may be applied without asking).
+4. `npx @warnyin/sdlc validate` — the always-budget check must be green.
+5. `node sdlc/.hooks/journal.mjs close`
+
+Learning direction is one-way by design: content flows from always → paths →
+manual → deleted as evidence accumulates. Getting leaner is the success metric.