Compose intrinsic Grammar-v1 type fragments exactly - #489
Merged
Conversation
This was referenced Sep 1, 2026
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.
Summary
Continue Matrix
SURF-008/ ledgerPHIL-SURFACE-ELAB-001by composing only already-verified context-free Grammar-v1 type fragments into one dispatcher.Contract
Unit,Bool, and validU<n>delegate to the exact primitive-type bridge from Elaborate Grammar-v1 primitive types exactly #474;Bytes[...]delegates to the exact intrinsic Bytes bridge from Elaborate literal Grammar-v1 Bytes sizes exactly #478;Proof[...]delegates to the exact proposition-bearing Proof bridge from Compose intrinsic propositions into Grammar-v1 Proof types #488;Executable pressure
Phase1GrammarV1IntrinsicTypeCompositionMain.hsparses primitive, literal Bytes, and intrinsic Proof aliases and requires their exact CoreTyvalues.U0,Bytes[x], a named type, and a tuple are negative pressure and must remain unresolved.This is the fourteenth bounded SURF-008 slice after #462, #464, #466, #468, #471, #474, #477, #478, #481, #482, #485, #486, and #488; full Grammar-v1 elaboration correspondence remains open.