Enable v9 Caveats and expiring Relationships - #175
Merged
Conversation
theronic
marked this pull request as ready for review
September 5, 2026 20:36
This was referenced Sep 6, 2026
Closed
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.
V9 evaluates qualifier-backed Caveats and exclusive expiry across checks, lookups, counts, cursors, and Relationship inspection. Detailed reads retain conditional permissions and residual context; Boolean checks and default lookups/counts return definite grants. An expired ban can reveal a grant without a database write.
Qualified writes atomically publish both endpoint references, schema and Relation fences, endpoint identity guards, qualifier cleanup, and caller-composed application data. Native and externally constructed connections support inert preparation and pure snapshot transaction planning. Ordinary no-op writes preserve the database basis; bounded object cleanup replans on certified contention.
Point, collection, rendered-page, and checkpoint reuse checks temporal certificates. Live cursors require restart outside their certified interval; explicit snapshots retain historical time. Bundled backends use exact-basis qualified answer reuse because arbitrary native writers cannot establish qualifier immutability from Relation stamps alone.
All 43 Phase 3 tasks are complete. Qualified serving is enabled by default, the engine epoch is 9, continuation semantic ABI is 3, and coordinated build metadata targets
9.0.0-SNAPSHOT. The five-element Relationship storage ABI remains 9. Datalevin remains excluded from Maven release eligibility until its fork artifact is published.Validation against the activated default:
docs/benchmarks/results/qualified-authorization-2026-09-05/. Budgets were not relaxed.The full legacy JVM battery and affected Datalevin contracts were also checked before changing the default. The migration, result/error, cache/cursor, clock, and pinned-time guides describe the final contract. The acceptance crosswalk is in
formal/qualified/acceptance.md.The final CI correction adds bounded CAS-contention retries for DataScript and Datahike's prepared writers, with deterministic interleaving and terminal-error tests. Generated-authority verification passes 9 heavy tests / 574 assertions and 625 correctness tests / 117,495 assertions; the affected writer suites pass 17 tests / 7,256 assertions. The unrelated-commit benchmark now enforces v9's deliberate exact-basis fallback while retaining the v8 managed-hit expectation under its compatibility binding.