Repository navigation
Single-use rung drop: admit one D0 lifecycle for group-a while the store walls are unfinished - #12744
Merged
Merged
Conversation
…escalation d0-group-a-ds41-2026-09-30) while the store walls are unfinished Operator-ruled 2026-09-30 (option A, relayed by proud-deer-538). gunbc.rung_drop.d0_store_walls_single_lifecycle declares the drop (previous MechanicallyPreventable, temporary Mitigatable, replacement staged, one lifecycle including its reruns, restoration: both walls live on srv1). d0_store_write_wall_standing now takes the group and escalation id: both walls finished admits every lifecycle; otherwise only the declared one is admitted and everything else refuses as before. Witnesses: the declared lifecycle is admitted on the real row; a second consent id, group-b and a retired drop refuse; the walls' own refusal still answers for group-b. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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
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.
Operator ruling, 2026-09-30, option A, relayed by proud-deer-538: take the fabric store walls off DS4.1's critical path with a declared, single-use rung drop.
The row:
gunbc.rung_drop.d0_store_walls_single_lifecycle.MechanicallyPreventable. Both store walls are required before D0 runs.Mitigatable. One operator-admitted lifecycle runs.ReplacementStaged. The store walls are in flight: Fabric store per-operation admission fold (d0_store_operation_wall PR 4a) #12537 and the rest of the d0_store_operation_wall chain.d0-group-a-ds41-2026-09-30, including reruns of that same lifecycle (same id, the frozen filing's execution revision). No other id and no other group.fabric_storage_append_principal_unrefusedretired and effective on srv1, andd0_store_operation_wallatStoreOperationWallRestored, sufficient for a rostered writer without D0 authorization to be refused at the store.docs/design-rung-drops.mdregenerated locally withgenerated_artifact_gate main_wet: exit 0, one path changed.The gate.
gunbc.spark.pair_serving_d0d0_store_write_wall_standing(group, escalation_id):d0_single_lifecycle_admits), and every other lifecycle gets the walls' refusal exactly as today.The wet door passes its
groupand itsauthorization=escalation id. Everything else in D0 is unchanged: operator approval through the approvals app, the durable claim, the frozen filing and the authority event log.Witnesses (
test.claim.spark.pair_serving_d0_witness), all PASS locally, ≤94 eval steps each:the_declared_single_lifecycle_is_admitted_while_the_drop_stands, on the real row.a_second_consent_id_or_group_b_or_a_retired_drop_refuses_the_single_lifecycle. The earlier idds41-group-a-d0-20260927refuses; group-b refuses; a retired drop refuses. The last is over a supplied standing,d0_single_lifecycle_admits_under.the_wet_door_refuses_while_the_fabric_storage_write_wall_drop_standsstill asserts the walls' own refusal, now for a lifecycle the drop does not admit (group-b).The earlier escalation id
ds41-group-a-d0-20260927. proud-deer-538 reports that the dispatches under it refused before filing anything, so no filing exists under it. I could not confirm that with a store read from this session. srv1 refuses this session's ssh (publickey), and the store's door is a unix socket on srv1. The confirming read isgunbc.spark.pair_serving_d0d0_read_filingfor that escalation on srv1, answeringD0FilingAbsent. It needs someone with srv1 access. Either way, this drop refuses that id; the RED above is exactly that case.🤖 Generated with Claude Code