Skip to content

GP1: define shadow Gate aperture and policy fixtures #79

Description

@flyingrobots

Campaign

Xyph Gate Alpha

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

Goalpost 1

Define the minimum Xyph fixture vocabulary for a shadow Gate run over the first protected workflow.

This is product-shape work over fixture refs, not enforcement or UI.

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?

Xyph-owned deliverables

Define fixture-level shapes for:

  • aperture config for payment_reliability@0
  • protected workflow mapping for payment_receipt_required@0
  • policy config with ALLOW, SHADOW, BLOCK, and OVERRIDE_WITH_DEBT
  • base/head HorizonDiffV0 expected output
  • obligation fixture for durable_receipt_evidence_required
  • expected shadow verdict for the unsafe payment path

The future command target is:

xyph gate explain-fixture payment_receipt_required@0

Acceptance criteria

  • One fixture id appears across all GP1 sibling issues: payment_receipt_required@0.
  • Xyph references EchoProofPlanV0, TraceRunReceiptV0, and WitnessCapsuleV0 by digest/ref.
  • The first result is SHADOW, not a required merge blocker.
  • Missing evidence becomes an obligation with owner/severity/TTL placeholder fields.
  • The fixture vocabulary can drive GP2 without additional product terminology.

Non-goals

  • No GitHub App or merge blocking.
  • No Workbench UI.
  • No Worker repair loop.
  • No Verify product.
  • No ZK verification.

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