Custom Job.
Constrained recipe composition for a custom mission, without falling back to untyped freeform promises. Default completion is pr-ready. Deploy posture surfaces only once a runtime is connected.
Your current setup carries forward while you choose what to start next.
- 01Governed scaffold + delivery graph seeded from typed recipe parts
- 02Choose from supported recipe parts: operator UI, billing, evidence reporting
- 03Prerequisites still resolve through canonical connectors, runtime, and trust posture
- 04Replay and approval posture stay on the canonical builder contracts
- 01Policy mode: warn
- 02Recipe parts are explicit; unsupported asks stay out of scope
- 03Evidence: launch, approvals, and replay stay attached to the same build run lineage
- 04Default completion: PR opened against main, gates green
Custom jobs stay governed by composing from a typed recipe registry. If your ask needs something outside these parts, the product should say so plainly instead of pretending it can build anything.
Operator UI
Role-gated operator workspace for the core mission flow.
Billing
Subscription or plan controls with payment-provider hooks.
Evidence & reporting
Evidence-backed reporting and audit-facing surfaces.
Total: 4 steps · Plan: Ship: Custom Job
Step names are templated here; the real plan is created in your workspace when you commit.
Sign in to commit this job. Your workspace is created and the initial delivery graph is seeded in one step.