coulomb/resource-control
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

feat(portfolio): fold in RAILIANCE-WP-0016 apps-pg evidence

Browse source 
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>
This commit is contained in:
tegwick 2026-08-14 09:36:57 +02:00
parent b64b5683df
commit 17de8b831e
16 changed files with 908 additions and 71 deletions
Download patch file Download diff file Expand all files Collapse all files

17
workplans/RESOURCE-WP-0003-managed-infrastructure-portfolio-control.md
View file

@ -287,6 +287,23 @@ resources with no contract dates at all, and six of seven resources sharing
- [x] At least two optimization cases complete the evidence-to-decision loop.
- [x] Portfolio reporting exposes unknown and unattributed values explicitly.
## Post-completion record
2026-08-14: `railiance-platform` delivered `RAILIANCE-WP-0016`, the first
delegated evidence from T04 to land. Folded in: the apps-pg resource record now
carries real capacity and the `apps-pg-dbbytes-v1` allocation driver, the first
operational control-cycle record replaced the illustrative apps-pg fixture, and
coverage moved to `data/portfolio-coverage-2026-08-14.json` with the gap marked
delivered and its 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 was
impossible without inventing one. Schema 0.2 permits null costs, a null
unattributed amount, a technical `unattributed_share`, and null measurements;
the comparator reports unknown amounts as `data_quality` rather than computing a
variance. Existing 0.1 records were not rewritten. Evidence:
`docs/evidence/RESOURCE-WP-0003-apps-pg-evidence-foldin-2026-08-14.md`.
## Standing gate
Both optimization cases are `blocked_on_evidence` by design: the mechanism is