coulomb/railiance-cluster
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-cluster/workplans/RAIL-BS-WP-0014-state-hub-surge-headroom.md
codex 551a898e4d
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Use canonical RAIL-BS-WP-0014 id for the STATE-WP-0091 residual. 
Assistant: grok
Assistant-Session: 01a09dc1-b21e-77e1-919e-fcad2f82b267
2026-09-14 10:17:39 +02:00

1.1 KiB
Raw Blame History

id type title domain repo status owner topic_slug origin origin_ref created updated related
RAIL-BS-WP-0014 workplan Keep node remaining CPU honest for State Hub surge and pending demand financials railiance-cluster proposed codex railiance residual STATE-WP-0091 2026-09-14 2026-09-14
RCLUSTER-WP-0014
STATE-WP-0091
CUST-WP-0071

Residual from STATE-WP-0091. State Hub now refuses promotion when remaining CPU cannot cover its 100m API surge, and when unrelated pending pods would eat the 5m sliver above 105m. Cluster observation must keep publishing allocatable, allocated, and pending-unrelated demand. 105m remaining is not capacity admission for factory or other zero-request workloads.

Include pending pods in capacity observations

id: RAIL-BS-WP-0014-T01
status: todo
priority: high

Extend tools/observe_cluster_resources.py / make cluster-observe so the published observation names pending unscheduled pods and their requests. State Hub's preflight already consumes that shape. Do not treat residual millicores as a scheduling guarantee.