source-grounding-auditlisted

# source-grounding-audit — Input Tracing Grounding Audit > Just because an artifact looks plausible doesn't mean it's grounded in source. plausible ≠ grounded. When AI generates artifacts without reading the source, those artifacts look like domain knowledge but are actually **Phantom Claims** coming from LLM weights. This skill back-traces each claim in the artifact to the declared source to explicitly mark Phantoms. ## Role Separation from steel-quench | Dimension | steel-quench | source-grounding-audit | |---|---|---| | **Attack target** | Output patterns (self-declarations, cushion language, reason for existence) | Input tracing (is the claim in the source?) | | **Core question** | "Is this structure flawed?" | "Where did this content come from?" | | **Activation timing** | All-angle quench just before completion | Immediately after source-based artifact generation or at point of suspicion | | **Primary attack vector** | Bus factor, self-reference, platform obsolescence | Phantom Claim, source not read, fabricated branching conditions | | **Representative pattern** | "Declaration only, no evidence" | "Number in TC that doesn't exist in source" | **Can be used together**: steel-quench Wave 1 real-code-based attack + source-grounding-audit Phantom marking can be run sequentially in the same session. But do not mix the roles of the two skills. --- ## Trigger Phrases | Phrase | Situation | |---|---| | "phantom detection", "phantom claim", "false claim detection" | Ful