coulomb/resource-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
resource-control/WORK-RECORDS.md
tegwick 17de8b831e feat(portfolio): fold in RAILIANCE-WP-0016 apps-pg evidence 
First delegated evidence from RESOURCE-WP-0003-T04 to land. railiance-platform
delivered apps-pg capacity, utilization, consumers, and the apps-pg-dbbytes-v1
allocation driver, and correctly delivered no EUR.

- data/resources/apps-pg.json: real capacity; allocation unattributed -> shared
  under apps-pg-dbbytes-v1; second consumer vergabe-teilnahme registered
- data/control-cycle/apps-pg-2026-09-base.json: first operational control-cycle
  record in the repository
- examples/control-cycle/apps-pg-*.json retired; the invented fixture collided
  with the real record's identifier
- data/portfolio-coverage-2026-08-14.json: gap marked delivered with three
  residual unknowns still open

The real evidence exposed a design gap in the T05 schema: v0.1 required a number
for every cost field, so recording genuine usage without a booked cost meant
inventing one. Schema 0.2 permits null costs, null unattributed_eur, a technical
unattributed_share, and null measurements. Null is unknown, never zero; an
unknown component makes the total null rather than the sum of the known parts;
and the comparator classifies unknown amounts as data_quality instead of
computing a variance. Existing 0.1 records are not rewritten.

apps-pg is now measured (idle at 5.8% of volume) and attributed, and remains
unpriced: delivered technical evidence does not create a booked cost.

86 tests pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-14 09:36:57 +02:00

2.6 KiB
Raw Blame History

Work Records — resource-control

Generated by statehub fix-consistency (CUST-WP-0061-T04, work-record stage 3). Do not edit by hand — edit the source file/block listed for each record and re-run fix-consistency to refresh this index. Archived workplans are omitted; closed decisions/intakes/engagements stay listed so recently-resolved work is still visible. [auto]

Kind ID Status Lane Source
workplan RESOURCE-WP-0001 finished — workplans/RESOURCE-WP-0001-statehub-bootstrap.md
workplan RESOURCE-WP-0002 active — workplans/RESOURCE-WP-0002-procure-postgres-backup-storage.md
workplan RESOURCE-WP-0003 finished — workplans/RESOURCE-WP-0003-managed-infrastructure-portfolio-control.md
task RESOURCE-WP-0001-T01 done — workplans/RESOURCE-WP-0001-statehub-bootstrap.md
task RESOURCE-WP-0001-T02 done — workplans/RESOURCE-WP-0001-statehub-bootstrap.md
task RESOURCE-WP-0001-T03 done — workplans/RESOURCE-WP-0001-statehub-bootstrap.md
task RESOURCE-WP-0002-T01 progress — workplans/RESOURCE-WP-0002-procure-postgres-backup-storage.md
task RESOURCE-WP-0002-T02 progress — workplans/RESOURCE-WP-0002-procure-postgres-backup-storage.md
task RESOURCE-WP-0002-T03 wait — workplans/RESOURCE-WP-0002-procure-postgres-backup-storage.md
task RESOURCE-WP-0002-T04 wait — workplans/RESOURCE-WP-0002-procure-postgres-backup-storage.md
task RESOURCE-WP-0002-T05 wait — workplans/RESOURCE-WP-0002-procure-postgres-backup-storage.md
task RESOURCE-WP-0002-T06 todo — workplans/RESOURCE-WP-0002-procure-postgres-backup-storage.md
task RESOURCE-WP-0002-T07 todo — workplans/RESOURCE-WP-0002-procure-postgres-backup-storage.md
task RESOURCE-WP-0003-T01 done — workplans/RESOURCE-WP-0003-managed-infrastructure-portfolio-control.md
task RESOURCE-WP-0003-T02 done — workplans/RESOURCE-WP-0003-managed-infrastructure-portfolio-control.md
task RESOURCE-WP-0003-T03 done — workplans/RESOURCE-WP-0003-managed-infrastructure-portfolio-control.md
task RESOURCE-WP-0003-T04 done — workplans/RESOURCE-WP-0003-managed-infrastructure-portfolio-control.md
task RESOURCE-WP-0003-T05 done — workplans/RESOURCE-WP-0003-managed-infrastructure-portfolio-control.md
task RESOURCE-WP-0003-T06 done — workplans/RESOURCE-WP-0003-managed-infrastructure-portfolio-control.md
task RESOURCE-WP-0003-T07 done — workplans/RESOURCE-WP-0003-managed-infrastructure-portfolio-control.md