correction-mining: miner has no negative-signal run telemetry

[ahuimanu]

Observed

The session-correction-mining miner emits nothing when it finds zero clusters:

$ uv run python -m gzkit.insights.correction_mining --dry-run
session-correction-mining: 0 cluster(s) at threshold 3 from ~/.claude/projects/...gzkit

A zero-proposal run is indistinguishable from a miner that has silently
decayed — e.g. a stale CORRECTIVE_MARKERS lexicon
(src/gzkit/insights/correction_mining.py:33-46) that no longer matches how the
operator phrases corrections would also report 0 cluster(s). Nothing is
written; no run-log records that the miner scanned N transcripts and found 0.

By contrast, the sibling sensor shipped in the same ADR — the Stop hook
(OBPI-0.0.70-01) — writes one telemetry line per block to
.gzkit/sensors/stop-turn-feedback.jsonl (src/gzkit/hooks/scripts/quality.py),
so its catch-rate is observable. The miner has no equivalent negative-signal
surface.

Design gap

ADR-0.0.70 § Consequences › Negative #3 names this exact decay class — the
"fence with no recorded intrusions" class — and books block telemetry as the
mitigation for the hook, but the ADR scoped telemetry to the hook only. The
miner's observability gap is therefore out of ADR-0.0.70's delivered scope,
not a defect in it: the work shipped as designed. This GHI homes the
forward-hardening follow-on.

Proposal

Add bounded run-telemetry to the miner: one append-only JSON line per run to a
gitignored .gzkit/sensors/ run-log capturing run timestamp, transcript count
scanned, distinct sessions, clusters found, and the active threshold — counts
and config only, never operator text (the operator-PII rule and ADR-0.0.70
Boundary Invariant 2 bind every emitted record). A zero-proposal run then leaves
a trace that distinguishes "ran, found nothing" from "did not run / decayed
lexicon."

Class of failure

Read-only mining sensors whose only output is their positive findings: when
findings are zero, there is no signal separating a healthy null result from a
silently-broken detector. Applies to any heuristic miner whose detection
vocabulary can drift out of step with its input.

Scope hint (advisory, for routing)

• Estimated diff: <=100 lines (telemetry helper + call site + test), single module
• Surfaces touched: src/gzkit/insights/correction_mining.py,
  tests/chores/test_session_correction_mining.py, .gitignore (the
  .gzkit/sensors/ path is already excluded)
• In-flight vs. new feature: planned forward-hardening (post-ADR-0.0.70)

Provenance

Surfaced by the quality-reviewer persona during the ADR-0.0.70 Gate-5 audit
(2026-06-13); recorded in
docs/design/adr/foundation/ADR-0.0.70-turn-end-feedback-and-correction-mining/audit/AUDIT.md
§ Recommendations.

Related

• ADR-0.0.70-turn-end-feedback-and-correction-mining (parent; Negative Defect: OBPI brief drift from manual derived fields; add ledger-derived sync #3 names
  the decay class)
• OBPI-0.0.70-02-session-correction-mining (the miner)
• OBPI-0.0.70-01-stop-hook-turn-end-feedback (the sibling sensor that DOES carry
  telemetry — the asymmetry)
• Related: insights: no governed gz insights author verb — only a hand-append path #575 (insights: no governed gz insights author verb) — adjacent cut
  of the same correction-mining surface. insights: no governed gz insights author verb — only a hand-append path #575 surfaces positive proposals via
  a CLI verb; this GHI is the negative-signal / observability cut. Different
  root cause; sequenced together is natural (campaign Phase E).

[ahuimanu]

Blocker (open-with-blocker, not dead-letter): destination needs an operator design conversation.

No same-session destination artifact exists yet:

• Parent ADR-0.0.70 is Validated (terminal) — a closed ADR cannot absorb a new OBPI increment (1:1 ADR-checklist↔OBPI sync mandate).
• A new pool ADR is forbidden by Architectural Boundary Patch 0.3.1: Enforce ledger JSONL schema validation (GHI) #2 ("Do not add more pool ADRs to the runtime track", Architecture Planning Memo §12).
• Not an in-flight direct-fix — adding a telemetry surface is new-feature work (~<=100 lines), which AGENTS.md § Defect-fix routing routes to OBPI ceremony, not the direct fix(...) path; and it exceeds what the audit pass was authorized to land.

Next concrete operator action: sequence this into the gz insights / campaign Phase E design conversation (sibling #575). When that ADR is authored, miner run-telemetry is a natural sibling increment under it — at which point this GHI closes superseded citing the new OBPI/ADR ID. Until that design conversation happens, this stays open with this blocker.

[ahuimanu]

Related: #620 (claim-grounding: agent prose state-claims have no turn-end gate). #620 candidate fix shape (b) — a telemetry-only turn-end sensor logging unbacked agent state-claims — would feed the correction-miner this issue notes lacks negative-signal telemetry. Shared ADR-0.0.70 lineage; both home to campaign Phase E.