# Builder Spec Governance

> Partial Skill: invoke by name only

- Skill: `cyberuni/builder-spec-governance` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add cyberuni/builder-spec-governance`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cyberuni/builder-spec-governance/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools, Web & Frontend
- Author: cyberuni (https://skillmd.com/u/cyberuni)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cyberuni/builder-spec-governance

---


# Builder-Spec Governance — the testability & coverage bar

The **Builder** bar at the **spec gate**: is this **capability** fully and testably specified? Judges
the capability's contract (read from its spec + suite), not the document's prose — that is
`sdd:spec-format-governance`. Loaded by both faces. The SDD default for the `builder` spec bar; a
plugin may bind its own, and this loads when the registry leaves `builder`/`spec` unbound.

## The bar

- **Every branch of the capability is covered.** Each edge of its control-flow graph (CFG) has its
  scenario, and every guard/negative edge is paired with a positive companion. The **scenario map
  is 1:1** — no orphan scenario, no uncovered edge (`sdd:suite-format-governance`). For a **fold**
  node whose rule combines two or more interacting sub-conditions, the CFG is drawn from that rule
  stated in **closed form** (single-condition folds may be by example — demanding closed form of one
  is over-firing), and its coverage is backed by a **mutation sweep** and a **safety dual**
  (`sdd:suite-format-governance`).
- **Every stated extension is a path in the CFG.** A use case's **extensions** are its divergences
  (`sdd:spec-format-governance`), and the CFG is the **single source** the scenarios derive from —
  so an extension earns its scenario **by being a path in the graph**, never as a second rule
  alongside the edge coverage above. The check is therefore: does the CFG contain a path to each
  stated extension? An extension with no path is a hole in the **graph** — fix it there, and the
  standing 1:1 edge coverage supplies the scenario. **Never derive a scenario from the prose
  directly**: a suite drawn from a stated list is 1:1 with that list by construction and can no
  longer surface a hole, which is the retrofit shape that has diverged in this corpus before. A use
  case declaring `extensions: none` asserts nothing can diverge — judge that claim against the
  graph. A **forbidden combination** is the same rule in guard form: it is a decision the CFG must
  carry, and its refusal scenario comes from that guard's edge.
- **Every scenario is testable.** Each asserts an observable outcome a check can confirm — a boolean,
  no "sometimes". A behavior the capability cannot expose cannot be specced.
- **A graded subject is still a boolean.** For a non-deterministic capability the contract reaches a
  per-scenario boolean through a rubric + threshold over N runs; the rubric form stays out of the
  boolean `.feature`, carried as a judge-only `@rubric` scenario.
- **A dimension or cut is grounded on non-author evidence.** When a `@rubric` dimension or its cut is
  justified by a **measurement** (an ablation Δ, a discrimination count), that measurement is admissible
  only if it is **not solely the author's own** — independently produced/reviewed by a non-author, or a
  fresh-adversarial ablation. An author's own instrument silently assumes the property under test. The
  standard is stated canonically at `sdd:doctrine-loop`; this bar requires it be met, not re-listed
  (the cold-instrument doctrine).

## Key points (read-check)

1. **Every branch of the capability is covered** — every edge has its scenario, guards paired with
   positives, the scenario map 1:1.
2. **Every stated extension is a path in the CFG** — the graph is the single source scenarios derive
   from, so an extension earns its scenario by being a path, never as a second rule alongside edge
   coverage; a divergence with no path is a hole in the *graph*. Never derive a scenario from the
   prose directly. `extensions: none` is a claim to judge; a forbidden combination is a guard the
   graph carries.
3. **Every scenario is testable** — an observable boolean outcome; behavior the capability cannot
   expose cannot be specced.
4. **A graded subject still reaches a per-scenario boolean** via rubric + threshold; the rubric stays
   out of the `.feature`.
5. **A dimension or cut is grounded on non-author evidence** — a measurement justifying it must be not
   solely the author's own (canonical standard: `sdd:doctrine-loop`); the cold-instrument doctrine.