Expose structured MCP reads with stable ledger identities - #601
Merged
WaylandYang merged 3 commits intoSep 11, 2026
Merged
Conversation
Floating-Y
force-pushed
the
feat/550-structured-read-contract
branch
2 times, most recently
from
September 10, 2026 17:01
f386e58 to
f053c8b
Compare
Signed-off-by: Floating-Y <118035379+Floating-Y@users.noreply.github.com>
Signed-off-by: Floating-Y <118035379+Floating-Y@users.noreply.github.com>
Signed-off-by: Floating-Y <118035379+Floating-Y@users.noreply.github.com>
WaylandYang
force-pushed
the
feat/550-structured-read-contract
branch
from
September 10, 2026 23:57
f053c8b to
88257f4
Compare
Contributor
|
Reviewed against Three small things I'll take as a follow-up rather than hold this on (tracked in an issue):
Also noted: refused calls (the shared |
5 tasks
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.
MCP readers currently have to parse prose to recover facts and provenance.
Add structuredContent alongside existing text for find_entities,
search_chunks, entity_facts, and changes, using the same UUIDs as RDF exports.
relation qualifiers, and explicit limit metadata.
No database migration or new dependency is required.
Conflict/review export (#564), chunk provenance in RDF, and SPARQL
remain separate work.
Validation
Closes #550.