Repository navigation
Retained Evidence Durability Boundary #519
Description
Activity
🔗 Related PRs
#326 - Echo contract hosting roadmap [merged]
#369 - docs: add Echo v0.1.0 release plan [merged]
#371 - feat(core): advance v0.1 contract evidence and retention [merged]
#379 - feat(core): commit runtime WAL ACK evidence [merged]
#380 - feat(core): expose retained evidence posture on readings [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!
Roadmap child slices created from
docs/design/wal-wsc-durability-roadmap.mdand deduped under this retained-evidence durability umbrella.- GP4 Retained Evidence Durability: [GP4-S1] Retained Ref Crosswalk #569, [GP4-S2] Durable Retained Blob Tier #570, [GP4-S3] WAL-After-Retention Commit Ordering #571, [GP4-S4] Retained Evidence WSC Export #572, [GP4-S5] App-Safe Missing Retention Semantics #573.
Related existing issues remain linked from the child bodies where relevant: #512, #513, #517, #522.
Closing from the 2026-07-03 issue fate audit. The useful work here is complete or superseded by the current GitHub-native release/goalpost structure; active follow-through now lives in the narrower open Echo issues.
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/v0.1.0/PLATFORM_retained-evidence-durability-boundary.mdOriginal lane:
v0.1.0Original legend:
PLATFORMOriginal backlog card
Retained Evidence Durability Boundary
Status: v0.1.0 release blocker.
Depends on:
Why now
Echo can expose retained-evidence posture, but posture is not the same claim as
durable recovery. The release proof needs explicit language and tests that
distinguish "the runtime knows this reading was missing" from "the runtime can
recover this material after restart."
Required behavior
Echo must distinguish:
from the current read model;
semantic coordinate, and commit anchor can survive restart;
reading, receipt, or artifact;
Acceptance criteria
evidence.
WAL/WSC evidence.
posture, not empty success.
digest match.
Test plan
reported as a successful empty read.
advertised as durable.
lookup identity stay separate.
Non-goals
into one noun.