Owner-only CFG-GOV follow-ups: Atlas custody runbook, corpus purge script (dry-run default), deploy notes - #29
Merged
Conversation
…g executed) - docs/atlas-read-only-custody-runbook.md — exact Atlas users/roles/grants for D-CFG-2(3) custody separation, per-consumer, with verification steps. - scripts/purge-scored-corpus.mjs — owner corpus purge: dry-run by default, exact per-collection before/after counts, --confirm-purge-scored-corpus required to act, hard-refuses the keep-list (signal_outcomes and scoring_context, which carries the raw ingest payloads). NOT RUN. - docs/cfg-gov-deploy-notes.md — behavioural deploy notes: records seal at admission, recordHash moves prospectively, purge BEFORE deploy so the store is uniformly sealed from the first record forward. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
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.
Prepares — and does not execute — the three owner-only items that complete the CFG-GOV slot work (afi-infra#28, afi-reactor#80, afi-config#80, all merged):
docs/atlas-read-only-custody-runbook.md(D-CFG-2(3)): the exact Atlas users, roles, and per-database grants —afi-evidence-writer(sole canonical writer),afi-evidence-reader(verify cron + all readout tooling),afi-analytics-writer(outcome capture, no canonical grant) — plus post-cutover verification steps. This custody separation cannot be enforced from these repos; it is Atlas console work.scripts/purge-scored-corpus.mjs: clears the pre-CFG-GOV scored corpus (canonicalscored_signal_evidence+_history) while HARD-KEEPING the observations —signal_outcomesandscoring_context(which carries the raw ingest payloads,rawUss, enabling offline re-scoring). Dry-run by default with exact per-collection before/after counts; acting requires--confirm-purge-scored-corpus; unknown arguments and keep-list names are refused. It has not been run (no database URI exists on the authoring machine; refusal paths proven without a connection).docs/cfg-gov-deploy-notes.md: what a deploy changes (records seal at admission;recordHashmoves prospectively per D-EV3-4(6), documented under D-CFG-6; verify-on-read + re-verification cron; composition-scoped proofs; analyticscompositionRefstamp) and why the purge must run BEFORE the deploy so the store is uniformly sealed from the first record forward.Documentation and an unexecuted script only — no runtime surface, no schema, no test change.
Made with Cursor