iiRecord
Agentic AI Atlas · Workspace Validation Map
page:docs-workspace-validationa5c.ai
II.
Page JSON

page:docs-workspace-validation

Structured · live

Workspace Validation Map json

Inspect the normalized record payload exactly as the atlas UI reads it.

File · wiki/docs/workspace-validation.mdCluster · wiki
Record JSON
{
  "id": "page:docs-workspace-validation",
  "_kind": "Page",
  "_file": "wiki/docs/workspace-validation.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/workspace-validation.md",
    "sourceKind": "repo-docs",
    "title": "Workspace Validation Map",
    "displayName": "Workspace Validation Map",
    "slug": "docs/workspace-validation",
    "articlePath": "wiki/docs/workspace-validation.md",
    "article": "\n# Workspace Validation Map\n\nThis document is the repo-level source of truth for which npm workspaces are active, which ones are release-critical, and which workflow path validates them.\n\n<!-- docs-discovery-note:start -->\nFor canonical documentation homes and public/internal positioning, use [Package and Plugin Docs Map](./package-and-plugin-map.md).\nThis file remains the validation-contract ledger, not the primary package/plugin discovery index.\n<!-- docs-discovery-note:end -->\n\nIf a workspace stays active, it must meet one of these conditions:\n\n- it is validated in `.github/workflows/ci.yml`\n- it is validated in the release/staging workflows because that is the only meaningful contract surface\n- it is explicitly called out here as intentionally excluded\n\n## Release-critical workspace families\n\nThese workspaces ship public packages or release-facing operational behavior. They are expected to stay aligned with both CI and release workflows.\n\n| Workspace or family | Role | Validation path |\n| --- | --- | --- |\n| `packages/sdk` (`@a5c-ai/babysitter-sdk`) | Core SDK and CLI runtime | `.github/workflows/ci.yml` jobs `test` and `packages-sdk`, plus `release.yml` and `staging-publish.yml` |\n| `packages/breakpoints-mux` | Published breakpoint runtime | `.github/workflows/ci.yml` job `test`, plus `release.yml` and `staging-publish.yml` |\n| `packages/agent-plugins-mux` | Published plugin compiler/runtime package | `.github/workflows/ci.yml` job `test`, plus `release.yml` and `staging-publish.yml` |\n| `packages/observer-dashboard` | Published observer dashboard package | `.github/workflows/ci.yml` job `observer-dashboard`, plus `release.yml` and `staging-publish.yml` |\n| `packages/hooks-mux/*` | Published hooks-mux packages | `.github/workflows/ci.yml` job `test`, plus `release.yml` and `staging-publish.yml` |\n| `packages/agent-mux/*` | Published agent-mux packages | `.github/workflows/ci.yml` job `test`, plus `release.yml` and `staging-publish.yml` |\n| `packages/transport-mux` | Published transport/proxy runtime package used by the agent-mux CLI/runtime chain | `.github/workflows/ci.yml` job `workspace-coverage` (`build` + `lint` + `typecheck` + `test` + `scorecard:migration`), plus `release.yml` and `staging-publish.yml` |\n| `packages/babysitter`, `plugins/babysitter-unified`, and generated/published harness plugin packages | Published metapackage, canonical plugin source, and harness plugin packages | `.github/workflows/ci.yml` job `test`, plus `release.yml` and `staging-publish.yml` |\n\n## Public advanced/runtime packages\n\nThese packages are publicly installable, but their canonical docs live primarily in package READMEs and the package/plugin docs map rather than the end-user getting-started flow.\n\n| Workspace | Role | Validation path |\n| --- | --- | --- |\n| `packages/babysitter-agent` | Public runtime CLI for headless/orchestrated/operator workflows; not the default first-stop end-user entrypoint | `.github/workflows/ci.yml` job `test`, plus `release.yml` and `staging-publish.yml` runtime build/test validation |\n| `packages/agent-core` | Public advanced/runtime dependency package consumed by `@a5c-ai/babysitter-agent` and runtime orchestration flows | `.github/workflows/ci.yml` job `test`, plus `release.yml` and `staging-publish.yml` |\n| `packages/agent-catalog` | Public graph/evidence catalog package consumed by SDK, agent-mux, hooks-mux, plugin compiler, and catalog-adjacent tooling | `.github/workflows/ci.yml` job `workspace-coverage` (`npm run ci:test --workspace=@a5c-ai/agent-catalog`), plus `release.yml` and `staging-publish.yml` |\n\n## Internal-only active workspaces\n\nThese workspaces are part of the active monorepo and ship code or operational behavior inside the repo, but they are not current public publish targets.\n\n| Workspace | Role | Validation path |\n| --- | --- | --- |\n| `packages/babysitter-tui-plugins` | Internal TUI plugin package for babysitter observability | `.github/workflows/ci.yml` job `workspace-coverage` |\n\n## Explicit exclusions\n\nThere are currently no active npm workspaces that are intentionally excluded from validation. `packages/transport-mux` now participates in the workspace-coverage job through its package-local `lint`, `typecheck`, and `test` commands alongside `build` and `scorecard:migration`.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs",
      "to": "page:docs-workspace-validation",
      "kind": "contains_page"
    }
  ]
}