Report confirmed deletions privately and bind approved Laya policy #34
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
backmeupplz/jev_antispam_bot!34
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/69-approved-audit"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Scope
Implements #69 Decision3196: private confirmed-deletion reporting to the sole authorized sink and matching approved ckpt-v2 rules/examples identity. User explicitly accepted the disclosed prompt tradeoff; tests do not relabel the benchmark.
Verification
Typecheck; 476 tests passed, 249 live-only skipped. Model companion has 12 offline tests. Independent Astra/high exact-head privacy/correctness review pending; this is not merge approval.
Coupled rollout
Companion model branch fix/69-approved-policy in backmeupplz/jev-laya. Both managed services currently pinned to release/69-pre-rollout at old deployed commits, preserving env/mount/deploy bytes. Stop old bot, deploy/verify model, deploy/start matching bot, verify source/prompt/checkpoint/cache/gates/capture and harmless audit receipt. No model-only rollout while old bot runs. Additive migration004; DATABASE_URL mandatory. Details in docs/audit-outbox.md and docs/approved-policy-rollout.md.
No raw production data or secrets included. No exactly-once claim; unknown deletion/send outcomes are explicit, bounded and not blindly retried.