Repository navigation
Adopt deterministic contract profile for shared boundary families #49
Description
Activity
Cross-repo trail:
- Coordinator: Consume Bunny/Wesley deterministic contract profile for git-warp codecs git-stunts/git-warp#685
- Bunny profile: Define deterministic contract profile for generated wire codecs bunny#194
- Wesley lowering: Keep Wesley profile-neutral for deterministic contract extensions wesley#651
- Doctrine anchor: git-stunts/git-warp@529210e
Ownership reminder: Continuum owns shared family semantics and proof posture here, not runtime internals or codec implementation.
🔗 Related PRs
#18 - Align Continuum sibling runtime doctrine [merged]
#19 - Add cross-repo contract family registry [merged]
#35 - docs: record git-warp gate ownership [merged]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.- Create Plan
🧪 Issue enrichment is currently in open beta.
You can configure auto-planning by selecting labels in the issue_enrichment configuration.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:issue_enrichment: auto_enrich: enabled: false
💬 Have feedback or questions? Drop into our discord!
Context
Continuum owns shared boundary language and proof posture across the stack. It should not own runtime internals, storage, or compiler implementation, but its authored shared families need a deterministic representation profile so generated artifacts can travel without drift.
The active split is now:
Why this exists
git-warpissue git-stunts/git-warp#685 exposed a scalar/byte-fidelity gap before generated codecs can safely own canonical runtime boundary bytes. Bunny and Wesley now have companion issues for the profile and compiler sides:Continuum should track the shared-family adoption side so this does not become a shadow vocabulary scattered through runtime repos.
Scope
Identify which Continuum family schemas should consume the deterministic profile first, likely around runtime-boundary/witnessed suffix exchange before broader families:
schemas/continuum-runtime-boundary-family.graphqlFor each adopted field or envelope, Continuum should specify the semantic noun and proof posture while deferring byte representation mechanics to the Bunny/Wesley profile/toolchain.
Acceptance
Related