Workflow

    Promote the Xyppy plugin through separate proof gates

    How repository health, durable hosting, ChatGPT metadata, in-host rendering, commerce decisions, and production operations remain independently verified instead of being collapsed into one launch claim.

    source verificationdurable hostingdeveloper modecommerce gateruntime proofXyppy Print This

    Workflow diagram

    Swipe horizontally to inspect the full diagram.

    Part of project

    Xyppy Print ThisParent project
    Promote the Xyppy plugin through separate proof gatesThis workflow
    Workflow diagramRendered with the workflow
    Workflow

    Promote the Xyppy plugin through separate proof gates

    9 steps
    1. Verify clean source main with typecheck, tests, build, docs, MCP contract, and checkout-safety assertions
      action
    2. Human chooses and authorizes a durable long-running HTTPS host
      decision
    3. Deploy the MCP endpoint and self-contained widget without adding live commerce credentials
      subprocess
    4. Refresh the personal ChatGPT app so current tool and widget metadata are rediscovered
      action
    5. Invoke the installed app and verify current endpoint reachability, tool discovery, and widget rendering
      decision
    6. Capture host-specific proof separately from repository and deployment proof
      action
    7. Human separately chooses Shopify, Stripe, or hybrid and approves image retention and operational ownership
      decision
    8. Keep live checkout disabled until backend, assets, review, and rollback behavior are implemented and verified
      state
    9. Treat cart creation, payment, print production, and fulfillment as later independently evidenced operations
      state

    Related chats

    Related links