CI/CD Platform · View 13 of 22 · Runtime
The ordering that matters
- The sandbox uploads the artefact and reports its outcome. The attestor then signs from the inputs the platform observed. Provenance therefore records what the platform saw, not what the build said about itself.
- The credential is requested by the job and issued by the broker against a job-scoped token. Nothing long-lived is ever present in the sandbox to be stolen.
- Destroying the sandbox is the last step, and it is asynchronous: the result is already sealed, so teardown cannot fail a successful job.
The failure branch
- The red message is lease expiry. A runner that goes silent is detected by its lease, not by the absence of a report, and the job is re-dispatched.
- A job is never reported successful on the basis of an absent runner. That rule is what makes a partition resolve to re-dispatch rather than to a false green.
Assumptions
- Queued to first step p50 ≤ 8 s, p99 ≤ 60 s; 12,000 sandbox creations per minute at peak.