Add transaction-composable quad patches - #32
Merged
Conversation
kcsfelty
force-pushed
the
feat/composable-quad-patches
branch
from
July 20, 2026 22:21
d264cff to
d90c67e
Compare
kcsfelty
marked this pull request as ready for review
July 20, 2026 23:19
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.
What changed
prepareQuadPatch()as a validated, ordered D1 statement planapplyQuadPatch()convenience API and typed conflict behaviorWhy
Taproot must commit canonical entity JSON, immutable revisions, search terms, and the corresponding RDF closure under one atomic D1 boundary. Diamond previously owned and immediately executed its internal batch, so an application could not safely include adjacent writes.
Closes #30.
Validation
npm run check