Conversation
forhappy
force-pushed
the
codex/node-write-scaling
branch
from
October 5, 2026 07:52
b96dffd to
02b25a3
Compare
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.
Independent Cells reserved a maximum-sized transaction allowance, which refused otherwise-small concurrent writes. Admit SQLite database, WAL, SHM and temporary-file growth before I/O, and reserve capture/commit credit from the database image bound. Preserve resource causes after proved rollback so the same owner and request identity can retry. Ambiguous commits and capture failures still fence.
Batch exact node-authority coverage across independent and coalesced Cell roots, preserving durability bindings, sparse completion history, cancellation and retirement. Keep a follower-proven owner usable after a later pre-SQL capacity refusal.
Use the installed node lease for quiet Cell liveness, removing periodic per-Cell control writes. Long preparation still checks the shared monotonic lease; exact-root publication, expiry fencing and unleased renewal behavior remain intact.
Add an offered-load Axum driver and application-owned follower fixture with pinned mTLS and canonical fsynced stores. Audit original identities and scoped receipts after cold restore. Critical measurements and source/binary provenance live in
crates/cellule-axum/performance; capacity qualification remains open.Validation: isolated LTX tests with and without replica features, runtime library, full runtime integration and durability tests, strict LTX/runtime/Axum Clippy, and default release builds pass. Format, layer/layout, documentation and SQL/peer checks pass. Broad workspace and process checks run in CI. The object/follower qualification gates are unchanged; current broad CI runs against the updated source.