Published pipeline record.
The latest pipeline record, with freshness visible.
This page reads the runner's latest published status artefact. It reports what that recorded run did and when; it does not prove that the VPS service is currently running. A stale, failed or missing record remains explicit.
The pipeline is designed for an unattended daily cadence spanning source refresh, recomputation, candidate-track certification, publication, deployment and proof-chain anchoring. This surface reports only the last published record: its run time, outcome, stages, collectors, publication and chain state, alerts and history. A record older than the freshness limit is stale, and a missing record renders unavailable rather than implying a healthy runner. Candidate-track certification is not the benchmark trusted gate; CSI values remain provisional while that separate gate fails closed.
Pipeline status
Fetching the latest run record. If no status artefact has been published this page will say so; it never shows a fabricated run.
The pipeline fails closed at every stage.
Each stage runs only if the stage before it succeeded, and every artefact it publishes carries the methodology version and the content-addressed hashes that make it reproducible. A source whose upstream release has not advanced is carried forward and labelled as such; it is never fabricated.
The status artefact is written by a runner and read by this page in the browser. It is a record of one run, not an independent health check of the current VPS service. The benchmark trusted gate is reported separately on the CSI page and still fails closed; the proof ledger, reproducibility and verification pages remain the authoritative record of what was published.
- Success
- Every stage completed and the publication changed or was confirmed.
- No change
- Every stage completed and no source, publication or chain state changed.
- Degraded
- Every stage completed and the served publication is intact, but the run raised a warning that must not be absorbed silently, for example the chain diverging from the anchored prefix, a low served volume, a calendar-year rollover or a non-200 smoke check; the reasons are listed on the page and the monitor sees the outcome.
- Partial
- A stage failed after the publication or the deploy had already succeeded, for example a push or an anchoring step; the alerts list says which, and the served publication is intact.
- Failed
- A stage failed and the stages after it did not run; the previous publication stays in place.
- Stale
- The last run finished longer ago than the freshness limit, so the pipeline may not be running; the last recorded run is still shown.