Repository navigation
Generic Contract Braid Substrate #476
Description
Activity
🔗 Related PRs
#315 - feat(kernel): strand contract — cycle 0004 [merged]
#326 - Echo contract hosting roadmap [merged]
#329 - Stack Witness 0001 fixture-backed jedit walking skeleton [merged]
#368 - feat(core): connect installed contract intent pipeline [merged]
#371 - feat(core): advance v0.1 contract evidence and retention [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!
Migrated from Method backlog
This issue was created from a legacy filesystem backlog card. GitHub Issues are now the live work tracker; repository docs remain Method evidence.
Source backlog:
docs/method/backlog/up-next/KERNEL_generic-contract-braid-substrate.mdOriginal lane:
up-nextOriginal legend:
KERNELOriginal backlog card
Generic Contract Braid Substrate
Status: planned kernel/runtime implementation.
Depends on:
Why now
jedit needs an ordered projection of edit strands over a file worldline, but
Echo should model that as a generic braid substrate.
What it should look like
A braid records:
The simple law is sequential: each new member forks from the current projection
frontier unless the caller explicitly requests a different basis.
Acceptance criteria
orderIndex.projectionAfterDigest.conflict posture.
Non-goals