agent-domain-routing-unity
Agent Domain Routing (theonekit-unity)
Section titled “Agent Domain Routing (theonekit-unity)”Loads when Unity files, Unity skills, agents or plans are touched. The Unity/DOTS task-pattern→agent lookup table lives in the on-demand skill t1k-unity-base-agent-domain-routing — invoke it (or /t1k:find-skill "<query>") when resolving “which agent owns this task.”
Unity lanes do NOT default to t1k-fullstack-developer (engine-agnostic fallback only). “Implement” with no narrower row is t1k-unity-base-feature-implementer (or implementer for engine code); copying/importing original assets and authoring prefab builders is t1k-unity-base-asset-porter; shader work in a mono project (no dots-core installed) is t1k-unity-base-developer, which is what bare role shader resolves to; a DOTS project reaches t1k-unity-dots-core-shader through the shader-dots overlay key.
Review and parity have owners. A PR/fix-delta review of Unity C# is t1k-unity-base-pr-reviewer (read-only). A parity or closure audit, or porting a confirmed deviation against reference evidence, is t1k-unity-base-parity-porter, which refuses unless the brief states owner-authorised or non-commercial research.
The constraints below fire unsummoned before the lookup.
Tie-break. A task naming a DOTS concept (ISystem, ECB, Burst, SubScene, t1k unity dots) takes its row in the routing skill above even when it also touches Assets/Scripts/. Everything else keeps core’s rows.
A parallel fan-out does NOT license a generalist. One editor holds the project at a time, so a specialist’s own per-change verification cannot run per lane; route to the specialist and state verification is centralized to the orchestrator (ai-velocity-batch-compile-unity.md — implement blind, verify once).
A phase lane is led by t1k-unity-base-lane-lead. Never t1k-hard-coder (native, for a hard fix that already failed once), never a native reflex. The lead edits nothing; it cuts the phase into routed hops of one or two files each, each with its own validated contract, disjoint within a wave. A brief the lane gate denies is split again and re-routed, never answered by spawning t1k-unity-base-developer natively. A 1-3 hop lane gets no lead; 6 leads at most. Editor work leaves the lane as a BLOCKED HOP; review is t1k-unity-base-pr-reviewer’s. § “Phase lanes” in the routing skill.
An Editor loop is not one brief for a cheap hop. One measurable step per hop, a progress file the orchestrator reads, final Editor verification native, mr-wait-memory.cjs --check-only before spawning. § “Editor loops” in the routing skill.
Related
Section titled “Related”t1k-routing-unity.json · t1k-unity-base-agent-domain-routing · docs/agent-domain-routing-unity.md