Repository navigation
chore: retire the spent CFG-GOV purge script and its deploy notes - #31
Merged
Merged
Conversation
Both artifacts completed their one-time purpose in the 2026-08-06 CFG-GOV
cutover (the purge ran at 2026-08-06T04:56:27Z; the deploy it gated shipped
as afi-reactor-00027-7zp and has since been superseded by 00028-mgv).
The script is retired rather than kept because it is a standing hazard, not
a tool: its PURGE_LIST deletion is an unconditional deleteMany({}) with no
date or lifecycle filter, so re-running it against today's store destroys
every sealed record written since. A future governed corpus-clearing act
(D-CFG-2 makes wiping sealed records a governed correction, not an
operational script run) must be authored fresh against the store it targets.
Owner instruction 2026-08-22: remove the superseded artifacts interfering
with forward momentum (standing forward-only ruling).
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Kilo Code Review could not run — your account is out of credits. Add credits or switch to a free model to enable reviews on this change. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Forward-only cleanup (owner instruction 2026-08-22). Two deletions, both artifacts whose one-time purpose completed in the 2026-08-06 CFG-GOV cutover:
scripts/purge-scored-corpus.mjs— ran once (2026-08-06T04:56:27Z, stamped on the scrubbed analytics rows) and became a standing hazard: itsPURGE_LISTdeletion is an unconditionaldeleteMany({})with no date or lifecycle filter, so re-running it today would destroy every sealed record written since. Ranked the highest-severity/lowest-cost fix in the 2026-08-12 risk audit. Any future corpus-clearing is a governed act under D-CFG-2 (immutability attaches at SCORED), authored fresh — never this script re-run.docs/cfg-gov-deploy-notes.md— owner-only notes for the already-completed 00027 deploy, whose §"Run the corpus purge" instruction is exactly the stale directive that made the script dangerous to keep.No code references either file (grep-verified; no package.json script entry). The custody runbook (
docs/atlas-read-only-custody-runbook.md) stays — its content describes standing infrastructure, not a spent act.🤖 Generated with Claude Code