Skip to content

Goalpost 0: scope EchoProofPlanV0 for Xyph Gate Alpha #135

Description

@flyingrobots

Campaign

Xyph Gate Alpha

Coordination anchor: flyingrobots/continuum#77

Goalpost 0

Decide whether the current uncommitted EchoProofPlan skeleton becomes the start of EchoProofPlanV0, and define the smallest Edict-owned contract needed for the first Gate Alpha vertical slice.

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.

Edict-owned slice

Emit a deliberately narrow EchoProofPlanV0 for the protected workflow fixture.

Expected local artifact fields:

  • targetIrDigest
  • contractBundleDigest or reviewed bundle subject digest
  • tickBound
  • structuralBound
  • capabilityFootprint
  • obstructionTaxonomyVersion
  • traceShapeVersion = TraceRunReceiptV0

Acceptance criteria

  • There is one checked fixture or golden for payment_receipt_required@0.
  • The plan digest is deterministic for the fixture.
  • The plan names the Echo trace shape it expects.
  • Unsupported/general proof-plan behavior is explicitly rejected or deferred.
  • The implementation path accounts for the existing local proof_plan.rs skeleton without silently treating it as complete.

Non-goals

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

Activity

  1. coderabbitai commented on Jul 8, 2026

    @coderabbitai
    🔗 Related PRs

    #41 - Add Gate C admission boundary checks [merged]
    #67 - Add Echo Target IR lowering [merged]
    #110 - Prepare v0.11.0-alpha.1 release [merged]
    #128 - Parse obstruction strand continuations [merged]
    #132 - Lower obstruction requirements to Echo Target IR [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 Jul 8, 2026

    @flyingrobots
    OwnerAuthor

    Goalpost 0 dependency posture — 2026-07-07

    Edict PR #134 is parked as non-blocking for Goalpost 0.

    The obstruction/counterfactual taxonomy matters for EchoProofPlanV0, but this first issue can define a provisional obstructionTaxonomyVersion field and align it after #134 lands. The immediate requirement is to decide how the current local proof_plan.rs skeleton should evolve into a deliberately narrow fixture-backed proof-plan contract.

  3. flyingrobots commented on Jul 8, 2026

    @flyingrobots
    OwnerAuthor

    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: #136

    GP1 freezes the fixture proof-plan vocabulary. GP0 remains the historical campaign grounding record.

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

    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