phantom-quenchlisted

The grounding member of the quench series — extracts proper nouns, numerical values, and branching conditions from artifacts (TCs, analysis reports, design documents), back-traces them to declared source files, and marks anything not found as a Phantom Claim (ungrounded — present in the artifact but not traceable to a declared source; not a claim that it is necessarily false). If steel-quench attacks output patterns (self-declarations, cushion language), phantom-quench attacks input tracing (where did this come from?). Renamed from source-grounding-audit (2026-06-06, quench-series); `/source-grounding-audit` still resolves as an alias. Triggered by "phantom detection", "phantom-quench", "phantom claim", "hallucinated claim detection", "source back-trace", "source audit", "verify source", "TC evidence tracing", "where did this come from", "grounding audit", "source grounding audit", "false claim detection".
chrono-meta/forge-harness · ★ 2 · AI & Automation · score 74

Install: claude install-skill chrono-meta/forge-harness

# phantom-quench — Input Tracing Grounding Audit > Just because an artifact looks plausible doesn't mean it's grounded in source. plausible ≠ grounded. > **Renamed from `source-grounding-audit` (2026-06-06)** — the grounding member of the quench series > (steel-quench · phantom-quench · goal-quench). Same skill, same ruleset; only the label changed to fit > the family. The **v1 paper (Zenodo 10.5281/zenodo.20397566) cites the old name** — that is the > historical record, not a phantom. `/source-grounding-audit` still resolves via the deprecated redirect > stub at `plugins/fh-meta/skills/source-grounding-audit/SKILL.md` (`successor: phantom-quench`). > This is a **label rename, not a capability change** — phantom-quench does not fuse steel-quench or > inject faults; those remain separate (orthogonality is deliberate — see Role Separation below). > > **Quench-series semantics** (resolves the "quench *what*?" question): each member subjects a different > thing to the forge — steel-quench hardens an **existing output**; phantom-quench hardens the system > against **mistaking the absent for present** (the phantom illusion — *not* the phantom as a material to > harden); goal-quench hardens the **goal itself** into an advanced version. Same verb, consistent grammar. > > **Not the same as `phantom-gate`.** `phantom-gate` is the *productized standalone* phantom detector — a > PyPI package run against any repo from the shell. `phantom-quench` is the *in-harness skill* — the same > de