--- name: parked-content-audit description: "CLOSED — the comprehensive content/canon sweep ran and its corrections shipped. Kept for the sourcing rule and the data-integrity constraints, which are permanent." metadata: node_type: memory type: project originSessionId: 0b7c5f41-bb34-4ab4-93be-fdb363f5eb40 --- # CLOSED — ran; corrections shipped Parked 2026-06-28 (owner: "Add 1-6") as a plan-only sweep of every content database across both games for completeness, canon accuracy and internal consistency. It ran and its canon corrections landed. **Nothing pending** — if another content sweep is wanted, re-scope to the remaining gaps rather than re-running this brief. *Correction 2026-07-20: removed the database/file inventory, protocol numbers, the specific canon suspects (since fixed), the shipped-corrections commit ref, and the verdict scaffolding. Current data structure is in `library/CODE_MAP.md`.* ## ⭐ THE SOURCING RULE — permanent, and the reasoning is the point **fallout.wiki is the ONLY acceptable source for canon facts.** Fetch the page and read it; do not fill gaps from model knowledge. Owner's framing, which is the rule's whole justification: **the agent is a typist, not an authority.** Content that *sounds* canon is exactly the failure mode — a plausible invented quest or a slightly-wrong stat is indistinguishable from a real one on inspection, and it poisons a database that is supposed to be a reference. Every correction must carry the source page it came from. This applies to numeric fields as hard as to names: values that feed lookups must be verified individually, not eyeballed. ## Permanent data-integrity constraints - **CSV column integrity is load-bearing.** No commas inside fields — a stray one silently shifts every column after it, and the parser will keep working while producing wrong data. Verify column counts after any edit. - **Per-game content must not bleed across games.** Content exclusive to one title appearing in another's data is a correctness bug, not a cosmetic one. - **Cross-check the two content systems against each other.** Anything referenced in one and missing from the other is a gap, and the mismatch is invisible until something tries to render it. - **Watch for duplicates and key collisions** across sections — same-named entries in different categories can silently overwrite each other in a shared lookup. Feeds [[parked-synthesis-masterplan]].