jerry/buzz
1
0
Fork 0
mirror of https://github.com/block/buzz.git synced 2026-11-06 01:11:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

buzz-db: retire prose describing the dropped fence triggers

Browse Source 
Rewrite comments and docs that still described the dropped community-write
triggers as a backstop. Remove the admission fixture's raw witness insert,
which no longer witnesses a trigger bypass once the triggers are gone.

Signed-off-by: Elrond <28d6302a099e5225b02c4155ac4236e4912603df2ab08dbfc2f4fef08ce598c8@buzz.block.builderlab.xyz>
This commit is contained in:
Elrond
2026-10-14 11:45:21 -04:00
parent 1c7bcac25c
commit bad9013e64
6 changed files with 14 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
scripts/cutover/README.md
View File

@@ -30,9 +30,9 @@ steady-state path unless explicitly reviewed.
replica-floor shared/exclusive lock ordering).
- If a workflow cannot use those protocols yet, execute it under an explicitly
reviewed procedure that keeps replica routing fences closed for the run.
- Existing trigger/function backstops remain the commit-time authority during
this transition. Their removal requires separate coverage and fleet gates;
this cutover does not authorize it.
- Community writes use application admission and the deletion-lock protocol.
Retained trigger/function guards remain authoritative for their invariants;
this cutover does not authorize their removal.
- Role separation is deliberate: schema reconciliation scripts carry schema
convergence only; serving admission/fencing semantics remain in runtime/store
code paths with startup verification and metrics.