@thebassclef/lite 1.0.4 → 1.1.0

package/dist/lite/standards/tier-tag-schema.md

@@ -0,0 +1,155 @@
+---
+tier: lite
+description: Per-file maturity-signal field that governs flow from bassclef-upstream (upstream experimental) → bassclef (public hardened release mirror).
+---
+<!-- andon-allow: operator-private -->
+<!-- andon-allow: bassclef-upstream -->
+
+# Tier-tag schema
+
+Per-file maturity-signal field that governs flow from `bassclef-upstream` (upstream experimental) → `bassclef` (public hardened release mirror). The release script (`scripts/release-to-bassclef.sh`) reads this field on every substrate primitive and decides whether to include it in the release.
+
+## Field
+
+- **Name:** `tier`
+- **Location per file type** (extended 2026-08-17 per ADR-052 D6):
+  - `.md` files (skills, luminaries, rules, ADRs, standards): YAML frontmatter, recommended as the first line after the opening `---`
+  - `.sh` files (hooks, scripts): header comment `# tier: <value>` on line 2 (after the shebang)
+  - `.yml`, `.yaml` files: comment `# tier: <value>` on line 1
+  - `.jsonc` files: line comment `// tier: <value>` on line 1
+  - `.json` (pure) files: underscored key `"_tier": "<value>"` in the top object (underscore signals metadata field per common convention)
+  - LICENSE, plain text: external entry in `standards/tier-file-allowlist.json`
+- **Values (extended 2026-08-17 per ADR-043 D1 amendment):** `upstream | archive | unknown | lite | standard | standard-pro | ultra`
+- **Default for untagged legacy files:** untagged .md and .sh files BLOCK release per #1209. Untagged JSON / YAML / LICENSE ship by default via ALLOWED_PATHS (per `scripts/release-to-bassclef.sh:508-513`).
+- **Required on:** skills, rules (enforced by `substrate-clarity-gate.sh`). Luminaries, hooks, ADRs, standards SHOULD carry it; strict enforcement deferred to a follow-on.
+
+## Scope — where the field applies
+
+The `tier:` field applies to substrate building-block surfaces whose maturity governs release-script filtering. It does not apply to documentation surfaces that ship unconditionally.
+
+**Applies to (field required or SHOULD carry):**
+
+| Surface | Path pattern | Enforcement |
+|---|---|---|
+| Skills | `.claude/skills/*/SKILL.md` | `substrate-clarity-gate.sh` BLOCKs if missing |
+| Rules | `.claude/rules/*.md` | `substrate-clarity-gate.sh` BLOCKs if missing |
+| Luminaries | `.claude/luminaries/*.md` | SHOULD carry; strict enforcement deferred |
+| Agents | `.claude/agents/*.md` | SHOULD carry; strict enforcement deferred |
+| Hooks | `.claude/hooks/*.sh` | SHOULD carry; strict enforcement deferred |
+| ADRs | `architecture/decisions/ADR-*.md` | SHOULD carry; strict enforcement deferred |
+| Standards | `standards/*.md` | SHOULD carry; strict enforcement deferred |
+| Strategy | `strategy/*` | SHOULD carry; strict enforcement deferred |
+
+These paths match the building-block list in `scripts/release-to-bassclef.sh:254-263`. The release script reads the field per file and filters accordingly.
+
+**Does NOT apply to (field MUST NOT appear):**
+
+| Surface | Path pattern | Enforcement |
+|---|---|---|
+| Release notes | `docs/release-notes/*.md` | `substrate-clarity-gate.sh` BLOCKs if `tier:` present |
+| Roadmaps | `docs/roadmaps/*.md` | `substrate-clarity-gate.sh` BLOCKs if `tier:` present |
+| Canvases | `docs/canvases/*.md` | `substrate-clarity-gate.sh` BLOCKs if `tier:` present |
+
+These paths ship unconditionally via the release script's fallback branch (`scripts/release-to-bassclef.sh:367-372` — "ship per allowed-path. No per-file tier needed"). Adding `tier:` there signals a distribution filter that does not exist.
+
+**Rationale.** Per /luminary consult 2026-07-31 (Norman signifier discipline + Brooks conceptual integrity + Linus adopter contract): a field with two meanings across the substrate breaks coherence. A field that signals distribution but does not filter distribution misleads readers. Documentation surfaces describe shipped work; they are not themselves substrate building blocks whose maturity gates release.
+
+**Legacy sweep.** Two release-notes shipped with `tier: standard` before this scope was clarified: `docs/release-notes/2026-07-10-v0.2.0.md` and `docs/release-notes/2026-07-10-v0.2.1.md`. Both swept in the same PR that added this Scope subsection.
+
+## Value semantics
+
+| Value | Ships in release? | Meaning to adopter |
+|---|---|---|
+| `private` | **No** | Operator-private even outside `docs/operator-private/`. Belt-and-braces per-file gate. |
+| `lite` | Yes | Early-access; minimal viable; expect rough edges. Signals "use it, file issues, expect change." |
+| `standard` | Yes (bassclef + bassclef-ultra) | Portfolio operator's product; adds atomic skills lite embeds. Ships in bassclef + bassclef-ultra. NOT in bassclef-lite. |
+| `standard-pro` | Conditional (with license key) | Extends `standard` with pre-release content. Ships to adopters whose `.bassclef-source.json` carries `tier_extension: standard-pro` AND `license_key`. Added bet 24b Step 2 (goal 20a Task 3.2). Iteration 3 wires the gate; Iteration 1 accepts the tag only. |
+| `ultra` | Yes (bassclef-ultra only) | Reflective intelligence; Voyage-driven skills. Ships in bassclef-ultra only. |
+| `archive` | **No** | Kept for historical reference or debugging. Not part of active development. Filters out at release. Added 2026-08-17 per ADR-043 D1 amendment. |
+| `unknown` | **No** | Awaiting operator triage. Not yet classified. Filters out at release. Should be resolved. Added 2026-08-17 per ADR-043 D1 amendment. |
+
+## Maturity progression (lite → standard → ultra)
+
+Promotion is **communicative, not mechanical.** A primitive that's ready for the next tier gets the frontmatter edited in a normal commit. The release script ships everything that isn't `private`; the tier name tells adopters how mature the file is.
+
+```
+new primitive  →  lite  →  standard  →  ultra
+                    ↓        ↓           ↓
+              ships, with maturity signal in name
+```
+
+There is no separate `/promote --tier-up` skill; if one is needed it'll be added when the operator notices friction.
+
+## Gating
+
+**Note (2026-08-17):** amended per ADR-052 D1 — concentric inclusion is the model. Each product ships every file tagged at a smaller-tier value plus its own value.
+
+The release script per tier:
+
+1. Reads `tier:` per file per format (see "Tier tag per file format" below)
+2. If `tier ∈ {private, upstream, archive, unknown}` → **exclude from every downstream release**
+3. If `tier == lite` → include in bassclef-lite + bassclef + bassclef-ultra
+4. If `tier == standard` → include in bassclef + bassclef-ultra (NOT bassclef-lite)
+5. If `tier == standard-pro` → include only when adopter carries `tier_extension: standard-pro` + `license_key`
+6. If `tier == ultra` → include in bassclef-ultra only
+7. If `tier == <anything else>` → refuse the release with "INVALID tier" error
+8. If `tier == <empty>` on ANY file inside ALLOWED_PATHS → BLOCK release (add a tier tag per file format)
+
+## Tier tag per file format
+
+Every file format that ships (or could ship) inside ALLOWED_PATHS carries a tier tag in a format the file's parser accepts:
+
+| Format | Tag mechanism | Example |
+|---|---|---|
+| `.md` | YAML frontmatter `tier: X` | `---\ntier: lite\n---` |
+| `.sh`, `.py` | header comment `# tier: X` (line 2 after shebang) | `#!/usr/bin/env bash\n# tier: standard` |
+| `.json` (data files) | top-level `"_tier": "X"` field | `{"_tier": "upstream", "data": ...}` |
+| `.json` (JSON Schema files) | `"$comment": "tier: X"` — because `$comment` is a recognized draft-2020-12 keyword; top-level unknown keys fail ajv strict mode | `{"$comment": "tier: standard", "$schema": ...}` |
+| `.jsonc` | header comment `// tier: X` | `// tier: standard\n{...}` |
+| `.yml`, `.yaml` | frontmatter `tier: X` OR header comment `# tier: X` | `---\ntier: lite\n---` |
+| Other text | header comment appropriate to format | — |
+
+Non-taggable formats (binary files) go into `standards/tier-file-allowlist.json` external allowlist per ADR-052 D6.
+
+Prior default-ship rule for non-md/sh files (superseded by this table 2026-08-20 per Wave 4 Option C Step 4): removed. Every file inside ALLOWED_PATHS now carries an explicit tag per format.
+
+## Defense in depth — path exclusion registry
+
+Files whose path matches an entry in `standards/path-exclusion-registry.json` are excluded from every release regardless of any inner `tier:` value. The path wins. Consumers (release script, audit tools) read the registry as the single source of truth for path-based exclusion classes: `session-runtime`, `operator-private`, `test-only`, `operator-internal-rd`, `prototype`, `config-per-repo`, `ephemeral-transient`.
+
+The path exclusion registry (operator-only) tracks classes + rationale per entry + how to add a new exclusion.
+
+The path-exclusion registry supersedes the prior inline `case` statement in `scripts/release-to-bassclef.sh` L415-460. The refactor to read the registry ships as a separate PR after this schema amendment.
+
+## Validation
+
+The `substrate-clarity-gate.sh` hook enforces on skill + rule edits:
+1. `tier:` present (BLOCK if missing)
+2. `tier:` value ∈ `{private, lite, standard, standard-pro, ultra}` (BLOCK if other value)
+3. `tier:` accepted as a recognized field (no `UNKNOWN_FIELDS` warning)
+
+The `bassclef-source-config-validate.sh` hook validates `.bassclef-source.json` `tier_extension` field against the same enum (minus `private` — adopters cannot opt into private content).
+
+Override hatches:
+- `SKIP_SUBSTRATE_CLARITY=1` (full hook bypass; logged via trace-helper)
+- Allowlists: `.claude/hooks/substrate-clarity-allowlist.txt`, `.claude/hooks/substrate-frontmatter-allowlist.txt`
+
+## Backfill provenance
+
+- 392 primitives initially backfilled with `tier: public` 2026-06-21 (WU-1 commits 73c8fce + bc00f99 + e28d73f)
+- 36 luminaries added to bassclef-upstream 2026-06-21 with `tier: public` (commit 54a65aa, WU-0 gap fix)
+- 9 presence files added 2026-06-21 with `tier: public` (commit cf53a5f)
+- All `tier: public` → `tier: standard` 2026-06-21 (commit TBD this session) per operator's rename to lite/standard/ultra vocabulary
+
+## Relationship to other tier concepts
+
+- `tiers:` (plural, in skill frontmatter): skill MODES like `[medium, full]` for /launch sizes. Distinct from `tier:` (release maturity).
+- `model_tier:` (in skill frontmatter): which Claude model the skill prefers. Distinct from `tier:`.
+
+## See also
+
+- `architecture/dual-repo-flow.md` — the full architecture this tier field operationalizes
+- `architecture/decisions/ADR-029-release-pipeline.md` — formalizes the release script that consumes this field
+- `architecture/decisions/ADR-030-adopter-inbox-flow.md` — the ingestion direction; doesn't read tier but operates inside the same bounded-context model
+- `scripts/release-to-bassclef.sh` — the consumer
+- `.claude/hooks/substrate-clarity-gate.sh` — the gate that enforces this field on skill + rule

package/dist/lite/standards/two-layer-config.md

@@ -0,0 +1,99 @@
+---
+tier: lite
+description: "Bassclef's config splits into two layers."
+---
+
+# Two-Layer Config — Shared vs Operator
+
+Bassclef's config splits into two layers. The **shared layer** is committed and identity-agnostic — every adopter sees it. The **operator layer** is gitignored and per-person — never committed, never shipped to adopters.
+
+This standard exists because the line between "what bassclef needs" and "what one operator has set up" was blurry before the 2026-05-23 cold-adopter run. Operator-specific paths, allow lists, and preferences leaked into shared config. Adopters would have inherited the operator's identity on first clone.
+
+## The two layers
+
+### Shared layer (committed)
+
+- `.claude/settings.json`
+- `CLAUDE.md`
+- `README.md`
+- All skills, hooks, rules, standards under `.claude/` and root dirs
+- All ADRs, decompositions, design docs
+
+**Rules for the shared layer:**
+
+1. Identity-agnostic. No absolute paths to specific home directories.
+2. No personal allow-list entries (broad npm grants, macOS process control, etc.).
+3. No "sunj-labs" references except in attribution.
+4. Tested against cold-adopter personas (`strategy/personas/`) before publication.
+
+### Operator layer (gitignored)
+
+- `.claude/settings.local.json`
+- `CLAUDE.local.md` (optional, if operator wants per-machine context)
+- `.env.local`
+- Anything ending in `.local`
+
+**Rules for the operator layer:**
+
+1. Holds operator-specific allow lists, machine paths, personal aliases.
+2. Never committed. `.gitignore` enforces this by listing the files explicitly.
+3. Each contributor creates their own. The shared `.gitignore` block tells them which files to create.
+4. Where convenience accumulates — broad `Bash(rm *)` grants, machine-specific paths, etc.
+
+## Mechanical enforcement
+
+`.claude/hooks/pre-commit-gate.sh` includes a CCF-3 absolute-path guard. It runs on every `git commit` and BLOCKs when any staged non-exempt file contains `/Users/<name>` or `/home/<name>` patterns.
+
+**Exempt paths** (where these patterns are legitimate — documentation, audits, test fixtures):
+
+- `.claude/rules/`, `.claude/hooks/`, `.claude/skills/`, `.claude/luminaries/`, `.claude/agents/`
+- `standards/`, `architecture/`, `design/`
+- `docs/` (all subdirs)
+- `chronicle/`, `strategy/`
+- `scripts/tests/`
+
+**Non-exempt** (where the guard fires): everything else. Most importantly `.claude/settings.json`, top-level configs, source code under `src/` or `lib/`.
+
+When the guard fires, it points to `.claude/settings.local.json` as the right home for the offending entry.
+
+## Override
+
+`SKIP_OPERATOR_PATHS=1 git commit` — logged via `trace-helper.sh`. Use only for genuine cases where the absolute path must live in the shared layer (rare). Document the rationale in the commit message.
+
+## What this fixes
+
+Before this standard:
+
+- `.claude/settings.json` shipped `Bash(rm /Users/<operator>/src/<org>/bassclef/*)` — F70 in the 2026-05-23 cold-adopter run. Every public clone would have inherited that operator-identity line.
+- Allow-list entries reflected operator workflow rather than adopter safety — F73 in the same run.
+
+After this standard:
+
+- F70 is removed from the committed `.claude/settings.json`.
+- The hook prevents the class from recurring.
+- New operator-convenience entries go to `.claude/settings.local.json`.
+
+## When to add a new field to the operator layer
+
+Any of these signals mean it belongs in `settings.local.json`, not `settings.json`:
+
+- Contains an absolute path matching `/Users/<name>` or `/home/<name>`.
+- Grants a broad permission (`Bash(rm *)`, `Bash(npm*)`, `Bash(pkill*)`) that an adopter on a first session would not be expected to want.
+- References operator-specific tools or paths (`/Applications/Tailscale.app/...`).
+- Encodes machine-specific config (hostnames, ports tied to a specific dev setup).
+
+When in doubt, default to the operator layer. It's cheaper to promote a setting from `settings.local.json` to `settings.json` later than to ship operator identity to every adopter.
+
+## Sources read
+
+- `docs/adoption-runs/2026-05-23-cold-adopter-1.md` — the cold-adopter run record (PR #735)
+- Operator handoff CCF-3 + Step 5 Issue 4 — the policy specification
+- F70 (operator path leak in committed `.claude/settings.json`)
+- F73 (allow-list grants reflect operator workflow rather than adopter safety)
+- `.claude/hooks/pre-commit-gate.sh` — the mechanical enforcement
+- `.claude/rules/blocked-items.md` — the resolve-or-defer protocol the BLOCKED signal slots into
+
+## Closes
+
+- bassclef#740 (CCF-3 — two-layer config policy)
+- bassclef#738 (Pre-launch cleanup — F70 instance)

package/dist/lite/standards/use-case-format.md

@@ -0,0 +1,292 @@
+---
+tier: lite
+description: - Alistair Cockburn — Writing Effective Use Cases (2000).
+---
+
+## Sources read
+
+- Alistair Cockburn — *Writing Effective Use Cases* (2000). Bassclef source for fully-dressed format, goal levels, extension enumeration, preconditions + guarantees, stakeholders + interests.
+- Alistair Cockburn — *Unifying user stories, use cases, and story maps* (2024). Artifact non-overlap (use-case ≠ user-story ≠ task-scenario ≠ story-map); this standard respects the boundaries.
+- `.claude/skills/use-case/SKILL.md` — the skill that produces this artifact; this standard codifies the format the skill emits.
+- `standards/user-story-invest.md` — sibling standard; user-stories slice use-case lines with traceability back. INVEST validation there is orthogonal to Cockburn validation here.
+- `standards/persona-schema.md` — primary-actor field MUST reference a persona slug per this schema.
+
+## What I'm NOT reading (with reason)
+
+- RUP, Jacobson "Use Case 2.0," and other use-case notation variants — Cockburn is the bassclef shape in sunj-labs per this standard. Alternatives may be adopted later with an explicit ADR.
+
+# Use-Case Format Standard
+
+Bassclef format for use cases in sunj-labs repos. The contract the
+`/use-case` skill writes and every downstream consumer
+(`/user-stories`, `/interaction-design`, `/decompose`, `/verify`,
+`/spec`) composes against.
+
+Template: `templates/use-case-template.md`.
+Skill: `.claude/skills/use-case/SKILL.md`.
+
+## Why this standard exists
+
+Before /use-case, the user-centric chain had:
+
+- `/jtbd-tasks` — WHY (job the product is hired for)
+- `/task-scenarios` — CONTEXT (narrative day-in-the-life)
+- `/user-stories` — WHAT (backlog tokens, INVEST-shaped)
+- `/decompose` — HOW (responsibilities + patterns)
+
+Missing: **goal-level behavior spec**. `/user-stories` slices
+goals into INVEST-sized increments, but stories don't enumerate
+alternate flows systematically. `/interaction-design` renders
+flows as diagrams, but diagrams permit free-form omission —
+nothing forces the designer to list every extension.
+
+Use cases close the gap. Cockburn's format *requires* extension
+enumeration (1a, 1b, 2a, 2b...), *requires* preconditions and
+postconditions, *requires* stakeholders-and-interests. The
+skill can't emit a valid use case without those fields, so
+cross-cutting concerns (audit, compliance, rate limits) can't
+be silently dropped on the way to `/decompose`.
+
+## File convention
+
+### Preferred path
+
+`docs/use-cases/UC-NNN-{slug}.md` — one file per use case.
+
+`NNN` is a zero-padded 3-digit number assigned in creation order.
+`{slug}` is URL-safe: lowercase, hyphens, no spaces. Slug MUST
+match a form of the goal (e.g., `sign-in-with-email` not
+`login` — avoids ambiguity when multiple auth flows coexist).
+
+### Matrix
+
+`docs/use-cases/_matrix.md` — traceability table with one row
+per use case. See `/use-case` skill Step 7 for columns.
+
+## Required fields
+
+Every use case MUST include these fields. The skill validates
+presence and emits WARN/BLOCK per the validation matrix below.
+
+### Header
+
+```markdown
+# UC-NNN — [imperative goal title]
+```
+
+The title is the goal statement, imperative mood, no period.
+Examples: `UC-001 — Sign in with email and password`,
+`UC-014 — Submit an expense for approval`.
+
+### Metadata block
+
+```markdown
+- **Primary actor**: [persona-slug]
+- **Goal level**: ☁️ summary | 🎯 user-goal | 🐟 subfunction
+- **Scope**: [system-under-design]
+- **Status**: draft | accepted | deprecated
+- **Last validated**: YYYY-MM-DD
+```
+
+**Primary actor** MUST be a persona slug from `docs/personas/` or
+equivalent. "User," "actor," or role words like "admin" without a
+persona file are WARN.
+
+**Goal level** exactly one of the three icons. Default ☁️/🎯/🐟
+per `/use-case` Step 2. Summary only for multi-session goals;
+subfunction only for reused-by-2+ use cases.
+
+**Scope** names the system boundary: `POA web UI + auth service`,
+`bassclef-sync hook`, `POA backend`. Fuzzy scope ("the app") is
+WARN — split into distinct use cases.
+
+### Stakeholders + interests
+
+```markdown
+## Stakeholders + interests
+
+| Stakeholder | Interest |
+|-------------|----------|
+| [stakeholder] | [what they want to be true about this goal's execution] |
+```
+
+At least **2 non-actor** stakeholders required. Non-actor means:
+not the primary actor. Examples: Compliance, Ops, Support, Billing,
+Legal, Security, Partners, Regulators, Operator/Admin.
+
+This block is load-bearing — it's what feeds `/decompose`'s -ility
+audit. A use case with only the primary actor listed will pass
+validation with a WARN but will produce a decomposition missing
+cross-cutting concerns. The skill will flag the WARN explicitly.
+
+### Preconditions + guarantees + trigger
+
+```markdown
+## Preconditions
+- [state invariant 1]
+- [state invariant 2]
+
+## Minimal guarantees
+- [what's true after, regardless of success/failure]
+
+## Success guarantees
+- [what's true after a successful run]
+
+## Trigger
+- [event that starts the use case]
+```
+
+**Preconditions** are checkable state invariants the use case
+assumes on entry. "The system is running" is throat-clearing, not
+a precondition — reject as WARN. Valid preconditions: "account
+exists," "user is authenticated," "quota below limit."
+
+**Minimal guarantees** hold on ANY exit (success or extension):
+typically audit logging, state consistency, no secret leakage.
+This is where the "audit-trail written even on failure" invariant
+gets recorded.
+
+**Success guarantees** hold on successful completion only.
+
+**Trigger** is the specific event (actor action, scheduled event,
+external signal) that starts the flow.
+
+### Main success scenario
+
+```markdown
+## Main success scenario
+
+1. [Actor action OR system response]
+2. [Next step, actor↔system alternating]
+3. [...]
+```
+
+Numbered list, 3-9 steps. Each step is either actor action or
+system response; alternate between them. Steps >9 = split into
+subfunction use case.
+
+Implementation language prohibited: "System calls Postgres" ❌.
+Say "System retrieves account" — let `/decompose` pick storage.
+
+### Extensions
+
+```markdown
+## Extensions
+
+- **Na. [condition]**:
+  - Na1. [step 1 of recovery]
+  - Na2. [step 2 of recovery]
+  - Na3. Use case ends with [outcome].
+```
+
+`N` = the main-scenario step number where the branch originates.
+`a`, `b`, `c` = multiple extensions at the same step. Sub-steps
+within an extension are `Na1`, `Na2`, `Na3`...
+
+Nested extensions (`Na1a`) are allowed but nesting >2 levels
+signals a subfunction extraction is needed.
+
+**Every step in the main scenario MUST have at least one
+extension considered.** If a step has no realistic branch, state
+that explicitly: `*No extensions — [reason]*`. Silence is a
+failure signal, not confirmation of happy path.
+
+Extension enumeration prompts (Cockburn, per skill Step 4):
+
+1. What if actor input is invalid?
+2. What if system can't complete step (timeout, dependency, resource)?
+3. What if a precondition silently broke?
+4. What if actor abandons partway?
+5. What if concurrent actor changed state?
+
+### Technology/data variations (optional)
+
+```markdown
+## Technology / data variations
+
+- *Step 3*: password may also be verified via WebAuthn credential
+- *Step 4*: session cookie may be HttpOnly OR stored in SessionStorage per platform
+```
+
+Use when the same logical step has multiple implementation paths
+with different -ility characteristics. Feeds `/decompose` with
+variation points needing Strategy pattern.
+
+### Related information
+
+```markdown
+## Related information
+
+- Non-functional requirements: [rate limits, latency SLOs, etc.]
+- References: [specs, ADRs, canvases, external docs]
+- Sliced by stories: US-NNN, US-NNN, ...
+```
+
+Rate-limit, latency, and other cross-cutting NFRs live here when
+they don't map cleanly to a stakeholder+interests row.
+
+## Validation matrix
+
+| # | Check | Fail signal | Severity |
+|---|-------|-------------|----------|
+| 1 | Goal level stated | Missing ☁️/🎯/🐟 | BLOCK |
+| 2 | Primary actor is a persona slug | "user" / missing / role word without persona file | WARN |
+| 3 | ≥2 non-actor stakeholders | Only primary actor listed | WARN |
+| 4 | Preconditions are checkable state invariants | Throat-clearing ("system is running") | WARN |
+| 5 | Main scenario steps numbered | Bullets or prose | BLOCK |
+| 6 | Main scenario 3-9 steps | ≥10 steps | WARN (candidate for subfunction split) |
+| 7 | Every step has ≥1 extension OR explicit "*No extensions — [reason]*" | Silence | BLOCK |
+| 8 | Extensions use Na Nb format | Free-form bullets | BLOCK |
+| 9 | Success guarantees trace back to trigger | Guarantee unrelated to trigger outcome | WARN |
+| 10 | Scope names a specific system boundary | "The app" / missing | WARN |
+| 11 | No implementation language in steps | "System calls Postgres" / framework names | WARN |
+| 12 | Trigger is a specific event | Abstract ("when needed") | WARN |
+
+BLOCK = skill refuses to emit; operator must fix.
+WARN = skill emits with warnings recorded in `_matrix.md`.
+
+## Relationship to adjacent standards
+
+| Standard | Relationship |
+|----------|-------------|
+| `persona-schema.md` | Primary actor MUST reference a persona slug per this schema |
+| `user-story-invest.md` | User stories slice use-case lines; stories cite UC-N step Xa in traceability |
+| `vpc-fit-validation.md` | VPC Pain-Relievers + Gain-Creators inform the stakeholders+interests "why this matters" framing |
+| `project-directory-layout.md` | `docs/use-cases/` is the bassclef path in app repos |
+
+## Relationship to adjacent skills
+
+| Skill | Role in use-case lifecycle |
+|-------|----------------------------|
+| `/use-case` | Produces use-case files per this standard |
+| `/user-stories` | Slices use-case lines into backlog tokens |
+| `/interaction-design` | Renders main scenario + extensions as diagrams |
+| `/decompose` | Reads use-case as alternative input to sequence diagrams; stakeholders+interests drive -ility audit |
+| `/verify` | Maps use-case lines to test assertions (1:1) |
+| `/spec` | Consumes use cases + stories as input |
+| `/shape` | `medium` + `full` tiers invoke /use-case as part of the chain |
+
+## Evolution
+
+- **v1.0 (2026-04-21)** — initial bassclef standard, Cockburn
+  fully-dressed format with goal levels, stakeholders+interests
+  discipline, and extension enumeration rules. Validation matrix
+  encodes BLOCK/WARN severities for skill-time gate.
+
+## Open questions for future iteration
+
+- **Concurrent-actor extensions**: Cockburn's rule 5 ("what if a
+  concurrent actor changed state?") is underspecified here. May
+  warrant a companion standard on optimistic-concurrency patterns
+  tied to use-case extensions.
+- **Use-case reuse (subfunction callouts)**: current format inlines
+  subfunction use cases; larger systems may need explicit "include"
+  references (UC-001 includes UC-042). Defer until observed pain.
+- **Use-case deprecation lifecycle**: `status: deprecated` is
+  noted but lifecycle (when to delete vs. archive) isn't codified.
+  Defer until first use-case is retired.
+
+## Closes
+
+- bassclef #213 (companion to `/use-case` skill)
+- Part of spec-lineage family epic #155