feat(spec-phase): surface zero-classification edge-probe requirements as unclassified candidates (#1110) (#1117)
Edge-probe now surfaces a zero-classification requirement (non-empty prose, no shape cue matched, no `shapes` override) as a single soft `unclassified — review manually` candidate instead of silently dropping it — the exact blind spot the probe exists to catch. Dismissible like any edge; the `shapes: []` opt-out stays silent; `TAXONOMY` (the closed 8 categories) is unchanged. Under `--auto` the candidate is left `unresolved`, never auto-`backstop` (a missing shape is not evidence an edge exists). Closes #1110
This commit is contained in:
@@ -77,6 +77,17 @@ Two rules keep the probe honest and prevent an "everything is N/A" failure mode:
|
||||
2. **Dismissal requires a reason string.** "N/A — input is a bounded enum, no boundary
|
||||
exists" is valid; silence is not. The reason string is the audit trail.
|
||||
|
||||
**Zero-classification surfaces an `unclassified` candidate (#1110).** The relevance filter is
|
||||
a heuristic over prose cues, so a requirement whose wording *is* edge-relevant but matches no
|
||||
shape cue would otherwise classify to zero shapes → zero edges and vanish from coverage with
|
||||
no signal — the same silent blind spot the probe exists to catch. Instead, a requirement with
|
||||
non-empty prose, no authored `shapes`, and zero matched shapes surfaces exactly one soft
|
||||
`unclassified — review manually` candidate (`category: "unclassified"`, `status: "unresolved"`).
|
||||
It is a dismissible nudge — resolve it, or dismiss it with a reason (e.g. a genuinely edge-free
|
||||
static-asset requirement) — never a hard block. `unclassified` is a review signal, **not** a
|
||||
ninth taxonomy category: the closed eight above are unchanged, and an explicit `shapes: []`
|
||||
opt-out stays silent (the author's deliberate "no edge surface").
|
||||
|
||||
Each raised edge carries two orthogonal axes — a resolution **lifecycle** and, when
|
||||
resolved, a **verification** tier (ADR-550 Decision 7, the shared probe-core model):
|
||||
|
||||
|
||||
@@ -295,6 +295,9 @@ For each Requirement gathered so far:
|
||||
- **Dismiss (reason)** → mark `dismissed` with a required non-empty reason.
|
||||
- **Backstop with a test** → mark `backstop`; note "held-out edge test" for plan-phase.
|
||||
- **Defer** → leave `unresolved`.
|
||||
- An `unclassified` row (probe `unclassified — review manually`) means the requirement's
|
||||
prose matched no shape cue (#1110) — treat it like any other candidate (**Specify**,
|
||||
**Dismiss (reason)**, or **Defer**). A manual-review nudge, not a hard block.
|
||||
|
||||
**Soft gate (after resolving):**
|
||||
- All applicable edges resolved → proceed to Step 6.
|
||||
@@ -310,6 +313,14 @@ For each Requirement gathered so far:
|
||||
otherwise auto-`backstop` (never auto-dismiss — a wrong dismissal is the exact silent
|
||||
failure being eliminated). Log: `[auto] edge coverage: C covered, B backstop, U unresolved`.
|
||||
|
||||
**`unclassified` exception (#1110):** `--auto` leaves an `unclassified` candidate
|
||||
**`unresolved`** (the soft gate surfaces it as a flagged planner assumption) — it never
|
||||
auto-`backstop`s it. A missing shape is not evidence an edge exists, so minting a held-out
|
||||
edge obligation on a requirement that may be genuinely edge-free would be a false claim and
|
||||
risks a vacuous edge test. Leaving it `unresolved` keeps the zero-cue requirement visible
|
||||
(never a silent drop) without fabricating an edge — which is exactly #1110's purpose: surface
|
||||
it for review, do not auto-handle it.
|
||||
|
||||
Populate the `## Edge Coverage` section of SPEC.md from the resolved edges.
|
||||
|
||||
## Step 5.6: Prohibition-Completeness Probe (must-NOT)
|
||||
|
||||
Reference in New Issue
Block a user