Attach resource-control allocation review to sizing work
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
Reject generated-only commits / generated-commit-guard (push) Successful in 18s

This commit is contained in:
codex 2026-10-19 15:10:06 +02:00
parent 96be6d028e
commit b63425d85a
2 changed files with 26 additions and 2 deletions

View file

@ -0,0 +1,15 @@
{
"case_id": "case:cross-owner:CUST-WP-0071-T03:resource-control",
"scenario_type": "cross_owner_wait",
"beneficiary_workplan_id": "CUST-WP-0071",
"beneficiary_task_id": "CUST-WP-0071-T03",
"obligor_repo": "resource-control",
"obligor_workplan_id": "RESOURCE-WP-0008",
"state": "observed",
"reason": "Owner review active: initial unbounded synthetic envelope exceeds node budget; consume isolated capped comparison, reconcile shared demand and return qualified proposal/keep decision with owner records.",
"owner_source_commit": "565b16e",
"observed_at": "2026-10-19T13:09:28.130592+00:00",
"worker_injection_enabled": false,
"authorization": "User explicitly authorized worker delegation or direct provider-repository implementation for this goal.",
"progress_receipt_id": "381ba7f7-35c6-49f4-8805-4503df060ccd"
}

View file

@ -126,8 +126,8 @@ id: CUST-WP-0071-T03
status: wait
priority: high
assignee: the-custodian
depends_on: [CUST-WP-0071-T01, CUST-WP-0071-T02]
blocking_reason: "Await CUST-WP-0071-T02 representative sample; Forgejo/runner demand and zero-request workload review need owner input (railiance-cluster, railiance-forge, resource-control)."
depends_on: [CUST-WP-0071-T01, CUST-WP-0071-T02, RESOURCE-WP-0008]
blocking_reason: "RESOURCE-WP-0008 is actively reviewing the synthetic comparison and current node budget; representative shared-service/runner demand and zero-request ownership remain explicit inputs. Attached to case:cross-owner:CUST-WP-0071-T03:resource-control."
state_hub_task_id: "6dc67558-eb1e-5bb6-a667-986f884dd495"
```
@ -459,3 +459,12 @@ comparison uses an isolated app container with the existing 1000m/1Gi limits.
Source review also requested bounded cleanup on driver exceptions and explicit
measurement gaps on sampler failure. T02 stays progress while that comparison
and review proceed; human workflow acceptance remains separate.
Resource-control has accepted the provider work as `RESOURCE-WP-0008`, source
commit `565b16e`, with an initial allocation review and reference from the
existing reef portfolio record. Replacing the observed 60m request with the
unbounded experimental 1950m request would yield 5495m scheduled against 4000m;
that scenario is rejected as an allocation, not used to justify procurement.
The cross-owner case is retained at
`docs/changes/CUST-WP-0071/resource-control-review-handoff.json`, progress receipt
`381ba7f7-35c6-49f4-8805-4503df060ccd`. No worker-injection service was enabled.