Repository navigation
[GP3-S4] CAS-Addressed WSC Export Fixture #566
Description
Activity
🔗 Related PRs
#263 - feat(echo-cas): content-addressed blob store (Phase 1) [merged]
#298 - feat(warp-core): TTD domain logic — provenance storage + causal cone walk [merged]
#329 - Stack Witness 0001 fixture-backed jedit walking skeleton [merged]
#371 - feat(core): advance v0.1 contract evidence and retention [merged]
#379 - feat(core): commit runtime WAL ACK evidence [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!
- added a parent issue
on Jun 20, 2026 - moved this from In Progress to Done in Continuum Stack Convergence
on Jun 28, 2026
Roadmap slice: GP3-S4
Goalpost: Goalpost 3: WSC Causal-History Export And Import
Parent: #522
Related: #521
Source:
docs/design/wal-wsc-durability-roadmap.mdon branchcycle/521-wal-wsc-storage-relationshipatbde7957c.Scope
Parent issues:
#522,
#519.
Scope:
retained material.
echo-casas byte storage, not semantic authority.Acceptance:
hashes.
Witness:
Dedupe note
This is the PR-sized implementation slice for the roadmap item above. Existing umbrella or adjacent issues remain linked as Parent/Related rather than duplicated here.