Infra / VPS

Parity, drift, and missing host evidence

This route now says exactly what it knows: repo parity is real, while live host telemetry still needs to be wired.

SourceRepo drift artifact22d old

ParityAlignedactive-work profile

Repos tracked44 in sync

CoverageRepo parityhost health not wired yet

Parity confidence

Repo drift is visible now, but live VPS health should not be implied until the host artifact exists.

The correction here is about honesty first: show real repo parity, then add CPU, RAM, disk, backups, and incidents only when the source is live.

38%Infra coverage

Repo drift is wired. Host health and backup proof are still missing.

Tracked repos

Drift artifact

pume-agentsin sync

main · local afbd127 · remote afbd127

pume-webin sync

main · local 288a8b8 · remote 288a8b8

pume-agents-backendin sync

main · local f0d39a2 · remote f0d39a2

pume-internal-ops-evidencein sync

main · local b8b9104 · remote b8b9104

Repo parity4/4 repos

All in sync

This infra lane is now grounded in the real repo drift artifact rather than invented host metrics.

Last drift report22d old

25 Feb

Freshness is explicit because a parity report is only useful if you can trust when it last ran.

Tracked reposactive-work profile

Current evidence covers repo/workspace parity only; host CPU, RAM, disk, and backups still need a live adapter.

Coverage

Current cockpit

Tracked repos aligned100%

Host telemetry coverage0%

Backup evidence coverage0%

Notes

Truth-first

Parity is currently clean across tracked reposclean

4 of 4 repos match remote main in the active-work profile.

Host health is still missing from the cockpitgap

This page should not pretend to know CPU, RAM, backups, or incidents until the VPS status artifacts are wired in.