Skip to content

Gate B - Networked Causal Suffix Exchange #591

Description

@flyingrobots

Contract

Echo 1.0 must demonstrate networked causal suffix exchange between Echo and git-warp over a real network boundary. The exchange must preserve witnessed causal history, admit or reject deterministically, and reconstruct state from received history rather than synchronizing mutable state snapshots.

Owner

Canonical repository: echo for the Echo release gate.

Contract partner: git-warp owns its peer implementation and compatibility evidence.

Executable check

A release-gate workflow or command must run the bidirectional network exchange fixture and return pass/fail.

Expected final shape:

cargo xtask test-slice echo-1.0-suffix-exchange

Required evidence

  • Echo commit SHA.
  • git-warp commit SHA.
  • Network trace or transcript.
  • Exported suffix bundle digests.
  • Admission/rejection receipts from both peers.
  • Reconstructed-state proof from received history.
  • CI workflow run URL or artifact bundle.

Negative cases

  • Duplicate suffix.
  • Reordered suffix.
  • Stale suffix.
  • Tampered suffix.
  • Interrupted exchange followed by resume.

Compatibility set

Must pin exact Echo and git-warp commits, protocol versions, and bundle schema versions used by the proof.

Pass rule

Pass only when both directions succeed over the network boundary, all negative cases deterministically reject or resume as specified, and the evidence bundle pins both peer identities and commit SHAs.

Activity

  1. added this to the Echo 1.0 milestone on Jun 20, 2026
  2. coderabbitai commented on Jun 20, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #323 - Witnessed suffix admission evaluator [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]
    #529 - Add Hello Echo demo and docs lifecycle policy [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!

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

    featureFeature umbrella (epic)lane:releaseMethod lane release.legend:platformMethod legend platform.release:echo-1.0Echo 1.0 release convergence scoperuntimeRuntime corespecSpec/Design document

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions