Gsd/phase 13 close v1 1 trusted peer genesis quorum policy and production - #360
Draft
henriqueaklein wants to merge 164 commits into
Draft
Conversation
henriqueaklein
force-pushed
the
gsd/phase-13-close-v1-1-trusted-peer-genesis-quorum-policy-and-production
branch
from
August 25, 2026 16:08
4b69d7c to
bc6da32
Compare
- Define reusable bounded codec and manifest contracts - Cover golden identity, normalization, malformed inputs, and tampering - Register the focused genesis manifest test target
- Encode reviewed genesis fields with bounded big-endian canonical bytes - Normalize and validate fixed-size trusted peer public keys - Derive and verify domain-separated SHA-256 fingerprints
- register identical patterns in independent registry objects - prove signer snapshots and owner teardown must remain node-local
- replace process-global registry storage with thread-safe object state - let SecureCrdt own or accept an injected isolated registry - route legacy lookups and registry tests through instance access
- register TrustedPeerRegistry and BurnConfig on their supplied SecureCrdt - preserve owner-token teardown within the same registry instance - fail factories when a same-node pattern is already registered
- move legacy SecureCrdt fixtures onto their owned registries - process same-key values under distinct in-process signer policies - retain one node's registration and quorum after peer teardown
- cover exact membership and burn threshold boundaries - exercise canonical policy decoding and successor linkage - prove proposed peers cannot authorize their own policy
- encode and validate versioned policy state with exact hash links - enforce strict-majority membership and two-thirds burn floors - bind successor authorization to the confirmed current policy
- Define typed trust snapshot and transition contract - Cover restart, network mismatch, ancestry, and fork rejection
- Commit genesis, policy, and burn heads in synchronous atomic batches - Revalidate canonical records, ancestry, and quorum proofs on every load
- Inject before and after batch-commit failures - Require one stable stale loser under concurrent successors
- Return stale outcomes for competing same-version successors - Preserve synchronous commit failure and recovery boundaries
- Record verified persistence and race-proof outcomes - Capture TDD gates, verification, and rollback boundary
- add barrier-driven concurrent account generation counterexample - add before- and after-readiness pinned signer regressions - require independent reviewed CR-11 and CR-12 RED diagnostics
- publish account and transaction services as one generation-owned snapshot - drain stale bridge work and reject callbacks from unpublished generations - pin trusted-peer approval labels and signatures to one node authority
- add four exact no-write and final-owner RED regressions - add deterministic listing and virtual-delay test seams - validate each pre-fix diagnostic independently in XML
- classify refresh outcomes and retry only transient discovery failures - dispatch through weak-owner system executor state with exact capped backoff - prove autonomous recovery, exhaustion, coalescing, and final-owner release
henriqueaklein
force-pushed
the
gsd/phase-13-close-v1-1-trusted-peer-genesis-quorum-policy-and-production
branch
from
August 26, 2026 14:21
ddb87b4 to
ea26555
Compare
…truction validator registration
…s atomically (CR-11)
henriqueaklein
force-pushed
the
gsd/phase-13-close-v1-1-trusted-peer-genesis-quorum-policy-and-production
branch
from
August 26, 2026 15:36
ea26555 to
33d8a51
Compare
… observations (CR-13)
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.
No description provided.