tegwick
10b988fa1c
The backup is procured and proven, so the loop runs on real evidence. - data/actuals/2026-08.json: first real observation. database 0.6365 GB, stored 0.0066 GB over 8 objects, backup success 1/1, restore RTO 1.08 min. Five proxies null, each with a named owner in measurement_gaps. - data/thresholds/platform-audit-storage.json + tools/thresholds.py: budget variance, abnormal growth, stale backup, unused commitment. Fail-closed — an unmeasured value is reported as unmeasured, never as within. - financial_exchange.py gains a usage mode emitting technical_usage records to fin-hub, with measurement gaps carried through and no infrastructure amount: fin-hub owns the booked fact and a null is never sent as 0.00. - observation schema 0.2 allows null cost and usage proxies; variance.py fails closed rather than reporting a 100% favourable variance on a missing amount. - platform-audit-storage: ordered -> active, commissioned 2026-08-14, on operational fact rather than on the purchase. The optimization case is now approved by the founder. That needed a schema change: Host Europe never supplied written terms, so options gained excluded/exclusion_reason. Previously an unevaluable alternative blocked its case forever, leaving the record claiming no decision while the bucket was in production. An excluded option keeps its unknowns and must say what would bring it back. August produces no variance and should not: the decision forecast starts at 2026-09, so August is a commissioning baseline. Threshold run is 2 within, 1 not applicable, 6 unmeasured, 0 breaches. Also fixes a pre-existing test failure: reef-storage consumers_actual is now rapp-postgres, which the assertion still expected to be empty. 136 tests pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 2026-08.json | ||
| README.md | ||
Monthly technical usage observations
After each provider billing period, add YYYY-MM.json conforming to
schemas/monthly-resource-observation.schema.json with
record_type: usage_observation. These records contain technical and labor
observations. Authoritative booked financial actuals come from fin-hub and are
referenced during reconciliation rather than copied into a second ledger.
Set forecast_ref to the forecast file used for the decision. Evidence should
identify, without secrets, the provider usage export/invoice, PostgreSQL/CNPG
measurement, restore drill, and internal time record.
Required proxies are database GB, provider stored GB, WAL GB, restore egress, write/read requests, infrastructure invoice cost, internal labor hours/cost, and total cost. Also capture backup success, maximum observed RPO, and restore RTO when available.
Run:
make variance ACTUAL=data/actuals/YYYY-MM.json