← Files Vibe CodingARCHIVED FILE
skills/vibe-workflow/references/evidence-normalization.md
1.46 KB · Oct 4, 2026 · 12:34 UTC
# Evidence Normalization ## Operation Analyze and return an actionable brief in the current conversation. Planning does not create a new assistant task or edit product code. Carry the full requested objective into the plan; separate independent work without silently discarding it. ## Goal Convert heterogeneous repository findings, logs, traces, tickets, and audit outputs into a deduplicated evidence set suitable for synthesis without changing priority or inventing missing facts. ## Normalize Accept logs, audit prose, tickets, traces, plans, or model outputs. Preserve provenance and exact uncertainty. Extract only evidence-backed owner, invariant, impact, acceptance, validation, scope, and rollout data. Do not upgrade hypotheses to facts, merge independent owners, or choose downstream implementation work. Return the narrowest applicable artifact: intake summary, audit result, task definition, implementation summary, or check evidence. When source material conflicts, keep both claims and mark the missing discriminator. - Preserve exact `path:line[-line]`, symbol, command, trace, timestamp, environment, and source references when available. - Mark each statement as direct evidence, inference, assumption, or unavailable fact. - Merge only identical observations; keep contradictory evidence side by side for [Synthesis](../../vibe-task/references/synthesis.md). - Remove prose that does not change owner, invariant, impact, acceptance, validation, dependency, or exclusion.
SHA-256: b0333cffa646ce2d3247552dc7ffba5a19755d718fc273ce01c4e9d54a274680