Scope#
WS09-001 defines a canonical endpoint class strategy so RunPod serverless
routing can be selected by:
- asset complexity,
- control complexity,
- runtime profile.
This strategy establishes the contract used by later WS09 tasks that introduce dedicated endpoint families, warm/cold policies, SLOs, and cost attribution.
Research and Existing Implementation Alignment#
Current implementation baseline was audited in:
apps/isis/generation-api/src/routes/jobs.ts(provider compatibility and endpoint-family support matrix)infra/runpod/endpoints/desired-state.json(current managed endpoint keys)docs/infrastructure/runpod-integration.md(operator-facing RunPod model)
Finding: endpoint family routing existed, but there was no first-class strategy artifact tying endpoint classes to complexity/runtime dimensions.
Deliverables#
- Added canonical endpoint class strategy contract in API
RUNPOD_ENDPOINT_CLASS_STRATEGYnow defines:- class inventory (
active+planned) - asset/control/runtime complexity tiers
- generation-type targets per class
- representative controls and rationale
- routing heuristics with preferred/fallback class paths
- class inventory (
- Exposed strategy via provider compatibility API
GET /api/v1/jobs/providers/compatibilitynow includesendpointClassStrategyin response payload.- Added regression assertion in route tests to guarantee presence of active and planned class entries.
- Updated infrastructure documentation
- Expanded
docs/infrastructure/runpod-integration.mdwith an explicit endpoint class strategy table and complexity/runtime dimensions for operators.
Verification Commands#
bash
pnpm --filter @isis/generation-api exec vitest run src/routes/jobs.spec.ts --reporter=dot
node scripts/isis/generate-remediation-backlog-v2.mjs
node scripts/isis/validate-v2-compliance-gate.mjs
Result#
WS09-001 is now implemented with a concrete endpoint class strategy contract
that links workload complexity to routing classes and is visible in API and
infrastructure documentation.