iiRecord
Agentic AI Atlas · Repo Map
page:docs-agent-reference-repo-mapa5c.ai
II.
Page JSON

page:docs-agent-reference-repo-map

Structured · live

Repo Map json

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

File · wiki/docs/agent-reference/repo-map.mdCluster · wiki
Record JSON
{
  "id": "page:docs-agent-reference-repo-map",
  "_kind": "Page",
  "_file": "wiki/docs/agent-reference/repo-map.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/agent-reference/repo-map.md",
    "sourceKind": "repo-docs",
    "title": "Repo Map",
    "displayName": "Repo Map",
    "slug": "docs/agent-reference/repo-map",
    "articlePath": "wiki/docs/agent-reference/repo-map.md",
    "article": "\n# Repo Map\n\nThis is the short orientation guide for the Babysitter monorepo.\n\n## High-Value Commands\n\nSource of truth: [`package.json`](../../package.json).\n\n```bash\nnpm run build:sdk\nnpm run test:sdk\nnpm run verify:metadata\nnpm run build:hooks-adapter\nnpm run test:hooks-adapter\nnpm run lint:hooks-adapter\n```\n\n## Core Packages\n\n| Path | Package | Role |\n| --- | --- | --- |\n| `packages/babysitter-sdk` | `@a5c-ai/babysitter-sdk` | Core runtime, storage, tasks, CLI, hooks, profiles, plugins, compression |\n| `packages/babysitter` | `@a5c-ai/babysitter` | Metapackage and `babysitter` binary |\n| `packages/genty/platform` | `@a5c-ai/genty-platform` | Platform API for harness integration, governance, interaction, and storage |\n| `packages/genty` | `@a5c-ai/genty` | Unified product package and owner of the `genty` CLI implementation |\n| `packages/genty/tui-plugins` | `@a5c-ai/genty-tui-plugins` | TUI panels for status, cost, and governance |\n| `packages/atlas` | `@a5c-ai/atlas` | Atlas catalog graph SDK, CLI, and data |\n| `packages/atlas/webui` | `@a5c-ai/atlas-webui` | Atlas graph explorer (Next.js) |\n| `packages/adapters/hooks/*` | `hooks-adapter workspace packages` | Hook normalization, CLI, and harness adapters |\n| `packages/adapters/policy` | `@a5c-ai/policy-adapter` | Proof-based policy enforcement trust core: unified signed envelopes, trusted-store key resolution, config-integrity manifest, policy schema + evaluator, `CommandAuthorization` issuance, argv matcher, and the tool-layer enforcement gates |\n\n## Policy Enforcement (proof-based)\n\nThe cryptographic policy-enforcement layer (Milestones A–E) lets a command run only when a\ndeclarative policy's required trust chain of signed evidence is satisfied. Enforcement is\ntoggled off-workspace by the pinned `POLICY_CONFIG_ROOT_FP` anchor; unpinned = back-compat\npass-through, pinned = active + fail-closed.\n\n- Overview + config + schema + gates + runbook: [`docs/policy-enforcement.md`](../policy-enforcement.md)\n- Authoritative design spec: [`docs/design/proof-based-policy-enforcement.md`](../design/proof-based-policy-enforcement.md)\n- Package: [`packages/adapters/policy`](../../packages/adapters/policy) (`@a5c-ai/policy-adapter`), worked example configs under [`packages/adapters/policy/examples`](../../packages/adapters/policy/examples).\n- Trust primitives: [`packages/genty/core/src/trust`](../../packages/genty/core/src/trust) (`SignedEnvelope`, model-decision + in-process attestation, chain, signing).\n- Enforcement surfaces: GATE 1 [`packages/adapters/tools/src/policy-verifier-wiring.ts`](../../packages/adapters/tools/src/policy-verifier-wiring.ts); genty session/MCP gates [`packages/genty/platform/src/harness/internal/createRun/orchestration/policy-enforcement-wiring.ts`](../../packages/genty/platform/src/harness/internal/createRun/orchestration/policy-enforcement-wiring.ts); GATE 3 credential backstop [`packages/adapters/core/src/policy-spawn-gate.ts`](../../packages/adapters/core/src/policy-spawn-gate.ts) + [`spawn-invocation.ts`](../../packages/adapters/core/src/spawn-invocation.ts); proxy attestation [`packages/adapters/transport/src/attestation.ts`](../../packages/adapters/transport/src/attestation.ts); SDK signed-breakpoint gate [`packages/babysitter-sdk/src/breakpoints/`](../../packages/babysitter-sdk/src/breakpoints).\n\n## Key Entry Points\n\n- SDK CLI: [`packages/babysitter-sdk/src/cli/main.ts`](../../packages/babysitter-sdk/src/cli/main.ts)\n- SDK command registry: [`packages/babysitter-sdk/src/cli/main/program.ts`](../../packages/babysitter-sdk/src/cli/main/program.ts)\n- SDK config and runs resolution: [`packages/babysitter-sdk/src/config/`](../../packages/babysitter-sdk/src/config)\n- genty product CLI: [`packages/genty/src/cli/main.ts`](../../packages/genty/src/cli/main.ts)\n- Metapackage shim: `packages/babysitter/bin/babysitter.js`\n- Atlas graph explorer: [`packages/atlas/webui/app/page.tsx`](../../packages/atlas/webui/app/page.tsx)\n\n## Repo Conventions\n\n- Import workspace packages by package name, never cross-package relative paths.\n- Keep event-sourced state transitions inside the SDK runtime and storage layers.\n- Prefer co-located tests in `__tests__/` with `*.test.ts`.\n- Unused variables should use `_` prefixes where needed for ESLint.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-agent-reference",
      "to": "page:docs-agent-reference-repo-map",
      "kind": "contains_page"
    }
  ]
}