Compute, storage and other resources procurement and cost minimization for railiance workloads.
Find a file
tegwick 13c2b82281 feat: restate the backup case in ITC-CAP terms; add evidence basis; publish consumption-mode signal
Three things.

1. CANON RESTATEMENT (info-tech-canon's ask after accepting our demand)
data/capability/platform-audit-storage.json restates the backup case against
ITC-CAP 0.2.0: requirement with profile, targets and the failure-domain
constraint that decided the procurement; two provisions (data.object and
data.backup); all four data.backup evidence hooks satisfied and measured; and
consumption in native units — GB, hours, tokens — with unknown never zero.

tools/capability.py reads their capabilities.yaml directly rather than copying
it, so drift in either repo fails here. The requirement asks D5, the provision
is D4, and the review reports below_requirement rather than inflating maturity.

2. EVIDENCE BASIS (tools/basis.py, docs/evidence-basis.md)
Every value declares how it was obtained on an ordered scale: invoiced,
measured, quoted, derived, projected, estimated, assumed, unknown. A derived
value resolves to the weakest basis among its inputs, so precise arithmetic
cannot launder weak assumptions.

First application is a finding about our own biggest decision: the Scaleway vs
Hetzner comparison, EUR 29.14/month stated to the cent, grades "indicative" —
1 of 4 load-bearing values evidenced, weakest "assumed". The direction is
robust; the magnitude is a model output. The cheapest fix is recording real
operator hours, not better arithmetic.

3. CONSUMPTION-MODE SIGNAL (railiance-platform RAILIANCE-WP-0017)
settlement.py gains a consumption-mode command projecting statements into the
signal they consume; make consumption-mode PERIOD=YYYY-MM publishes
data/consumption-mode/current.json. Currently an empty list: no live charges for
2026-09, so no entity is restricted. Publishing the empty list makes that an
assertion rather than an absence, which their contract distinguishes. The
validator fails if the published signal is stale.

185 tests pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-15 18:42:06 +02:00
data feat: restate the backup case in ITC-CAP terms; add evidence basis; publish consumption-mode signal 2026-08-15 18:42:06 +02:00
docs feat: restate the backup case in ITC-CAP terms; add evidence basis; publish consumption-mode signal 2026-08-15 18:42:06 +02:00
examples feat: operational resource procurement facility 2026-08-14 13:15:02 +02:00
schemas feat: migrate live inventory to five-facet 0.3 and close WP-0006 2026-08-15 02:47:31 +02:00
tests feat: restate the backup case in ITC-CAP terms; add evidence basis; publish consumption-mode signal 2026-08-15 18:42:06 +02:00
tools feat: restate the backup case in ITC-CAP terms; add evidence basis; publish consumption-mode signal 2026-08-15 18:42:06 +02:00
workplans feat: migrate live inventory to five-facet 0.3 and close WP-0006 2026-08-15 02:47:31 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-15 02:48:40 +02:00
.gitignore feat(portfolio): complete RESOURCE-WP-0003 T06 optimization cases and T07 reporting 2026-08-14 09:28:44 +02:00
.repo-classification.yaml Seed resource control and backup procurement plan 2026-08-10 17:46:39 +02:00
AGENTS.md Seed resource control and backup procurement plan 2026-08-10 17:46:39 +02:00
INTENT.md docs: reef attribute refs and resource object workplan 2026-08-14 15:44:44 +02:00
Makefile feat: restate the backup case in ITC-CAP terms; add evidence basis; publish consumption-mode signal 2026-08-15 18:42:06 +02:00
SCOPE.md chore: refresh WORK-RECORDS and SCOPE after WP-0006 finished 2026-08-15 02:48:19 +02:00
WORK-RECORDS.md chore: refresh WORK-RECORDS and SCOPE after WP-0006 finished 2026-08-15 02:48:19 +02:00