Readiness
Is your environment ready for deployment?
Ready for review. No launch blockers found. Continue with the path or readiness detail.
Can continue
Yes for readiness review
Blocked by
No launch blocker in the readiness gate
Missing next
Continue with the path or readiness detail
Runtime boundary
No handler, endpoint, callable, or production write is created here.
StartContinue the path.
Rollout gatesView heavier deployment checks.
Protocol / verifyPublic receipt protocol, schema, keys, and verification tools.
Draft store
Dedicated self-service store configured
Store requirement
Dedicated store is required before production
Production writes
No production write from this readiness page
Launch gate
Launch gate is clear
Open checks
Review only what needs attention.
01Pre-execution Boundary
Draft planning cannot mutate production boundary runtime.
Draft work stays review-only until a production rollout is explicitly approved.
- Self-service writes only to self_service_drafts.
- Deployment review request is review-only and sets production_write=false.
- Formal boundary units and runtime calls remain outside the self-service draft path.
02Database Isolation
Draft storage has a dedicated enterprise isolation path.
Self-service draft storage is separated from production boundary execution.
- SELF_SERVICE_DATABASE_URL is the preferred draft-store connection.
- REQUIRE_SELF_SERVICE_DATABASE_URL=true prevents production fallback before launch.
- Local/development refuses Railway DB connections unless explicitly overridden for smoke testing.
03Verification Surface
Machine-verifiable receipts remain independently checkable.
Receipts remain verifiable without re-implementing the signing path in self-service.
- Public verification material is served through the standard protocol JWKS.
- Receipts use the established signature flow rather than a self-service reimplementation.
- The readiness surface links to the protocol spec instead of duplicating core receipt logic.
04Deployment Review
Enterprise rollout is explicit, inspectable, and reversible before production.
Rollout stays gated by owner, environment, support, and rollback readiness.
- A saved coverage plan becomes the review packet.
- Expansion moves are appended as draft coverage, not custom implementation work.
- Production deployment should require owner, environment, SLA, rollback, and support confirmation.
Boundary posture
Sensitive context stays with the host.
Craton does not need the full business payload to fix a boundary. The host sends the minimum boundary fields, receives a machine-verifiable result, and keeps sensitive context inside its own system.
Minimum boundary fieldsPartner, gate, system scope, authority context, and external reference are enough for the boundary check.
No payload custodySend only the fields needed for the boundary check. Craton does not need your full business payload. Do not send full transaction files, contract bodies, medical records, credentials, private keys, or your datasets.
Machine-verifiable receiptThe host and downstream systems verify the signed receipt and commitment ID without exposing the original case payload.
Readiness detail
Deployment, integration, and boundary posture.
1. Scope
Map one production-bound boundary path and receive a draft boundary object plus API access context.
2. Review
Request deployment review. This stores intent only and does not touch production boundary runtime.
3. Deploy
Production rollout happens only after environment, owner, SLA, rollback, and security review are confirmed.
4. Continue
After the initial scope is completed, continue current coverage or expand from the current path.
{
"draft_store_isolation": "dedicated",
"environment": "production",
"launch_gate": {
"passes_enterprise_db_gate": true,
"recommended_require_flag": true,
"requires_self_service_database_url": true
},
"local_production_db_override_enabled": false,
"primary_database_url_configured": true,
"production_like": true,
"production_write_from_self_service": false,
"require_self_service_database_url": true,
"self_service_database_url_configured": true,
"status": "ready_for_review"
}