Classify the layer
Route the task to UI, dependencies, containers, infrastructure, APIs, auth, AI tools, security, data, or internal policy before choosing a source.
The atlas organizes the registries, package indexes, documentation sources, marketplaces, catalogs, and review checks that agents need before they make implementation decisions.
RegistryRouter uses the atlas to help agents distinguish official implementation sources from discovery material, examples, marketplaces, community lists, and policy-controlled systems.
Route the task to UI, dependencies, containers, infrastructure, APIs, auth, AI tools, security, data, or internal policy before choosing a source.
Use official registries, docs, package indexes, vendor references, and internal catalogs as implementation authority. Treat examples as discovery unless verified.
Surface maintenance, license, pricing, secrets, data access, compatibility, and approval checks before the agent changes the codebase.
The reference spans the systems agents commonly touch when building modern software.
{
"registry": "shadcn/ui",
"layer": "ui_frontend",
"authority_level": "official_install_source",
"cost_model": "free_open",
"best_for": "source-owned UI components",
"risk_checks": [
"accessibility",
"dependencies_added",
"visual_fit",
"license"
]
}The long-form atlas is available as a browsable reference. RegistryRouter is designed to expose the same source intelligence through agent-readable records, policy checks, and preflight reports.