Goalpost 0: scope TraceRunReceiptV0 for Xyph Gate Alpha

[flyingrobots]

Campaign

Xyph Gate Alpha

Coordination anchor: flyingrobots/continuum#77

Goalpost 0

Define the smallest Echo-owned trace receipt shape that can support the first Xyph Gate Alpha shadow verdict.

Fixed campaign facts

• Protected workflow fixture: payment_receipt_required@0
• Aperture id: payment_reliability@0
• Target Echo trace shape: TraceRunReceiptV0
• First policy question: can a payment path reach capture:success without a durable receipt obligation being satisfied?
• Commercial surface target: Xyph Gate shadow verdict, not an enforcing blocker yet.

Echo-owned slice

Expose or fixture a deterministic trace receipt for the protected workflow path.

Expected local artifact fields:

• run identity and basis refs
• ordered TraceRowV0 entries
• per-row tick, operation, capabilityFootprint, reads, writes, obstruction
• terminal stateRootAfter
• retained evidence refs or explicit missing-retention posture
• digest domain for the trace receipt

Acceptance criteria

• Echo can produce or validate one fixture trace for payment_receipt_required@0.
• The trace shape is boring, deterministic, and inspectable.
• The receipt can be referenced by a Continuum WitnessCapsuleV0 fixture.
• The receipt can be compared by Xyph as base/head evidence.
• The issue explicitly states whether PR feat(warp-core): add WAL evidence segment catalog #644 must land first or can be parked.

Non-goals

• No product-facing Workbench explanation.
• No ZK proof backend.
• No general replay closure claim.
• No application nouns in Echo core.
• No GitHub merge blocking.

[coderabbitai]

🔗 Related PRs

#145 - AIΩN bridge doc + tick receipts (#144) [merged]
#329 - Stack Witness 0001 fixture-backed jedit walking skeleton [merged]
#339 - feat(core): add obstruction receipt skeleton [merged]
#379 - feat(core): commit runtime WAL ACK evidence [merged]
#582 - docs: define the Echo 1.0 release contract and move live planning to GitHub [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!

[flyingrobots]

Goalpost 0 dependency posture — 2026-07-07

Echo PR #644 is parked as non-blocking for Goalpost 0.

For this issue, TraceRunReceiptV0 may begin as a fixture-backed receipt shape. The Goalpost 0 requirement is to name the minimal trace contract Xyph and Continuum can reference, not to finish WAL durability first.

WAL durability becomes a hard dependency later when the campaign moves from fixture-backed trace evidence to Goalpost 2 Core Trace and Goalpost 6 retained evidence verification.

[flyingrobots]

GP0 is complete.

Final campaign decisions:

• Campaign: Xyph Gate Alpha
• Protected workflow: payment_receipt_required@0
• Aperture: payment_reliability@0
• Proof-plan shape: EchoProofPlanV0
• Trace shape: TraceRunReceiptV0
• Evidence envelope: WitnessCapsuleV0
• Diff shape: HorizonDiffV0
• Obligation shape: ObligationV0
• First policy question: can capture:success happen without durable receipt obligation satisfaction?
• Product mode: shadow verdict before enforcement

Successor GP1 issue: #646

GP1 freezes the fixture trace receipt vocabulary. GP0 remains the historical campaign grounding record.