Repository navigation
Persist source-bound fragments and checked reading traversals - #123
Draft
isomorphisms wants to merge 2 commits into
Draft
isomorphisms wants to merge 2 commits into
isomorphisms wants to merge 2 commits into
Conversation
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.
Source-linked reading records currently have no ordinary-file round trip or decoded-source revision binding. This child of the existing canonical successor keeps IB.Strand's information projection and IB.Occurrence's fragment traversal separate, adds checked revision-bound TSV graph records and rebuilt link queries, and consumes Longview's existing immutable publication adapter.
Implemented: source/representation/decoded-digest/decoder/code-point binding; range, traversal and link refusal; overlapping literal search; explicit UTF-8 boundary mapping; commit-marked serialization and decode; bounded Grease snapshot/hash/UTF-8 validation and publication only after successful normalization. A minimal pre-existing canonical Text constructor compatibility repair is included in this isolated child, with its two consumers and missing Data.Text import.
Evidence: actual current Idriç checker ff4d852862a3942592f8ade9afde8d409d9803be typechecks the new core, acceptance and command. Its pure compiler normalizer returns True for all 13 cases; a mutation bypassing source binding makes the wrong-unit and changed-revision cases False. Current Grease 5651cf97a1b5042f24f14112a7ade9a1518eb0bc executes ordinary-file roundtrip, preserves producer exit 7, refuses stale bytes and uncommitted tails, and reopens prior committed state. The Grease OS producer is an explicit fixture; it is not Idriç runtime acceptance.
Status: PARTIAL. The integrated Idriç normalizer executable remains blocked on qualified ICK/NDK consumer generation. No alternative backend was selected. The durable adapter comes from the retained Longview line and must be reconciled at integration; this branch does not copy it. Physical Android and real private corpus are NOT_RUN. Exact receipts, runtime digests and inherited Grease compatibility options are in docs/fragment-store-acceptance.md.
Owner: #101; execution assignment #120 / IB-S06. Parent: isomorphisms/ib PR #48, “Rewrite canonical IB slice in current Idriç style” (#48).