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

Record State Hub MCP 10m as reef evidence, not admission.

Browse source 
RESOURCE-WP-0007: state-hub is an actual consumer. 105m remaining
does not change allocation mode or usable capacity.

Assistant: grok
Assistant-Session: 01a09dc1-b21e-77e1-919e-fcad2f82b267
This commit is contained in:
tegwick 2026-09-14 10:34:27 +02:00
parent 8b88dfde8b
commit 195bcc5c34
2 changed files with 14 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

11
workplans/RESOURCE-WP-0007-state-hub-release-margin.md
View file

@ -4,7 +4,7 @@ type: workplan
title: "Fold State Hub 10m MCP request into reef-railiance-k3s without calling 105m admission"
domain: financials
repo: resource-control
status: proposed
status: finished
owner: codex
topic_slug: railiance
origin: residual
@ -12,6 +12,7 @@ origin_ref: STATE-WP-0091
created: "2026-09-14"
updated: "2026-09-14"
related: [RESOURCE-WP-0003, STATE-WP-0091, RCLUSTER-WP-0014]
state_hub_workstream_id: "a0f4f765-7e63-5af3-b122-0f988fd57c5f"
---
Residual from STATE-WP-0091. State Hub lowered the MCP CPU request 50m → 10m
@ -23,10 +24,16 @@ authorize procurement or scaling.
```task
id: RESOURCE-WP-0007-T01
status: todo
status: done
priority: medium
state_hub_task_id: "0a364c8e-f558-5a84-8487-94ffabb4680d"
```
Record the MCP request change as workload-owned demand on
`reef-railiance-k3s`. Keep booked financial authority in fin-hub. Do not
mark the 105m remainder as available shared capacity.
**Done 2026-09-14.** `data/resources/reef-railiance-k3s.json` now lists
`state-hub` as an actual consumer and records the MCP 10m request as
workload evidence. Allocation mode stays `unattributed`. No capacity metric
was increased and 105m is not treated as shared headroom.