docs: design task/role model policy and SA-ROLE delivery DAG

[pcvantol]

Owner-requested architecture increment

Document and retain EP_ROLE_TASK_MODEL_POLICY_V1 under the existing SA-ROLE / SA-F09 line. This is design/roadmap plus offline documentary guards, not implementation or active model allocation.

Design

• Separate optional-role selection (SA-SEL), provider/model/effort binding (SA-ROLE) and execution/capacity authority (existing EP host).
• Explicit matrix for implementation, docs-only work, corrective repair, independent Quality/Security, selected specialists, diagnosis/finalization reasoning and no-LLM deterministic control targets.
• First shipping slice: qualified different model/effort profiles on the existing EP-managed Codex/session adapter. No required API subscription or automatic metered fallback; other adapters remain independently qualified extensions.
• Logical capability/profile/assignment/admission/invocation/observation contracts reuse EP effective profiles and CENTRAL. Deterministic precedence, constrained overrides, actual capability checks and unchanged in-flight snapshots.
• Requested/resolved/translated/observed settings remain distinct. Unknown model or usage is not fabricated. Full Q/S rubrics, read-only independence and current candidate/profile binding remain mandatory.
• Finite qualified fallback is not retry authority: no blind alternate after MAY_HAVE_HAPPENED, reviewer shopping, new repair budget, or raised host timeout ceilings.
• EP Operations Console administration, five languages, safe preview/activation/readback and historical explanation; no replacement for Workspace or Forge planning policy.
• Comparative quality/latency/usage qualification required before active real-model bindings. No live comparisons or model IDs selected now.

Roadmap / artifacts

New architecture, scoped roadmap and documentary JSON graph: 7 RMP nodes, 16 future RMT scenario families. Existing SA nodes/edges/statuses/evidence remain unchanged; SA-ROLE completion additionally references RMP-Q. Resolution consumes SA-CTX/SA-OBS and only the required qualified POL-E service subset, not the entire policy programme. Both subagent and policy roadmap navigation point to this same design.

The canonical EP roadmap already links the subagent roadmap and SA-ROLE; no competing master roadmap was added. All runtime nodes stay PLANNED. No first-canary prerequisite, full-SA-Q prerequisite or PR175 activation added.

Evidence and validation

Source inspected and candidate based on 4a6dace73ccc15146a9afe5db356957d8af4bbbb. Candidate: 87df5668d609b81b42c5bb3a9908e33e55cd8d54.

• 10 focused offline documentary checks passed on the local draft, Python 3.13.5, in a partial isolated editing workspace; not a full EP checkout or installed-runtime test.
• Draft staged whitespace check PASS. Three modified originals were reconstructed and verified against their fetched Git blob SHAs before additive edits. Six final uploaded files match the tested local blobs; the final architecture wording was read back separately and will be tested at the exact hosted head. No claim of full local runtime qualification.
• Await actual hosted exact-head validation, version/security and applicable checks; no synthetic PASS or independent-review claim.

NO_BUMP: production code, package/version files, workflows, executable Mission DAGs, CENTRAL/runtime state, installed services, credentials, providers and other repositories remain unchanged. Normal protected delivery only, no bypass. This PR neither starts the canary nor resets any authority/budget.

[pcvantol]

Finale controle op exact 87df5668d609b81b42c5bb3a9908e33e55cd8d54, base nog 4a6dace73ccc15146a9afe5db356957d8af4bbbb:

• Vergelijking toont uitsluitend de zeven bedoelde documentatie/DAG/testbestanden (863 toevoegingen, 1 verwijdering); geen runtime, versie, workflow of andere repository gewijzigd.
• Tien nieuwe offline documentaire tests op de lokale draft opnieuw PASS met Python 3.13.5; staged whitespace check PASS. De gecombineerde SA/RMP-afhankelijkheden zijn resolvable en acyclisch. De eerder vermelde beperking blijft: zes geüploade blobs matchen de lokaal gecontroleerde bytes, de finale architectuurtekst is afzonderlijk remote teruggelezen; hosted qualification hieronder hoort bij de echte PR-candidate. Geen lokale volledige EP-/installed-/modelqualification claim.
• Engineering Platform validation: SUCCESS, https://github.com/pcvantol/engineering-platform/actions/runs/34696354448 . De vier browser-shards zijn geslaagd; de afzonderlijke conditionele UI-GOLDEN-LOCALIZATION-job is SKIPPED en wordt niet als PASS geteld.
• CodeQL: SUCCESS, https://github.com/pcvantol/engineering-platform/actions/runs/34696354446 .
• Security baseline: SUCCESS, https://github.com/pcvantol/engineering-platform/actions/runs/34696354473 .
• Golden Qualification: SUCCESS, https://github.com/pcvantol/engineering-platform/actions/runs/34696354444 .
• Trusted Delivery: SUCCESS, https://github.com/pcvantol/engineering-platform/actions/runs/34696354520 ; de eigen workflow zette Owner Authorization op SUCCESS / niet vereist voor deze LOW/NORMAL-risk paden.
• TDE observe: SUCCESS, https://github.com/pcvantol/engineering-platform/actions/runs/34696354456 ; observe-only.

Geen reviews of open reviewthreads aangetroffen. Dit is een eigen diff-/evidencesamenvatting, geen onafhankelijke approval of synthetisch reviewbewijs. Normale PR-merge met expected-head; geen bypass.

Inhoudelijke afsluiting: 11 taakklassen, 7 RMP-implementatienodes en 16 toekomstige kwalificatiescenario's; originele SA-ROLE dependencies en SA-F09-status/evidence blijven behouden. POL-E wordt als benodigde gekwalificeerde subset hergebruikt. Expliciete same-Codex eerste levering, geen verplichte API-subscriptie, geen ambiguïteitsfallback/reviewer-shopping/budgetreset of verhoogde hosttimeouts. Requested/resolved/observed zijn onderscheiden; Consolebeheer gebruikt dezelfde EP-services.

Dit levert architectuur en roadmap, NIET actieve routing, nieuwe modellen of providerkwaliteitbewijs. NO_BUMP; alle RMP-runtimewerk blijft PLANNED. PR175, primaire installs/CENTRAL, bestaande grants en live canary blijven ongewijzigd. De oorspronkelijke pending-CI-regel is hiermee opgevolgd door daadwerkelijke finale resultaten.