I.
Wiki article
Reading · 1 mindocs/atlas-catalog-unification
Atlas Catalog Unification reference
The catalog runtime has been unified into @a5c-ai/atlas as the
Continue reading
Nearby pages in the same section.
adapters docsAgent-Adapter ↔ Babysitter IntegrationAgent Layer Gaps — Full Agent StackContributor ReferenceArticlesHarness AssimilationAtlas Graph ↔ Library Gap ReportBabysitter BlueprintsBabysitter Plugins → Blueprints RenameBabysitter CLI & SDK Examplesa5c Development DocumentationEvil FallbacksGenty Features Backlog: Adversarial Gap Analysisgenty Stack RenamesUsing the Babysitter GitHub ActionUsing Babysitter with Claude Code GitHub ActionsUsing Babysitter with Codex GitHub ActionsUsing Babysitter with Gemini CLI GitHub ActionsHardcoded Harness/Target Gaps — Should Be Derived from Atlas GraphHarness Features Backlog: Gap Analysis (Restructured)Here Be Dragons — Babysitter MonorepoHermes Agent Deep ResearchPackage and Plugin Docs MapAgent PluginsReferenceReference ReposContinuous Release PipelineRepositories Using BabysitterBabysitter Run History InsightsSupermemory Deep ResearchTesting StrategyBabysitter User GuideBabysitter v6: The Orchestration Platform Goes Universala5c.ai V6 Spec And RoadmapWorkspace Validation Map
Atlas Catalog Unification
The catalog runtime has been unified into @a5c-ai/atlas as the @a5c-ai/atlas/catalog subpath export. Only the atlas workspace owns catalog source, build, package metadata, and CI coverage.
Current State
| Surface | Location | Purpose |
|---|---|---|
@a5c-ai/atlas | packages/atlas/ | Graph schema, indexer, YAML loader, CLI, webui |
@a5c-ai/atlas/catalog | packages/atlas/src/catalog/ | Agent discovery, capability metadata, SDK integration |
Import Guidance
Runtime consumers should import catalog APIs from @a5c-ai/atlas/catalog. Package manifests should depend on @a5c-ai/atlas because the catalog API is a subpath export of that package.
import {
getCatalogDiscoverySnapshot,
getFallbackHarnessMetadata,
listPluginTargetDescriptors,
} from "@a5c-ai/atlas/catalog";Build And Test
The catalog surface is validated as part of atlas and the downstream contract matrix:
npm run build --workspace=@a5c-ai/atlas
npm run test:atlas-catalog-contractsThe final migration state keeps catalog source, tests, generated discovery snapshot, package exports, docs, and CI metadata under atlas.