Repository navigation
docs: bind capability and SQL claims to actual implementation evidence - #147
Merged
Merged
Conversation
psvensson
marked this pull request as ready for review
October 26, 2026 12:17
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.
Purpose
One coordinated owner-level steering clarification under rule-set revision 4 (no new global R-rule, new acceptance gate or product feature). Identify code-facing claims that cannot be justified on the current backend and specify the existing owners' fail-closed obligations.
Scope / coverage
docs/current-capabilities.jsonstates split component presence, raft-rs cadence, compaction and integrated recovery.DO UPDATE→orReplacesemantic defect and public typed-refusal boundary, including literal and uncertain-COMMIT obligations.docs/rs-raft-convergence-snapshot-20261026and lab recovery branchdocs/disposable-recovery-20261026in its separate repo.Concrete unfixed source gaps (do not close with docs)
src/partition/partition-snapshot-cadence.jsreturnsCOMMITTED_LOG_UNSUPPORTEDfor file-backed leaders. Automatic raft-rs snapshot/compaction/recovery still needs an owner-level implementation and exact-candidate proof.src/query/pg/pg-translate.jsmaps PostgreSQLON CONFLICT DO UPDATEto replacement; a code repair must implement correct semantics or typed refusal before side effects. Public literal and transaction-unknown-outcome proofs remain open.Verification performed
78052505ce375b50ba94b812adc8b67b9e5f5084: success. Generated metadata is current;npm run checkpassed its fast-static audit and all 179 selected test files (4,750 runner-reported assertions, zero failed files).Integration coordination
Historical predecessor tests remain valid in their original scope. The active RS-Raft integration branch is not changed or resumed by this PR. Preserve existing accepted repairs and the 25 October stop instruction.