The go-live operator pack is now browsable.
This page makes the launch-readiness surface readable without exposing private operator logs. Runtime durability, settlement readiness, execution targets, delivery posture, and the current blocker set stay visible in one place so a builder can see what still needs closeout before launch.
Launch state
The go-live pack keeps the launch posture explicit instead of implying readiness too early.
- State: current
- Blocking issues: 0
- Configured execution targets: 0
- Configured treasury profiles: 0
- Callback delivery enabled: undefined
- Runtime recovery posture: current
- Native settlement ready: undefined
- Checkout ingress security ready: undefined
JSON pack · Go-live summary · Runtime durability · Delivery summary
Blocking issues
These are the current operator-facing blockers the go-live pack exposes.
Settlement readiness · Treasury destinations · Checkout security
Next actions
The pack stays concrete about the next operator moves instead of hiding them behind vague launch language.
Operator shell · Receipt · Activation · Release kit · Money-in · Claim · Governance disputes
Related surfaces
Go-live works best when it sits next to the rest of the release path and the claim path.
Start · Try · Stack · Catalog · Money-in · Operator shell · Proof · Claim · Releases · Site map
Payment posture
The launch pack keeps money-in, repeat-use, and human procurement paths explicit so the go-live decision remains bounded.
- Machine primary: current
- Repeat-use primary: current
- Human primary: current
- External fronts: 0