Design resource-vector and provider-aware admission policies

[eric-tramel]

Priority Level

Low

Epic: #645
Depends on: #641, #646, #644, #657, #649, #650
Related: #647, #648, #654
Target branch: epic/645-async-scheduling while the epic is active.

Source of Truth

Specification details live in PR #658 under plans/645/, especially task-admission.md, request-admission.md, capacity-model.md, observability.md, benchmark-plan.md, and issue-map.md. This issue tracks the design-spike slice and gates only.

Design Scope

Produce a decision-ready design for future resource-vector and provider-aware task-admission policies. This issue is design-only unless a follow-up implementation issue is explicitly created.

This issue owns:

• deciding whether resource-vector internals stay scheduler-internal or require any public metadata additions beyond Add opt-in SchedulingMetadata for generator resource scheduling #641;
• the minimal SchedulerResourceKey / SchedulerResourceRequest shape for a later implementation;
• mapping resolved metadata from Add opt-in SchedulingMetadata for generator resource scheduling #641/Ingest SchedulingMetadata into async scheduler grouping #646 into scheduler resource requests without exposing scheduler internals as plugin API;
• defining how task-stage provider/model awareness avoids duplicating request-stage AIMD admission from Refactor model-call request control into RequestAdmissionController #657;
• liveness, release/accounting, cancellation/error, telemetry, and benchmark requirements for a later implementation;
• recording rejected alternatives.

Quality Gates

• No resource-vector implementation lands as part of this design issue.
• The design preserves the task/request admission split and consumes request pressure only through read-only snapshots if needed.
• The design keeps FairTaskQueue responsible for ready ordering, not resource ownership.
• The future implementation acceptance bar includes liveness, no permit leaks, multi-resource fairness tests, stale/retry/salvage behavior, correlated telemetry compatibility, and Build async scheduling benchmark harness for admission and fairness work #649 benchmark evidence.
• Benchmark matrix covers asymmetric provider/model capacities, different dominant resources, neutral single-resource workloads, heavy-root compatibility, and correlated scheduler/request traces.

Validation

Close with an accepted design document or plan update that cross-references plans/645, lists open questions, records rejected alternatives, and defines the exact follow-up implementation issue(s) and evidence gates.