From 9135ae9c5958e6e8190557edcf05b1c3baad437a Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 21 Oct 2026 08:48:22 +0200 Subject: [PATCH] TEN-WP-0013: wave-2 resource right-sizing receiving workplan Receiving workplan for the 2026-10-21 node allocation review (RESOURCE-WP-0008-T03 / CUST-WP-0071-T03). Wave-2 apply is human-gated; no manifest changes. WORK-RECORDS.md regenerated from staged sources. Co-Authored-By: Claude Opus 5.5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 8340@bnt-lap001 Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c --- WORK-RECORDS.md | 2 + ...TEN-WP-0013-wave2-resource-right-sizing.md | 54 +++++++++++++++++++ 2 files changed, 56 insertions(+) create mode 100644 workplans/TEN-WP-0013-wave2-resource-right-sizing.md diff --git a/WORK-RECORDS.md b/WORK-RECORDS.md index b40d48f..354aac3 100644 --- a/WORK-RECORDS.md +++ b/WORK-RECORDS.md @@ -22,6 +22,7 @@ | workplan | TEN-WP-0010 | finished | — | workplans/TEN-WP-0010-mutable-grouping.md | | workplan | TEN-WP-0011 | finished | — | workplans/TEN-WP-0011-security-layer-conformance.md | | workplan | TEN-WP-0012 | blocked | — | workplans/TEN-WP-0012-external-conformance-waits.md | +| workplan | TEN-WP-0013 | ready | — | workplans/TEN-WP-0013-wave2-resource-right-sizing.md | | task | TEN-WP-ADHOC-2026-07-24-T01 | done | — | workplans/ADHOC-2026-07-24.md | | task | TEN-WP-ADHOC-2026-10-03-T01 | done | — | workplans/ADHOC-2026-10-03.md | | task | TEN-WP-0001-T01 | done | — | workplans/TEN-WP-0001-statehub-bootstrap.md | @@ -78,6 +79,7 @@ | task | TEN-WP-0011-T06 | done | — | workplans/TEN-WP-0011-security-layer-conformance.md | | task | TEN-WP-0012-T01 | wait | — | workplans/TEN-WP-0012-external-conformance-waits.md | | task | TEN-WP-0012-T02 | wait | — | workplans/TEN-WP-0012-external-conformance-waits.md | +| task | TEN-WP-0013-T01 | wait | — | workplans/TEN-WP-0013-wave2-resource-right-sizing.md | | intake | TEN-IN-0001 | closed | yellow | docs/intakes/residuals.md | | intake | TEN-IN-0002 | closed | red | docs/intakes/residuals.md | | intake | TEN-IN-0003 | closed | — | intakes/intakes.md | diff --git a/workplans/TEN-WP-0013-wave2-resource-right-sizing.md b/workplans/TEN-WP-0013-wave2-resource-right-sizing.md new file mode 100644 index 0000000..2139f20 --- /dev/null +++ b/workplans/TEN-WP-0013-wave2-resource-right-sizing.md @@ -0,0 +1,54 @@ +--- +id: TEN-WP-0013 +type: workplan +title: "Wave-2 resource right-sizing from the 2026-10-21 allocation review" +domain: infotech +repo: tenant-engine +status: ready +flavor: implementation +owner: claude +topic_slug: netkingdom +created: "2026-10-21" +updated: "2026-10-21" +related: + - CUST-WP-0071 + - RESOURCE-WP-0008 +--- + +# TEN-WP-0013 — Wave-2 resource right-sizing from the 2026-10-21 allocation review + +Receiving workplan in `tenant-engine` for the wave-2 request changes below. + +Origin: the 2026-10-21 node allocation review (`RESOURCE-WP-0008-T03`, feeding `CUST-WP-0071-T03`). Per the founder's 2026-10-21 delivery interview (`the-custodian/docs/decisions/2026-10-21-cust-wp-0071-delivery-interview.md`) the small adjustments form wave 2: one receiving task per owner repo, applied later in a batch. Applying wave 2 needs a separate founder approval, so every cluster-write task here is a human-gated `wait`. This file changes no manifest. + +## Apply the reviewed request changes + +```task +id: TEN-WP-0013-T01 +status: wait +priority: medium +needs_human: true +blocking_reason: "Wave-2 cluster write; founder approval for wave 2 not yet given (2026-10-21 interview)" +``` + +Values are pod-aggregate figures from the budget file (7-day window ending 2026-10-21T06:08Z). Limits stay unchanged unless stated. + +| Workload (ns/name) | Pods | CPU request | CPU limit | CPU p95/peak 7d (m) | Memory request | Memory limit | Mem p95/peak (Mi) | Throttle | Action | +|---|---:|---:|---:|---:|---:|---:|---:|---:|---| +| `tenant-engine/tenant-engine` | 1 | 25m → **5m** | 300m | 2.4/2.6 | 48Mi → **48Mi** | 192Mi | 53.1/67.8 | 0.0 | decrease | + +Source and container detail: + +- `tenant-engine/tenant-engine`: Deployment `tenant-engine`, container `tenant-engine`, `deploy/base/tenant-engine.yaml` (25m/48Mi, limits 300m/192Mi). Memory p95 53Mi is slightly above the 48Mi request (below the change threshold); the owner may raise it to 64Mi. + +Evidence: resource-control `docs/evidence/2026-10-21-node-allocation-review/2026-10-21-node-budget.md` (+ `.json`, commit `3d9b1bd`). Rule: CPU = max(floor, p95x1.5, peakx0.5) rounded up to 5m; memory request = 7d p95 working set x1.15 (only when the change is at least 64Mi). + +Steps: + +1. Map the pod-aggregate proposal onto the named container(s) in the source file; where a workload has several containers or pods, split by the per-pod figures in `2026-10-21-workload-usage.json` and keep the sum at the proposed value. +2. Prepare the source change as a reviewed commit (no push, no sync) and record the before values here. +3. Apply only inside the batched wave-2 rollout, after founder approval, through the owner's normal deploy path (ArgoCD sync or documented helm/kubectl apply). + +Verification: `kubectl -n get pod -o jsonpath='{..resources}'` shows the new requests; pods Ready with no new restarts or OOMKilled over 24h; for CPU decreases the throttle ratio and request latency stay at or below the 7d baseline; node request total drops by the expected delta. + +Rollback: revert the source commit and re-sync/re-apply; the before values in the table above are the rollback target. Keep before/after `kubectl get -o yaml` captures as the receipt.