Evidence-backed provisioning across five vendors
Minting one environment crosses providers with different APIs, authorization models, and failure modes: Supabase, GitHub, Slack, Linear, and deployment sinks. Run that as a black box and every failure becomes “run it again and hope.” We made the opposite bet: every step leaves evidence. A mint is an ordered workflow. Each step records status, duration, a provider workflow reference, and the artifacts that show what was created and where. The whole trail is available from the console and from iship status.
Delegation needs receipts.
Blocked is not failed
Some providers require a human approval. A Linear OAuth app is one example. Treating that checkpoint as an error creates needless retries; treating it as a terminal result strands the run. Instead, the step pauses as “Needs you” with one clear action, and the workflow resumes after approval. Ordered steps make that recovery dependable. Everything before the checkpoint remains complete. Everything after it waits. The operator can open the relevant artifact without reconstructing activity across several provider consoles.
Delegation needs receipts
This matters most when a human did not start the mint. An agent provisioning resources on your behalf is acceptable only when you can inspect what was created, which customer-owned account received it, when it happened, and which key initiated the work. Evidence is the difference between delegation and abdication.