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.
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 workflowWorkflow
Promote the Xyppy plugin through separate proof gates
- Verify clean source main with typecheck, tests, build, docs, MCP contract, and checkout-safety assertionsaction
- Human chooses and authorizes a durable long-running HTTPS hostdecision
- Deploy the MCP endpoint and self-contained widget without adding live commerce credentialssubprocess
- Refresh the personal ChatGPT app so current tool and widget metadata are rediscoveredaction
- Invoke the installed app and verify current endpoint reachability, tool discovery, and widget renderingdecision
- Capture host-specific proof separately from repository and deployment proofaction
- Human separately chooses Shopify, Stripe, or hybrid and approves image retention and operational ownershipdecision
- Keep live checkout disabled until backend, assets, review, and rollback behavior are implemented and verifiedstate
- Treat cart creation, payment, print production, and fulfillment as later independently evidenced operationsstate