Skip to content

v0.1.0 Replay And DIND Proof #526

Description

@flyingrobots

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/TEST_v0.1.0-replay-dind-proof.md
Original lane: v0.1.0
Original legend: TEST

Original backlog card

v0.1.0 Replay And DIND Proof

Status: narrow local release witness implemented; broader DIND gate remains.

Depends on:

Why now

The release sentence depends on deterministic replay. Echo must prove that the
local contract-host path can reproduce receipts, outcomes, and readings from
the retained package, submission, scheduler, and reading evidence.

Required witness

Add a local replay/DIND proof for the app contract path:

same package
+ same accepted submissions
+ same scheduler policy
+ same retained evidence
-> same receipts, outcomes, and readings

Acceptance criteria

  • The external proof fixture participates in replay.
  • Accepted submissions replay with stable submission identity.
  • Tick receipts reproduce for the same scheduler-owned decision set.
  • Reading envelopes reproduce for the same query basis, vars, aperture, and
    observer identity.
  • Missing retained material produces obstruction rather than fake success.
  • cargo xtask dind or a narrower documented release witness covers the
    path.

Implemented local slice

cargo xtask test-slice contract-path-release now runs the explicit local
contract path release witness: installed contract pipeline replay, reference
trusted host loop, and the serious external-consumer-shaped fixture. The command
is a narrow release witness, not a replacement for broader DIND CI gates.

Non-goals

  • Do not require distributed replica import.
  • Do not implement settlement shells.
  • Do not require full observer-rights revelation proofs.

Activity

  1. coderabbitai commented on Jun 1, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #323 - Witnessed suffix admission evaluator [merged]
    #358 - feat(core): add admission evidence boundaries [merged]
    #368 - feat(core): connect installed contract intent pipeline [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 plan command 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!

  2. flyingrobots commented on Jun 19, 2026

    @flyingrobots
    OwnerAuthor

    Roadmap child slices created from docs/design/wal-wsc-durability-roadmap.md and deduped under this replay/DIND umbrella.

    Related umbrellas: #521, #522, #519, #510, #517.

  3. flyingrobots commented on Jul 3, 2026

    @flyingrobots
    OwnerAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    lane:releaseMethod lane release.legend:testMethod legend test.runtimeRuntime corespecSpec/Design document

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions