feat(emit): fail-fast guard on status-index integrity - #101
Merged
Conversation
Defense in depth against the class of bug that shipped a "revoked" badge. Before any signing/deploy, validate every active record's status_index: integer >= 0, distinct across members (no shared status bit), and absent from the revocation ledger (no active member on a burned index). On violation the build fails loudly instead of silently publishing broken data. This catches what the sequential next-index fix cannot: two near-simultaneous inscriptions that computed the same index before either merged. Pure logic in lib/member-indices.mjs with tests (incl. the exact blafourcade-on-revoked case). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PC9TRnYr5AXe7GmBmHjkBy
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.
Defense in depth against the class of bug that shipped a "revoked" badge.
Before any signing/deploy, validate every active record's status_index:
integer >= 0, distinct across members (no shared status bit), and absent from
the revocation ledger (no active member on a burned index). On violation the
build fails loudly instead of silently publishing broken data.
This catches what the sequential next-index fix cannot: two near-simultaneous
inscriptions that computed the same index before either merged. Pure logic in
lib/member-indices.mjs with tests (incl. the exact blafourcade-on-revoked case).
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01PC9TRnYr5AXe7GmBmHjkBy