Harden secondary indexes with an industrial atomic foundation - #52
Merged
Conversation
forhappy
marked this pull request as ready for review
July 29, 2026 18:52
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.
Outcome
Implements the approved
2026-07-28-secondary-index-industrial-foundation-hard-cutover.mdplan for the industrial foundation: atomic architecture, bounded resources, correctness, observability, and rigorous release gates.This is a hard cutover. It adds no compatibility reader, dual publication, migration shim, or suffix-named V2/V3 API.
Architecture
IndexedCollectionStateroot and one CAS linearization point.MemStore,FileNodeStore, PGlite, redb, RocksDB, and SlateDB are verification-only.Industrial controls
Release gates
docs/secondary-index-release-evidence.md.Local validation
cargo fmt --all -- --checkcargo clippy --all-targets -- -D warningscargo test: 500 library tests, all integration suites, 74 doc testsRelease status
The implementation is complete for review. Merge and production release remain gated on the required PR workflow. Swift runtime parity requires a configured macOS/XCTest runner, and scheduled ASan/extended performance evidence must be attached before a production release.