← All outcomes
Job briefPack: software-deliveryOutcome: custom-mission

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.

01 / SCOPEWhat ships
  • 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
02 / GOVERNANCEGates that fire
  • 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
03 / RECIPESupported composition parts

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

Operator UI

Role-gated operator workspace for the core mission flow.

billing

Billing

Subscription or plan controls with payment-provider hooks.

evidence-reporting

Evidence & reporting

Evidence-backed reporting and audit-facing surfaces.

04 / DELIVERYInitial WU graph (preview)

Total: 4 WUs · Title: Ship: Custom Job

scaffoldFramework: DeliveryP100 · root
schemaFramework: DataP110 · ↳ prev
uiExperience: WorkspaceP120 · ↳ prev
ciOperations: CI/CDP130 · ↳ prev

Step ids are templated; final WU ids are bound to your workspace when you commit.

05 / COMMITCrossing the line

Sign in to commit this job. Your workspace is created and the initial delivery graph is seeded in one step.