0001: Runtime orchestration

Kind: reference.

Status: Accepted. Decision date: 2026-09-26. Recorded: 2026-09-26.

Acceptance authority: the prior supervisor accepted issue 146, revision 2. That receipt records supervisor acceptance, not a human approval mark. The current Codex supervisor authorized this record through issue 137.

Context

Root modules mixed orchestration, field instructions and backend framing. The accepted ownership map assigned each concern to an existing or explicitly named package. This record preserves its runtime decision without extending that map.

Decision

Use thin typevet.runtime facades for orchestration. Do not introduce a typevet.engine layer. Keep pure domain rules in typevet.domain and port contracts in typevet.ports. Keep backend framing in outbound adapters.

Consequences

Runtime composes lower layers without owning evaluation workflows. The import policy enforces the layer order. Later, commit 58bfc8a added the runtime-to-evaluation prohibition for issue 190. That guard is current enforcement, not part of the original decision. Run uv run lint-imports to check these boundaries.

Issue 148 assigned the migration and compatibility requirements. Commit 68c0dda implemented runtime ownership and Gemma framing separation. The current runtime package exposes the orchestration surface. This record makes no new runtime change and does not prove live model quality.