Skip to content

GP1: define EchoProofPlanV0 fixture and digest domain #136

Description

@flyingrobots

Campaign

Xyph Gate Alpha

GP0 anchor: #135
Workspace plan: /Users/james/git/profunctoroptics/DEMO.md

Goalpost 1

Define the minimum Edict proof-plan fixture vocabulary for the first Xyph Gate Alpha workflow.

This issue should account for the existing local proof_plan.rs skeleton without treating it as complete.

Fixed campaign facts

  • 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?

Edict-owned deliverables

Define fixture-level shape for EchoProofPlanV0 with at least:

  • targetIrDigest
  • contractBundleDigest or reviewed bundle subject digest
  • tickBound
  • structuralBound
  • capabilityFootprint
  • obstructionTaxonomyVersion
  • traceShapeVersion = TraceRunReceiptV0
  • proof-plan digest domain

The proof plan should support base/head comparison for the protected workflow fixture.

Acceptance criteria

  • One fixture id appears across all GP1 sibling issues: payment_receipt_required@0.
  • The proof-plan digest is deterministic for the fixture.
  • The plan names the Echo trace shape it expects.
  • Unsupported or general proof-planning behavior is explicitly rejected or deferred.
  • Edict PR Define obstruction and counterfactual taxonomy #134 remains non-blocking for GP1 unless this issue deliberately promotes it.

Non-goals

  • No general proof planner.
  • No ZK constraints.
  • No Echo execution.
  • No Continuum participant policy.
  • No Xyph UI.

Sibling issues

To be filled after GP1 sibling anchors exist.

Metadata

Metadata

Assignees

No one assigned

    Labels

    campaign:xyph-gate-alphaCross-repo Xyph Gate Alpha vertical-slice campaign

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions