chore(consistency): renormalize lifecycle state [auto]

Updated by fix-consistency on 2026-09-14:
  - workplan status: ready → active
This commit is contained in:
custodian-sync 2026-09-14 11:46:22 +02:00
parent 1fff598581
commit b39cb476e7

View file

@ -4,7 +4,7 @@ type: workplan
title: "Size Railiance workloads from actual demand and establish a weekly allocation review"
domain: infotech
repo: the-custodian
status: ready
status: active
owner: the-custodian
topic_slug: custodian
created: "2026-09-11"
@ -53,7 +53,7 @@ plan. Do not treat reservation headroom as measured spare processing capacity.
```task
id: CUST-WP-0071-T01
status: todo
status: done
priority: high
assignee: the-custodian
state_hub_task_id: "4ae8eb8d-f8c5-5256-ae50-c323cfd73d7a"
@ -78,6 +78,17 @@ Done when a repeatable observation reconciles current allocation totals,
identifies missing/stale signals without reporting them as zero demand, and
updates the existing portfolio evidence with accountable owner references.
**Done 2026-09-14.** Repeatable command:
`python3 scripts/reconcile_railiance_allocation.py`. Evidence:
`docs/evidence/2026-09-14-allocation-reconcile.{json,md}` plus
`docs/evidence/namespace-ownership.yaml`. Live totals: 4000m capacity,
3985m scheduled, 25m pending, 15m residual (not a guarantee). Host and
cluster CPUs counted once. Unknown namespaces listed, then filled for
`approval-engine` and `vergabe-demo-company`. Zero-request workloads named.
STATE-WP-0091 preflight refuses (15m remaining). Forgejo omission remains a
Prometheus/dashboard gap, not a Kubernetes API gap. RESOURCE-WP-0007 already
updated reef-railiance-k3s owner evidence.
## Measure the Vergabe prototype under representative pilot use
```task