{
  "id": "page:docs-atlas-catalog-unification",
  "_kind": "Page",
  "_file": "wiki/docs/atlas-catalog-unification.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/atlas-catalog-unification/README.md",
    "sourceKind": "repo-docs",
    "title": "Atlas Catalog Unification",
    "displayName": "Atlas Catalog Unification",
    "slug": "docs/atlas-catalog-unification",
    "articlePath": "wiki/docs/atlas-catalog-unification/README.md",
    "article": "\n# Atlas Catalog Unification\n\nThe catalog runtime has been unified into `@a5c-ai/atlas` as the\n`@a5c-ai/atlas/catalog` subpath export. Only the atlas workspace owns catalog\nsource, build, package metadata, and CI coverage.\n\n## Current State\n\n| Surface | Location | Purpose |\n|---------|----------|---------|\n| `@a5c-ai/atlas` | `packages/atlas/` | Graph schema, indexer, YAML loader, CLI, webui |\n| `@a5c-ai/atlas/catalog` | `packages/atlas/src/catalog/` | Agent discovery, capability metadata, SDK integration |\n\n## Import Guidance\n\nRuntime consumers should import catalog APIs from `@a5c-ai/atlas/catalog`.\nPackage manifests should depend on `@a5c-ai/atlas` because the catalog API is a\nsubpath export of that package.\n\n```ts\nimport {\n  getCatalogDiscoverySnapshot,\n  getFallbackHarnessMetadata,\n  listPluginTargetDescriptors,\n} from \"@a5c-ai/atlas/catalog\";\n```\n\n## Build And Test\n\nThe catalog surface is validated as part of atlas and the downstream contract\nmatrix:\n\n```bash\nnpm run build --workspace=@a5c-ai/atlas\nnpm run test:atlas-catalog-contracts\n```\n\nThe final migration state keeps catalog source, tests, generated discovery\nsnapshot, package exports, docs, and CI metadata under atlas.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs",
      "to": "page:docs-atlas-catalog-unification",
      "kind": "contains_page"
    }
  ]
}