docs: close live projection convergence and retain capacity residual
Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
parent
b5920d85e3
commit
b0063abe18
3 changed files with 373 additions and 3 deletions
57
workplans/STATE-WP-0091-release-headroom.md
Normal file
57
workplans/STATE-WP-0091-release-headroom.md
Normal file
|
|
@ -0,0 +1,57 @@
|
|||
---
|
||||
id: STATE-WP-0091
|
||||
type: workplan
|
||||
title: "Check release headroom and retain a capacity allocation handoff"
|
||||
domain: infotech
|
||||
repo: state-hub
|
||||
status: ready
|
||||
owner: codex
|
||||
topic_slug: infotech
|
||||
created: "2026-09-10"
|
||||
updated: "2026-09-10"
|
||||
related: [STATE-WP-0090, RCLUSTER-WP-0014, RESOURCE-WP-0003, HFACT-WP-0001]
|
||||
---
|
||||
|
||||
Residual from STATE-WP-0090: revision 61 failed with Insufficient CPU even though
|
||||
runtime usage was modest. Revision 63 succeeded after a measured same-service
|
||||
MCP request adjustment. The single 4,000m node still reserves 3,895m (97.4%),
|
||||
leaving 105m against a 100m API surge. Existing cluster collection and portfolio
|
||||
contracts are finished inputs, not workplans to reopen. No factory capacity
|
||||
admission follows from this release.
|
||||
|
||||
## Check scheduling headroom before State Hub promotion
|
||||
|
||||
```task
|
||||
id: STATE-WP-0091-T01
|
||||
status: todo
|
||||
priority: high
|
||||
```
|
||||
|
||||
Add a read-only preflight to the existing promotion path. Reuse Kubernetes and
|
||||
railiance-cluster capacity evidence; check effective pod requests, init/overhead,
|
||||
placement constraints, rollout surge and migration-hook ordering. Report observed
|
||||
freshness, remaining CPU/memory and precise insufficient-capacity reasons before
|
||||
starting Helm. Do not claim a scheduling guarantee from an aggregate sum or lower
|
||||
requests automatically. Prove the observed 65m refusal and 105m narrowly sufficient
|
||||
case, including unrelated concurrent demand. Keep atomic rollback.
|
||||
|
||||
## Review sustained service demand and hand off shared capacity
|
||||
|
||||
```task
|
||||
id: STATE-WP-0091-T02
|
||||
status: todo
|
||||
priority: high
|
||||
```
|
||||
|
||||
State Hub owns its workload demand and release requirement. Check MCP latency,
|
||||
errors, CPU contention and coverage after the 50m-to-10m request change; its 500m
|
||||
limit, memory and replicas remain unchanged. The initial 1,078 five-minute samples
|
||||
are partial coverage, not a full week. Propose a durable release margin and hand
|
||||
any shared allocation or provisioning change to live records with railiance-cluster,
|
||||
railiance-platform and resource-control using their existing authority contracts.
|
||||
Include HFACT T01/T04 factory demand, other zero-request workloads and host usage;
|
||||
current aggregate reservation alone is not capacity admission. No unrelated
|
||||
allocation, procurement or scaling is authorized by this workplan. Close only
|
||||
after the repeatable preflight and explicit receiving work records are verified.
|
||||
|
||||
Evidence: docs/evidence/2026-09-10-projection-convergence.json.
|
||||
Loading…
Add table
Add a link
Reference in a new issue