@thebassclef/lite 0.1.3 → 1.0.1

package/substrate/.claude/rules/guardrails.md

@@ -1,73 +0,0 @@
----
-tier: lite
-globs: ["*"]
-description: Agent guardrails — behavior boundaries, escalation rules, capability ceilings for autonomous operation
----
-
-# Agent Guardrails
-
-Formal behavior boundaries for autonomous agents. These are hard constraints,
-not guidelines.
-
-## What agents must NEVER do
-- Push to main without PR review
-- Delete data in production databases
-- Deploy to production without human approval — even in orchestrator-gated mode. This is the hardest guardrail. No exceptions.
-- Deploy to any environment not configured in substrate.config.md deploy_targets
-- Modify auth/security middleware without human approval
-- Expand scope beyond the declared time budget
-- Skip a hard gate (Inception → Elaboration → Construction → Transition)
-- Self-report gate compliance without evidence artifacts
-- Override another agent's decision authority (e.g., Builder overriding Architect on ADRs)
-- Send external communications (emails, Slack, webhooks) without human approval
-- Modify CI/CD pipeline configuration without human approval
-- Create or delete GitHub repos, branches on main, or release tags
-
-## What agents must ALWAYS do
-- Save state before ending (commit, push, LAST_SAVE)
-- Write a chronicle entry at session end
-- Run /temperance before non-trivial implementation
-- Run /verify after each task before committing
-- Flag ambiguity rather than proceeding with assumptions
-- Produce a substrate artifact at every handoff
-- Reference the iteration goal when starting work
-- Check the risk register at iteration start
-
-## Escalation rules
-- Builder → Architect for ADR questions
-- Builder → PM for scope questions
-- Builder → Designer for UX questions
-- Any agent → Orchestrator for sequencing disputes
-- Any agent → Human for: scope expansion, security changes, external communications, budget overruns
-
-## Capability ceilings by role
-- Reviewer: read-only. Cannot modify code.
-- Shaper: cannot implement or deploy.
-- PM: cannot implement or architect.
-- Designer: cannot implement. Validates only.
-- Creative Director: cannot implement. Directs only.
-- Architect: cannot implement in Construction. Designs only.
-- Builder: cannot override ADRs. Implements within constraints.
-- Deployer: cannot write application code. Ships only.
-- Closer: cannot build. Documents and closes only.
-- Orchestrator: cannot override any role's decision authority. Coordinates only.
-
-## Graceful exit conditions
-
-See `standards/graceful-exit.md` for the full exit protocol, checkpoint format,
-checkpoint triggers, and recovery procedure.
-
-Summary of conditions (full protocol in the standard):
-- Time budget exhausted → save state, write checkpoint, report progress, end
-- Budget limit reached → save state, write checkpoint, report, end
-- Ambiguity unresolvable without human → save state, write checkpoint, escalate, end
-- Blocked by external dependency → save state, log blocker in checkpoint, end
-- Error after 3 diagnosis attempts → save state, write checkpoint, escalate, end
-- User interrupts → save state immediately, write checkpoint
-- Context pressure ≥ 70% → write checkpoint, let compaction run, re-read survival kit
-
-## Agent identity in artifacts
-- Every commit by an autonomous agent includes the agent role in the message
-- Every PR created by an agent is labeled with the agent role
-- Chronicle entries note which agent(s) were active
-- This enables audit: who did what, with what authority

package/substrate/.claude/rules/hook-wire-on-author.md

@@ -1,103 +0,0 @@
----
-tier: lite
-description: Every new bassclef hook (a file under .claude/hooks/*.sh) MUST be added to project .claude/settings.json in the same PR that authors it.
----
-
-# Hook Wire On Author
-
-Every new bassclef hook (a file under `.claude/hooks/*.sh`) MUST be added to project `.claude/settings.json` in the same PR that authors it. Hooks without settings entries are dead-letter — they exist on disk but stay silent on every tool call. The substrate appears to ship the safety net; in reality, every adopter session runs without it.
-
-INSTEAD of shipping the hook on its own: include the settings entry in the same PR. The cost is one settings.json edit; the work compounds across every adopter session.
-
-This rule closes the substrate-defect class that produced bassclef-upstream#319 (phase-1, closed 2026-06-24) + #376 (phase-2, this rule's filing context).
-
-## Why this rule exists
-
-Audit during PR #318 surfaced 32 of 42 bassclef hooks without settings entries. The defect class: write hook → ship hook → forget the settings entry. No mechanical check existed to flag these at PR-author boundary.
-
-INSTEAD of letting the gap repeat: this rule + the V2 mechanical layer in `pre-commit-gate.sh` close the class at the authoring boundary so phase-3 never has to file.
-
-Phase-1 (#319) shipped a subset of P0 entries during the 2026-06-24 architect-review longrun. Phase-2 (#376) shipped the remaining 11 during the 2026-06-26 ultra-plus thread longrun. Both bets exist because the discipline was methodology-only.
-
-## When this rule fires
-
-Any PR that adds a new `.claude/hooks/*.sh` file. The rule passes through on:
-
-- Edits to existing hooks (only NEW hook files trigger)
-- Test files under `.claude/hooks/tests/`
-- Library scripts under `lib/` (those are sourced; not hooks)
-- Documentation under `.claude/hooks/*.md`
-
-## What the rule requires
-
-When a PR adds a new hook file, the same PR MUST also include an edit to `.claude/settings.json` adding the hook at its correct matcher. The hook's header MUST declare its intended matcher per these conventions:
-
-- `# PreToolUse: <matcher>` — added under `hooks.PreToolUse[].matcher`
-- `# Stop` — added under `hooks.Stop[].hooks`
-- `# PostToolUse: <matcher>` — added under `hooks.PostToolUse[].matcher`
-- `# SessionStart` — added under `hooks.SessionStart[].hooks`
-- `# UserPromptSubmit` — added under `hooks.UserPromptSubmit[].hooks`
-
-The PR body MUST include a `Bootstrap pair shipped` block per `.claude/rules/bootstrap-pair-discipline.md` naming both the hook file AND the settings.json entry line.
-
-## Anti-patterns
-
-These shapes fail this rule.
-
-**Hook shipped without settings entry.** Author edits `.claude/hooks/foo.sh`, commits, opens PR. Settings.json untouched.
-
-INSTEAD: ship the settings entry in the same PR. The cost is small (one settings.json line); the work compounds across every adopter session.
-
-**Hook references "sourced-only by design" in header.** Hook docstring says "this hook is sourced by other hooks, not connected directly." Phase-1 audit treated this as exempt; phase-2 reshape clarifies: composite/sourced libraries belong under `lib/`, not `.claude/hooks/`.
-
-INSTEAD of marking the hook exempt: move sourced-only libraries to `lib/`. Hooks under `.claude/hooks/` either get a settings entry or get moved.
-
-**Hook shipped at wrong matcher.** Author adds `pre-build-gate.sh` under PreToolUse Bash when its header says PreToolUse Edit|Write|MultiEdit. Hook stays silent.
-
-INSTEAD of guessing the matcher: read the hook's header before adding the entry. The matcher convention is documented above.
-
-## Mechanical layer
-
-**V1.5 (bassclef-upstream#1163 Layer 4, shipped 2026-08-08):** `.claude/hooks/hook-classifier-canary.sh` fires as PreToolUse Edit|Write|MultiEdit against paths under `.claude/hooks/*.sh` (excludes tests dir + fixtures). Detects new hook files that lack any recognized wiring signal (settings.json / .github/workflows / scripts/release-to-bassclef.sh / launchd header / sourced-lib header). Emits ADVISORY to stderr naming 5 remediation paths. Sources `lib/mechanism-fidelity.sh` for the classifier vocabulary. Override: `SKIP_HOOK_CLASSIFIER_CANARY=1`. Tier 0 test at `.claude/hooks/tests/hook-classifier-canary.test.sh` (10 tests).
-
-**V2 (deferred):** flip canary from ADVISORY to BLOCK once one calibration cycle passes with zero operator-reported false positives.
-
-**V3 (deferred to pre-commit sibling):** extend `pre-commit-gate.sh` to scan `git diff --staged --name-only` for new hooks and BLOCK when settings entry absent. Two-layer defense (author-time canary + commit-time gate) closes the class end-to-end.
-
-Defer V3 to a separate goal when V1.5+V2 have shipped through enough PRs that the failure modes are stable.
-
-## Override
-
-`SKIP_HOOK_WIRE_ON_AUTHOR=1 <command>` — logged via trace-helper. Use only when:
-
-- The hook is genuinely "in development" and ships without settings entry with a follow-on ticket filed AND the current PR cites the follow-on
-- Emergency rescue where adding the entry would break the harness
-
-INSTEAD of overriding for routine work: ship the settings entry in the same PR. The cost is small (one settings.json line); the discipline compounds across every adopter session.
-
-## Composes with
-
-- `.claude/rules/bootstrap-pair-discipline.md` — sister discipline (this rule extends the bootstrap-pair contract to hook + settings entry)
-- `.claude/rules/cold-adopter-harness-discipline.md` — sister discipline at adopter-observable boundary (settings.json IS adopter-observable)
-- `.claude/rules/blocked-items.md` — BLOCK protocol the V2 mechanical layer fires
-- `@luminary saltzer-schroeder` — complete mediation (the safety net is connected, not dead-letter)
-- `@luminary michael-nygard` — stability pattern (the settings entry is what makes the safety net real)
-- `@luminary linus-torvalds` — adopter-trust ceiling (bassclef hooks without settings entries equal adopter hooks without settings entries)
-
-## Distinct from
-
-- `.claude/rules/bootstrap-pair-discipline.md` — that rule covers any substrate building block + its pair; this rule covers the specific hook + settings entry case
-- `.claude/rules/testing-tier-config.md` — that rule covers Tier 0 strict TDD on the hook itself; this rule covers the settings entry beyond the test
-- `.claude/rules/cold-adopter-harness-discipline.md` — that rule covers adopter-observable changes broadly; this rule covers the hook-settings slice
-
-## Refs
-
-- bassclef-upstream#376 (parent — V1 ships this rule)
-- bassclef-upstream#319 (phase-1 closed; the sweep that surfaced the discipline gap)
-- bet `docs/iteration-bets/2026-06-26c-hook-wiring-phase-2.md` § WU-3 (this rule)
-- `.claude/rules/bootstrap-pair-discipline.md` (sister)
-- `@luminary saltzer-schroeder` + `@luminary michael-nygard` (anchors)
-
-## Retirement condition
-
-This rule retires only if bassclef migrates off hooks-as-substrate-primitives (very unlikely; hooks are the operational layer for substrate-discipline enforcement). The V2 mechanical extension may absorb the methodology check; the discipline at author time persists.

package/substrate/.claude/rules/identifier-leak-prevention.md

@@ -1,104 +0,0 @@
----
-tier: lite
-description: Bassclef commits stay free of operator machine identifiers.
----
-
-<!-- andon-allow: [A-Za-z][A-Za-z0-9]*-MacBook-(Air|Pro) -->
-<!-- andon-allow: /Users/[a-z][a-z0-9._-]+ -->
-<!-- andon-allow: /home/[a-z][a-z0-9._-]+ -->
-
-# Identifier leak prevention
-
-Bassclef commits stay free of operator machine identifiers.
-
-INSTEAD of committing hostname strings (X-MacBook-Air, DESKTOP-XYZ, X-server-N), absolute paths starting with /Users/ or /home/, or any operator-identifying metadata: rewrite the message or content with placeholders (branch name, `<machine>`, `$HOME`) before commit.
-
-This rule is the methodology layer. The mechanical layer is `.claude/hooks/pre-commit-identifier-leak-scrub.sh` (PreToolUse Bash matcher on `git commit`). Both required.
-
-## Why this rule exists
-
-Coverage gap surfaced by outside consult on 2026-09-01 (issue sunj-labs/bassclef#1471). Existing leakage scans (release-script andon + operator-private-path-check) target directory references, not identifier strings. Auto-save-checkpoint commits interpolated hostname into every message — 98 such commits landed on bassclef-upstream main + spread to public bassclef via archive snapshots.
-
-CCF-3 keeps operator config gitignored and out of git history.
-INSTEAD of assuming that discipline holds at the .gitignore layer alone: enforce at the commit boundary via this hook + rule pair. Both layers close the loop between principle and mechanism.
-
-## When this rule fires
-
-Every `git commit` invocation across bassclef and adopter repos. The hook scans:
-
-1. Commit message text (parses `-m "..."` arg)
-2. Staged content (`git diff --cached`)
-
-Fires on PreToolUse Bash matcher when `tool_input.command` starts with `git commit`. Non-git-commit commands pass through cleanly.
-
-## What the rule requires
-
-No commit lands with these patterns in message OR staged content:
-
-- **Hostname shapes**: `[A-Za-z][A-Za-z0-9]*-MacBook-(Air|Pro)`, `DESKTOP-[A-Z0-9]{4,}`, `*-server-*`, `*-desktop-*`
-- **Absolute paths**: `/Users/<name>`, `/home/<name>`
-
-Extension mechanism — future pattern classes added to the hook's `IDENTIFIER_PATTERNS` regex + a corresponding Tier 0 test.
-
-## Anti-patterns
-
-**Auto-save-checkpoint commits with hostname suffix.**
-
-INSTEAD of interpolating `$(hostname -s)` into the commit message per `save-state.sh` historical L222-225 shape: use branch name + file count only. Session identity moves to commit trailer if debug needed locally.
-
-**LAST_SAVE file with `machine:` field.**
-
-INSTEAD of writing machine identifier into `.claude/LAST_SAVE`: either gitignore the file OR drop the `machine:` field. This ticket takes both paths — gitignore the file + drop the field.
-
-**state/markers/ tracked in git.**
-
-INSTEAD of selectively-gitignored marker subdirs (contradicts `session-artifacts.md` L14-25): broad `state/markers/` gitignore + `git rm -r --cached state/markers/` one-time cure. Adopters inheriting the sync run the same cure once.
-
-## Override path
-
-`SKIP_IDENTIFIER_LEAK_SCRUB=1 git commit ...` — logged via trace-helper. Rare use cases:
-
-- Documentation explaining what patterns to avoid (e.g., this rule body cites the pattern class)
-- Migration scripts that intentionally reference historical hostname strings
-- Emergency rescue where the hook itself misbehaves
-
-INSTEAD of routine overrides: rewrite the commit or content. The cost is small; the discipline compounds across every future commit.
-
-## Adopter cure (one-time)
-
-Adopters running bassclef-sync after this rule ships see one-time drift. Existing `state/markers/*` files stay tracked in their index but ignored by the new .gitignore.
-
-Cure:
-
-```bash
-git rm -r --cached state/markers/
-git commit -m "chore: untrack state markers per bassclef identifier-leak-prevention rule"
-```
-
-The working-tree files stay. Only the git index changes.
-
-## Composes with
-
-- `.claude/rules/session-artifacts.md` (L14-25 — state/markers gitignore intent this rule enforces)
-- `.claude/rules/blocked-items.md` (BLOCK protocol the hook fires)
-- `.claude/rules/testing-tier-config.md` (Tier 0 strict TDD on the hook + tests)
-- `.claude/rules/hook-wire-on-author.md` (settings.json wiring discipline)
-- `.claude/rules/bootstrap-pair-discipline.md` (hook + rule + test + wire ship together)
-- `.claude/rules/we-dont-break-adopters.md` (adopter cure documented above)
-- `.claude/hooks/pre-commit-identifier-leak-scrub.sh` (mechanical implementation)
-- `.claude/hooks/tests/pre-commit-identifier-leak-scrub.test.sh` (12-test coverage)
-- @luminary saltzer-schroeder — complete mediation
-- @luminary linus-torvalds — adopter contract (ADR-031)
-- @luminary michael-feathers — characterization tests
-- @luminary michael-nygard — stability pattern (fail-soft on grep missing)
-
-## Refs
-
-- Parent ticket: sunj-labs/bassclef#1471
-- Rule intent source: `.claude/rules/session-artifacts.md` L14-25
-- Mechanism gap: `scripts/release-to-bassclef.sh` L257-289 (andon scan scoped to dirs)
-- Hostname source: `.claude/hooks/save-state.sh` L222 + L247
-
-## Retirement condition
-
-This rule retires only if bassclef stops committing content that could contain identifiers. Every commit is a potential leak surface, so retirement is unlikely. Pattern set may evolve as new operator-identifying shapes surface; the discipline of scanning at commit time persists.

package/substrate/.claude/rules/iteration-bet-brief-completeness.md

@@ -1,54 +0,0 @@
----
-tier: lite
-description: When Orchestrator (or any agent) delegates a Construction stack to a subagent (Builder, Designer, Architect), the brief MUST include, verbatim and with file paths, every artifact…
----
-
-# Iteration Goal Brief Completeness
-
-When Orchestrator (or any agent) delegates a Construction stack to a
-subagent (Builder, Designer, Architect), the brief MUST include, verbatim
-and with file paths, every artifact the iteration goal cites that applies
-to the stack's scope.
-
-## Required in every delegation brief
-
-- Canvas (if scope touches a subsystem covered by the canvas)
-- Spec or decomposition artifact
-- **All prototypes** listed in the goal's References, scoped to which apply per surface
-- ADRs the goal pins as governing constraints
-- Design token file(s) if the scope touches token-governed surfaces
-- Prior PRs that shipped shared primitives the stack should reuse
-- Luminary map (primary pair + any extended pairs tagged to surfaces in scope)
-
-## Checkpoint before spawning the subagent
-
-Before the Task/Agent call, enumerate the goal's reference list and confirm
-each relevant entry is in the brief. Missing entries = re-brief before
-spawn. In sequential mode, same checkpoint applies to the role handoff
-within a single session.
-
-## Operator- vs orchestrator-gated
-
-- **Orchestrator-gated**: Orchestrator constructs the brief and validates
-  completeness before delegation. No operator prompt required.
-- **Operator-gated**: operator may shape or override, but the default is
-  full transmission. Partial briefs require explicit operator choice.
-
-## Why this rule exists
-
-POA iteration #499 (2026-04-12): bet cited an approved prototype under
-Reference artifacts. Orchestrator delegated Stack-1 (Review Queue UI) to
-Builder with decomposition + verbal density guidance but without the
-prototype path. Builder built against decomposition only → cramped UI
-shipped → rebuild required.
-
-The goal was correct. The delegation dropped information. Every bassclef
-repo using the iteration-bet pattern has this exposure.
-
-## Relationship to other rules
-
-- `artifact-ingestion.md` — Builder's obligation to read staged artifacts;
-  this rule is Orchestrator's reciprocal obligation to surface them
-- `design-direction.md` — approvals are load-bearing; bet references
-  carry the approvals and must reach Builder intact
-- `sdlc-gates.md` — pre-build gates; brief completeness is itself a gate

package/substrate/.claude/rules/lite-manifest-schema-change-discipline.md

@@ -1,98 +0,0 @@
----
-tier: lite
-description: Every lite-manifest schema change ships a migration-note ledger entry in the same PR. Adopters read the ledger before sync.
----
-
-# Lite-manifest schema-change discipline
-
-Every change to `standards/lite-manifest.schema.json` (schema shape) or to the output shape of `<tier>-manifest.json` (extractor emissions) MUST ship with a matching ledger entry in `standards/lite-manifest-schema-changes.md` in the same PR. The release script blocks the cascade if the ledger has no entry for the outgoing `manifest_version`.
-
-This rule is the methodology layer. The mechanical layer is a pre-flight check in `scripts/release-to-bassclef.sh` (Step 3.6, added in goal 2026-09-07c Step 4). Both required.
-
-Sister discipline at the file-rename surface; same shape at a different surface — files there, schema fields here.
-
-## Why this exists
-
-`v0.36.0` (2026-09-06) dropped `upstream_commit` from lite-manifest content per sunj-labs/bassclef-upstream#1508. Three bassclef-web scripts crashed at next sync because they read `.upstream_commit` and got `undefined`. No note warned adopters. bassclef-web#269 promoted the pattern.
-
-Every adopter of the lite manifest sits on this class. Without a ledger discipline, every future schema change replays the failure.
-
-## When this rule fires
-
-Any PR that touches:
-
-- `standards/lite-manifest.schema.json` (schema shape)
-- `scripts/generate-lite-manifest.sh` in a way that changes the output shape (adds or removes emitted keys)
-
-Skips:
-
-- Content-only manifest regens (backfill helper adds descriptions to source files; content_hash changes but no schema shift)
-- Comment-only edits to schema or extractor
-
-## What the rule requires
-
-When a PR changes the manifest schema OR output shape:
-
-1. **Ledger entry** — add a new entry to `standards/lite-manifest-schema-changes.md` in the same PR. Format per the ledger's format section. Newest-first ordering.
-2. **Version bump** — pin the entry to a specific `manifest_version` bump. Per the schema title description policy:
-   - Adding an optional field → MINOR bump
-   - Adding a required field → MAJOR bump (breaking)
-   - Removing a field → MAJOR bump
-   - Content-only change → PATCH bump
-3. **Downstream cure named** — the entry names what adopters need to do. If nothing (backward-compatible add), say so explicitly. If code change (like the v0.36.0 `upstream_commit` removal), name the pattern.
-4. **Release script pre-flight** — before every `/release`, the script reads the ledger and confirms an entry exists for the outgoing `manifest_version`. Missing entry BLOCKs the cascade.
-
-## Anti-patterns
-
-**Schema field added but no ledger entry.** Release script pre-flight BLOCKs.
-INSTEAD: add the entry in the same PR.
-
-**Ledger entry written but wrong version bump.** Adopters plan their pin update against the wrong version.
-INSTEAD: correct the bump before merge. AJV validation of the entry format catches inconsistency.
-
-**Downstream cure vague (no name for the class).** Adopters at cold-sync can't reason about which script needs fixing.
-INSTEAD: cite the class + link to a reference cure like bassclef-web c9a9da7.
-
-**Schema change ships without adopter coordination.** Even with a ledger entry, adopters that exact-pin the manifest_version need advance warning.
-INSTEAD: coord comment on bassclef-web#256 + bassclef-cli#51 BEFORE the release cascade per Linus L6 pre-mortem cure.
-
-## Override
-
-`SKIP_LITE_MANIFEST_SCHEMA_LEDGER=1 <command>` — logged via trace-helper. Use only when:
-
-- The schema change is a comment-only edit that keeps the shape stable
-- The change reverses a prior entry (a rollback) and the prior entry names both the change and the rollback
-- One-shot migration script that touches the schema during a migration window
-
-INSTEAD of overriding for routine work: write the entry. The cost is small (one section in the ledger); the discipline compounds across every adopter that syncs.
-
-## Composes with
-
-- file-rename-discipline (standard tier) — sister at the file surface
-- `.claude/rules/we-dont-break-adopters.md` — parent discipline (ADR-031)
-- `.claude/rules/cold-adopter-harness-discipline.md` — sibling smoke fires against ledger entries before release
-- `.claude/rules/bootstrap-pair-discipline.md` — this rule + hook + tests + settings wire ship together
-- `.claude/rules/testing-tier-config.md` — Tier 0 strict TDD on ledger format tests
-- `.claude/rules/blocked-items.md` — BLOCK protocol the release-script pre-flight fires
-- `standards/lite-manifest.schema.json` — the schema this ledger tracks
-- `standards/lite-manifest-schema-changes.md` — the ledger this rule enforces
-- `scripts/release-to-bassclef.sh` — release-script pre-flight (Step 3.6)
-- ADR-031 (we-don't-break-adopters)
-- ADR-029 (release pipeline)
-- @luminary linus-torvalds — lead. Adopter contract; the ledger is the operational form of Torvalds's rule at the schema surface
-- @luminary tony-hoare — pre/postcondition contract on schema changes
-- @luminary michael-nygard — stability pattern (block-on-missing-entry)
-- @luminary michael-feathers — characterization test on the ledger format
-
-## Refs
-
-- Parent ticket: sunj-labs/bassclef-web#269 (promote: ship migration notes when lite-manifest schema removes or renames fields)
-- Root cause: v0.36.0 upstream_commit removal broke 3 bassclef-web scripts (commit `c9a9da7` on bassclef-web repaired downstream)
-- Goal: `docs/iteration-bets/2026-09-07c-lite-manifest-schema-plus-extractor-plus-backfill-plus-ledger.md`
-- Risk ledger: `docs/risk-ledgers/2026-09-07c-lite-manifest-schema-extractor-backfill-ledger.md` Linus L6 + Hoare H6
-- Sister rule: file-rename-discipline (standard tier)
-- @luminary linus-torvalds — Torvalds's rule at the schema surface
-
-## Retirement condition
-
-This rule retires only if bassclef stops shipping a lite manifest. Adopter count and change cadence may evolve; the discipline of documenting every schema change at the PR that ships it persists.

package/substrate/.claude/rules/longrun-prep-plan-doc-compression.md

@@ -1,89 +0,0 @@
----
-tier: lite
-description: When a plan doc at docs/next-session-plan-*.md (modified within 48 hours) carries a ## Recommended session sequence (or equivalent) section, /longrun prep MUST skip the full Steps…
----
-
-# /longrun prep — compress when plan doc pre-picks scope
-
-When a plan doc at `docs/next-session-plan-*.md` (modified within 48 hours) carries a `## Recommended session sequence` (or equivalent) section, `/longrun prep` MUST skip the full Steps 1.4c-1.7b option-table ceremony and present the pre-authored sequence directly. This rule closes bassclef-upstream#1307 R1 — the workflow-overhead class where prep re-authors 15-25 turns of ceremony an earlier session already shipped in a plan doc.
-
-This rule is the methodology layer. The mechanism is the /longrun SKILL body Step 0.85 (bassclef-upstream#1307 R1). V2 Stop-hook enforcement is deferred per pre-mortem R5.
-
-## When this rule fires
-
-Every `/longrun prep` dispatch. The SKILL body Step 0.85 checks for a plan doc first. When one is found, the compressed prep path fires. When none matches, the full ceremony holds.
-
-Detection criteria (all three must match):
-
-1. File matching `docs/next-session-plan-*.md` exists at repo root
-2. File was modified within the last 48 hours (`find -mtime -2`)
-3. File body contains one of: `## Recommended session sequence`, `## Recommended sequence`, `## Next-session pickup`
-
-## What the compressed path requires
-
-When the compressed path fires, prep still ships the three-block opener per `.claude/rules/operator-facing-prose.md` Rule 3 (Problem + Value + Evidence). The compression targets Steps 1.4c-1.7b:
-
-- **Skip:** re-authoring the full 5-axis-per-option block for every option (SKILL Step 1.5)
-- **Skip:** re-authoring a full card for every non-recommended option (SKILL Step 1.6)
-- **Skip:** re-authoring step cards + per-step compounding blocks (SKILL Steps 1.7 + 1.7a) for options the plan doc did not recommend
-- **Keep:** scan-table at the top (3-5 rows summarizing the plan doc's items)
-- **Keep:** one card for the recommended item per SKILL Step 1.6
-- **Keep:** step cards + per-step compounding for the recommended item only per SKILL Steps 1.7 + 1.7a
-- **Keep:** recommendation sentence per SKILL Step 1.7b
-- **Add:** plan doc file path cited inline as source
-
-Operators still pick from the scan table. The plan doc's ranking becomes the default, not a mandate.
-
-## Anti-patterns
-
-**Full ceremony fires despite plan doc present.** The exact class #1307 R1 filed. Cure: run the SKILL Step 0.85 detection first.
-
-**Plan doc detection succeeds but prep still authors 5-axis blocks for every option.** Partial compression is not compression. Cure: skip the per-option 5-axis blocks; keep them only for the recommended item's card.
-
-**Compressed prep drops the recommendation sentence.** Operators still need one-line rationale. Cure: keep Step 1.7b.
-
-**Compressed prep skips the three-block opener.** Rule 3 discipline holds regardless of compression. Cure: Problem + Value + Evidence always land before scan-table.
-
-INSTEAD of any of these: check for plan doc first (SKILL Step 0.85 detection); use the recommended sequence verbatim; ask operator to confirm or reshape.
-
-## Override
-
-`SKIP_LONGRUN_COMPRESS=1 <command>` — logged via trace-helper. Use only when the plan doc is out of date and the operator wants a fresh option set. In that case, dispatch full ceremony and note the override reason in the prep opener.
-
-INSTEAD of overriding routinely: update the plan doc. A stale plan doc is a bad plan doc; fixing it upstream compounds across every future prep.
-
-## V2 mechanical layer (deferred)
-
-V1 ships this rule + SKILL body Step 0.85 amendment. V2 (deferred follow-on ticket) will add a Stop hook that:
-
-1. Detects `/longrun prep` output in the assistant's most recent message
-2. Detects presence of a fresh plan doc via `find -mtime -2`
-3. Checks whether the prep output carries 3+ per-option 5-axis blocks (evidence of full ceremony)
-4. Emits ADVISORY finding when full ceremony fires despite plan doc being present
-
-Defer V2 until this rule (V1 methodology) has shipped through 3-5 preps and the mechanical extension has stable heuristics.
-
-## Composes with
-
-- `.claude/skills/longrun/SKILL.md` Step 0.85 — the SKILL amendment this rule prescribes
-- `.claude/rules/operator-facing-prose.md` Rule 3 — three-block opener still fires under compression
-- `.claude/rules/compounding-sequence-fresh-analysis.md` — per-option 5-axis fresh analysis still holds for the recommended item's card
-- `.claude/rules/plan-enumeration-needs-value-props.md` — every option in the compressed scan-table still carries a value-prop cell
-- `.claude/rules/blocked-items.md` — silence is not deferral (plan doc detection reports fire vs skip explicitly)
-- `.claude/rules/bootstrap-pair-discipline.md` — this rule + SKILL amendment ship as paired bootstrap
-- @luminary john-ousterhout — deep module (compression path hides plan-doc detection behind narrow interface)
-- @luminary donald-norman — signifier + feedback (plan doc presence is a signifier; compressed vs full ceremony is user feedback)
-- @luminary frederick-brooks — conceptual integrity (compression preserves the option-table + card + step-card shape; only volume shrinks)
-
-## Refs
-
-- bassclef-upstream#1307 R1 — this rule's filing ticket
-- `docs/next-session-plan-2026-08-20.md` — the plan doc that motivated the R1 class filing
-- operator_recap_2026-08-19e L96 — evidence source (25-40t ceremony vs 5t needed)
-- `.claude/skills/longrun/SKILL.md` Step 0.85 — mechanism this rule prescribes
-
-## Retirement condition
-
-This rule retires only if `/longrun` stops accepting plan docs as pre-authored scope. Until then, the discipline of compressing prep against pre-authored sequences survives.
-
-Closes bassclef-upstream#1307 R1.

package/substrate/.claude/rules/loop-discipline.md

@@ -1,81 +0,0 @@
----
-tier: lite
-description: Every step that ships code or substrate runs the six-step cycle for shipping code or substrate.
----
-
-# /loop discipline — methodology layer
-
-Every step that ships code or substrate runs the six-step cycle below. This rule is the methodology layer; the full cycle spec lives with operator substrate.
-
-## When this rule fires
-
-The rule fires when an agent or operator opens a feature branch, commits, opens a PR, runs review, or merges. The discipline applies regardless of work scope — single-issue fix, multi-step /longrun, and substrate-defect filing all run the same six steps.
-
-## What the rule requires
-
-Before merging a PR that touches code or substrate, the agent has done all six main steps plus three sub-steps:
-
-0.5. `/pre-mortem` light fired (3 luminary lenses, 5-8 risks per lens, 30 min per Klein workshop shape) BEFORE Step 1 /temperance. Marker exists at `state/markers/pre-mortem/<branch-slug>.marker` citing the risk ledger path. Strongest concerns fold into the plan before edits begin. Per `.claude/skills/pre-mortem/SKILL.md` light mode.
-1. `/temperance` fired with answers stated (smallest shape, blast radius, brute-force check). Marker exists at `state/markers/temperance/<branch-slug>.marker`.
-2. `/luminary` picked at least one primary lens. Marker exists at `state/markers/luminary/<branch-slug>.marker`. Slugs recorded in the evidence row's `authoring_luminaries` field.
-2a. Marker declares `lead` field naming one primary luminary; `supporting` field lists the others. Lead is the luminary whose lens verifies the ship at Step 5.5. Format mirrors bet-doc frontmatter `authoring_luminaries.primary` and `.supporting`.
-3. Tier 0 strict TDD satisfied where the testing tier requires it. Tests pass. The `testing-tier-enforce` hook has not blocked the commit.
-4. Review run. Findings categorized as red, amber, green, note. CodeReviewer agent dispatched OR inline review with luminary lens applied.
-5. Red and amber findings resolved through one or more iterations. Iteration count recorded. When the change is a SKILL body rewrite (any file under `.claude/skills/*/SKILL.md`), the intent check is measurable — run `scripts/intent-drift-check.sh --skill <slug>`. Cosine at or above 0.90 versus the saved vector at `.claude/embeddings/skills/<slug>.json` passes. Cosine below threshold means intent drifted and the rewrite iterates or reverts. Subjective promise-list checks satisfy the step ONLY when no saved vector exists (new skill). Threshold raised from 0.85 to 0.90 per #790 (2026-07-19) after first-6-cures median landed at 0.987.
-5.5. Lead lens confirms all red and amber findings cleared before Step 6 merge. Marker exists at `state/markers/lead-lens-signoff/<branch-slug>.marker` naming the lead luminary and either "no findings" or the specific finding IDs cleared. Rubber-stamp sign-off is a discipline miss — sign-off must cite finding IDs or state "no findings" with rationale.
-6. PR body carries the structured evidence including the three markers from Steps 0.5, 2a, 5.5. Squash merge. Evidence row status flips to merged.
-
-Silence at any step is not deferral. Explicit deferral with stated rationale is the only acceptable skip.
-
-The three sub-steps (0.5 + 2a + 5.5) close the aggregate-GREEN balancing check gap named in #845 body Cure B. When every gate reports GREEN independently but the fix ships in the wrong shape, the missing signal is a balancing check — a lens that reads the aggregate and asks "does this actually solve the problem." The lead luminary IS the balancing check. Ships per #836.
-
-## What this rule does NOT require
-
-- A specific number of luminaries (one minimum; five maximum per `/luminary` skill ceiling).
-- A specific finding count (red and amber findings should exist; zero on every PR signals shallow review).
-- A specific iteration count (zero is acceptable when first review is clean).
-- The CodeReviewer agent specifically — inline review with luminary lens is acceptable for smaller scope.
-- A standalone evidence document. Tier 1 evidence rows live in PR body sections; tier 0 in standalone files. Both satisfy the rule.
-
-## Skip path with explicit deferral
-
-Some work skips part of the cycle by declaration:
-
-- **Trivial change** — typo, dependency bump, single-line rename. Commit message line `loop: skipped — trivial change, no review surface` records the skip.
-- **Documented emergency** — production incident with operator-approved bypass. PR body carries authorization.
-- **Operator direct merge** — operator authors the change and merges. The discipline applies to the agent work that surfaces it, not to the operator's edit.
-
-Silence is not skip. Default is run the cycle.
-
-## Composes with
-
-- `standards/construction-evidence-discipline.md` — the artifact produced per cycle
-- `.claude/rules/testing-tier-config.md` — step 3 enforcement
-- `.claude/rules/wu-sequencing-compounds.md` — sister discipline at the multi-step bet level
-- `.claude/rules/blocked-items.md` — the protocol for surfacing skipped steps that should have run
-- `.claude/skills/pre-mortem/SKILL.md` — Step 0.5 method; light mode shape (3 lenses, 30 min)
-- `.claude/luminaries/gary-klein.md` — Step 0.5 anchor (pre-mortem originator)
-
-## Mechanical enforcement
-
-V1 ships this rule + the standard. V2 (deferred) extends `pre-commit-gate.sh` to verify both markers exist for the branch before any commit, and adds a PR-open hook that verifies the evidence section is present in the PR body.
-
-Per memory `feedback_hooks_beat_methodology_for_substrate_quality`: V2 hook ships alongside the methodology — both required for the discipline to hold across context boundaries.
-
-## Override path
-
-`SKIP_LOOP_DISCIPLINE=1 <command>` — logged via trace-helper. Use only for migration scripts that author many goal docs at once, or for emergency rescue. Routine skip is not an override target; routine skip is a methodology miss.
-
-## Source dialogue
-
-2026-06-23 overnight bet 23a (discipline mechanization three disciplines). The loop was exercised on every step during the goal; this rule and the companion standard codify what the goal did.
-
-## Refs
-
-- goal doc `docs/iteration-bets/2026-06-23a-discipline-mechanization-three-disciplines.md` — the goal that ran the loop and proved the discipline
-- `.claude/luminaries/kent-beck.md` — primary lineage (red-green-refactor)
-- `.claude/luminaries/gary-klein.md` — Step 0.5 pre-mortem lineage
-- Memory `feedback_hooks_beat_methodology_for_substrate_quality` — pattern for V2 mechanical layer
-- Ticket 836 — parent filing (three sub-steps + hook extension)
-- Ticket 845 — Cure B (aggregate-GREEN balancing check) — Step 5.5 lead-lens sign-off ships that cure
-- Goal doc `docs/iteration-bets/2026-07-24a-ship-836-loop-discipline-extension.md` — ship vehicle for the three sub-steps