What happened
On PR #4221, the code agent wrote AIResource (capital I) throughout the migration design document instead of the correct AiResource (lowercase i). The review agent ran 3 times and never caught the error. The human domain expert (gabemontero) flagged this across 5 inline comments, making it the most impactful review finding. The boost workspace AGENTS.md (lines 66–69, 237–244) correctly points agents to aiAssetTaxonomy.ts as the taxonomy source of truth, but does not enumerate the actual entity kind names or their casing in the naming conventions section (lines 165–176).
What could go better
The boost workspace AGENTS.md has a naming conventions section that lists config namespaces, permission names, resource types, DB tables, and extension points — but omits the most important domain-specific names: the entity kinds themselves. Agents writing or reviewing documentation about entity kinds have no quick reference for canonical casing. They would need to proactively read aiAssetTaxonomy.ts to discover that the kind is AiResource not AIResource. Issue #4335 proposes adding naming fidelity guidance to the code agent definition, but that would not help the review agent. Adding the entity kind names directly to the workspace AGENTS.md naming section would benefit both code and review agents. Confidence: high — the naming error is a direct consequence of the missing reference, and the fix is low-risk and additive.
Proposed change
In workspaces/boost/AGENTS.md, extend the existing naming conventions section (around line 165) to include the canonical entity kind names from aiAssetTaxonomy.ts. Add a subsection like:
### Entity kind names (exact casing required)
- `AiResource` — agents, skills, rules (NOT `AIResource`)
- `AiModelServerAPI` — model servers (`kind: API, spec.type: ai-model-server`)
- `API` — MCP servers (`spec.type: mcp-server`)
- `Resource` — tools, vector stores
This gives both code and review agents an immediate reference without requiring them to read the taxonomy source file.
Validation criteria
After the change, the next 3 code or fix agent runs on boost workspace issues involving entity kinds should use correct casing for entity kind names. Review agent runs on documentation referencing entity kinds should flag casing mismatches against the AGENTS.md reference.
Generated by retro agent from #4221
What happened
On PR #4221, the code agent wrote
AIResource(capital I) throughout the migration design document instead of the correctAiResource(lowercase i). The review agent ran 3 times and never caught the error. The human domain expert (gabemontero) flagged this across 5 inline comments, making it the most impactful review finding. The boost workspace AGENTS.md (lines 66–69, 237–244) correctly points agents toaiAssetTaxonomy.tsas the taxonomy source of truth, but does not enumerate the actual entity kind names or their casing in the naming conventions section (lines 165–176).What could go better
The boost workspace AGENTS.md has a naming conventions section that lists config namespaces, permission names, resource types, DB tables, and extension points — but omits the most important domain-specific names: the entity kinds themselves. Agents writing or reviewing documentation about entity kinds have no quick reference for canonical casing. They would need to proactively read
aiAssetTaxonomy.tsto discover that the kind isAiResourcenotAIResource. Issue #4335 proposes adding naming fidelity guidance to the code agent definition, but that would not help the review agent. Adding the entity kind names directly to the workspace AGENTS.md naming section would benefit both code and review agents. Confidence: high — the naming error is a direct consequence of the missing reference, and the fix is low-risk and additive.Proposed change
In
workspaces/boost/AGENTS.md, extend the existing naming conventions section (around line 165) to include the canonical entity kind names fromaiAssetTaxonomy.ts. Add a subsection like:This gives both code and review agents an immediate reference without requiring them to read the taxonomy source file.
Validation criteria
After the change, the next 3 code or fix agent runs on boost workspace issues involving entity kinds should use correct casing for entity kind names. Review agent runs on documentation referencing entity kinds should flag casing mismatches against the AGENTS.md reference.
Generated by retro agent from #4221