Skip to content

t1k-routing-unity-dots-core.json

priority: 91

Module overlay for theonekit-unity dots-core — the DOTS half of unity routing. Holds <role>-dots keys, selected by core’s resolveRole() when the project fact architecture reads dots; with no fact, or a fact naming no suffixed key, resolution falls back to the bare keys in t1k-routing-unity.json (p90). Kit-scoped filename so the flattened fragment cannot collide with another kit’s.

RoleAgent
compile-doctor-dotst1k-unity-dots-core-compile-doctor
debugger-dotst1k-unity-dots-core-debugger
environment-dotst1k-unity-dots-core-environment
implementer-dotst1k-unity-dots-core-implementer
optimizer-dotst1k-unity-dots-core-optimizer
reviewer-dotst1k-unity-dots-core-reviewer
shader-dotst1k-unity-dots-core-shader
tester-dotst1k-unity-dots-core-tester
validator-dotst1k-unity-dots-core-validator

Raw JSON (ground truth)
{
"_doc-fact-resolution": "Core resolves the `architecture` fact ITSELF: the p100 project fragment (`t1k-config-unity-project.json`, `{ \"priority\": 100, \"architecture\": \"dots\" }`) first, then the kit's declarative fallback `architectureDetect` in `.claude/t1k-config-unity.json` (`com.unity.entities` in `Packages/manifest.json` or `packages-lock.json`, `searchDepth: 1`). Nothing has to be run first. `.claude/scripts/detect-unity-architecture.cjs` (base module, `files.scripts`) INSPECTS those signals — reporting the declaration's verdict, marker density as ADVISORY, and a warning when the two disagree — and writes the p100 fact only under an explicit `--set dots|mono`.",
"_doc-no-fileRouting": "`fileRouting` and `errorRecovery` are deliberately NOT repeated here. Their values are role keys, resolved through `roles` AFTER the architecture split, so the p90 entries already reach these agents on a DOTS project — duplicating them would create a second source of truth for the same pattern.",
"_doc-reviewChecklist": "P10 (theonekit-core#3128) routing-fragment key, override-by-priority like `roles`. `readReviewChecklist()` picks the highest-priority declaration across every `t1k-routing-*.json` in `.claude/`; this fragment only exists on a consumer that installed the `dots-core` module, so a mono-only project never sees this value. The path is written in the INSTALLED (flattened) form — `skills/<id>/...`, no `modules/dots-core/` prefix — because the resolver reads it against a live `.claude/` directory, which for every real consumer is the flattened layout (`docs/module-system.md` § \"Flattening\").",
"_doc-scoped-keyword-harvest": "The KEYWORD half of this design is core's, not this file's (unity#1146). `resolveRole()` was always architecture-conditional, but `buildIndex()` used to shred a suffixed key like an ordinary compound role key — publishing its prefix token (`debugger`) into the GLOBAL keyword index, so a DOTS specialist was suggested on any project, and leaving the agents whose prefix a p90 bare key already owned (`reviewer`, `optimizer`, `environment`) with NO keyword at all. Core now harvests these keys into an architecture-scoped overlay and merges it only when the project's resolved `architecture` fact matches, which is what makes the intent above real: on a DOTS project the seven-plus overlay agents own their role words and win; anywhere else they contribute nothing. Two consequences for anyone editing `roles` here — (1) the suffix must name an architecture the install DECLARES (`architectureDetect[].value` in `t1k-config-unity.json`, or a pinned `t1k-config-*-project.json` fact), never a free-form word, or the key is treated as an ordinary compound role and its prefix leaks again; (2) each key's BASE must also exist as a bare key in the p90 fragment, because that bare key is the mono lane's total fallback (`tests/test-architecture-role-routing.cjs` pins both properties).",
"_doc-why-suffixed-keys-only": "Nine roles, nine agents — one suffixed key per shipped dots-core agent, and no bare key. A bare key here would shadow the p90 lane for EVERY project, not just DOTS ones (routing fragments merge by priority, and this one is higher), which is exactly the misroute this overlay exists to fix.",
"description": "Module overlay for theonekit-unity `dots-core` — the DOTS half of unity routing. Holds `<role>-dots` keys, selected by core's `resolveRole()` when the project fact `architecture` reads `dots`; with no fact, or a fact naming no suffixed key, resolution falls back to the bare keys in `t1k-routing-unity.json` (p90). Kit-scoped filename so the flattened fragment cannot collide with another kit's.",
"priority": 91,
"registryVersion": 1,
"reviewChecklist": "skills/t1k-unity-dots-core-architecture/references/dots-review-checklist.md",
"roles": {
"compile-doctor-dots": "t1k-unity-dots-core-compile-doctor",
"debugger-dots": "t1k-unity-dots-core-debugger",
"environment-dots": "t1k-unity-dots-core-environment",
"implementer-dots": "t1k-unity-dots-core-implementer",
"optimizer-dots": "t1k-unity-dots-core-optimizer",
"reviewer-dots": "t1k-unity-dots-core-reviewer",
"shader-dots": "t1k-unity-dots-core-shader",
"tester-dots": "t1k-unity-dots-core-tester",
"validator-dots": "t1k-unity-dots-core-validator"
}
}