Skip to content

GP1: define Xyph Gate Alpha evidence vocabulary fixtures #78

Description

@flyingrobots

Campaign

Xyph Gate Alpha

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

Goalpost 1

Freeze the minimum fixture vocabulary for the first Xyph Gate Alpha evidence exchange.

This is a fixture vocabulary freeze, not a broad Continuum protocol freeze.

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?

Continuum-owned deliverables

Define fixture-level shapes for:

  • WitnessCapsuleV0
  • ApertureV0
  • HorizonDiffV0
  • ObligationV0
  • evidence posture fields
  • digest domain names for the fixture artifacts

The vocabulary must be able to name:

  • Edict proof-plan digest
  • Echo trace receipt digest
  • Xyph policy verdict ref
  • open or satisfied obligations
  • missing, partial, redacted, stale, or unsupported evidence

Acceptance criteria

  • One fixture id appears across all GP1 sibling issues: payment_receipt_required@0.
  • The capsule can wrap base/head Gate evidence refs.
  • Missing evidence is represented as an obligation, not a warning string.
  • Evidence posture distinguishes what is native, translated, witnessed, claimed, missing, or unsupported.
  • The issue explicitly says what is deferred to later Continuum protocol work.

Non-goals

  • No final protocol family freeze.
  • No ZK proof vocabulary.
  • No global admission service.
  • No product UI.
  • No GitHub enforcement.

Sibling issues

To be filled after GP1 sibling anchors exist.

Activity

  1. coderabbitai commented on Jul 8, 2026

    @coderabbitai
    🔗 Related PRs

    #18 - Align Continuum sibling runtime doctrine [closed]
    #20 - Rewrite README around witnessed causal history [closed]


    📝 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

    GP1 sibling anchors

    GP1 closes when these four fixtures agree on the same payment_receipt_required@0 evidence vocabulary and digest/ref story.

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