iiRecord
Agentic AI Atlas · Standard Process Library Implementation
page:docs-reference-standard-process-library-2026-01-20a5c.ai
II.
Page JSON

page:docs-reference-standard-process-library-2026-01-20

Structured · live

Standard Process Library Implementation json

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

File · wiki/docs/reference/standard-process-library-2026-01-20.mdCluster · wiki
Record JSON
{
  "id": "page:docs-reference-standard-process-library-2026-01-20",
  "_kind": "Page",
  "_file": "wiki/docs/reference/standard-process-library-2026-01-20.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/reference/STANDARD_PROCESS_LIBRARY_2026-01-20.md",
    "sourceKind": "repo-docs",
    "title": "Standard Process Library Implementation",
    "displayName": "Standard Process Library Implementation",
    "slug": "docs/reference/standard-process-library-2026-01-20",
    "articlePath": "wiki/docs/reference/STANDARD_PROCESS_LIBRARY_2026-01-20.md",
    "article": "\n# Standard Process Library Implementation\n\n**Date:** 2026-01-20\n**Task:** Todo #6 - Create the standard library of processes\n**Status:** Historical implementation note, updated for the current library layout\n\n---\n\n## Summary\n\nThis document originally described an early standard-library foundation in a project-local `.a5c/processes/` layout. The current built-in standard library for this repository lives under `library/`.\n\nProject-local `.a5c/processes/` directories still matter, but only as copied or customized workspace assets. Public documentation should treat `library/` as the canonical source of built-in processes.\n\n---\n\n## Current Library Layout\n\nThe current library is organized under `library/`, including:\n\n- `library/methodologies/`\n- `library/specializations/`\n- `library/processes/shared/`\n- `library/examples/`\n- `library/assets/`\n- `library/reference/`\n- `library/README.md`\n\nRepresentative entry points that exist in the repo today:\n\n- `library/tdd-quality-convergence.js`\n- `library/methodologies/plan-and-execute.js`\n- `library/methodologies/ralph.js`\n- `library/methodologies/devin.js`\n\nFor current user-facing counts and category breakdowns, see `docs/user-guide/features/process-library.md`.\n\n---\n\n## Relationship to `.a5c/processes/`\n\nUse the following distinction in public docs:\n\n- `library/` is the built-in library shipped with the Babysitter repository and the active process-library binding.\n- `.a5c/processes/` is a project-local location for copied, generated, or customized process assets.\n\nThat means a process may exist in both places:\n\n1. As the built-in source in `library/`\n2. As a project-local override in `.a5c/processes/`\n\nWhen docs show a built-in example, they should point at `library/` unless the point of the example is specifically about local overrides.\n\n---\n\n## Current Usage Examples\n\n### Built-in Process\n\n```bash\nbabysitter run:create \\\n  --process-id methodologies/plan-and-execute \\\n  --entry library/methodologies/plan-and-execute.js#process\n```\n\n### Built-in Methodology Loop\n\n```bash\nbabysitter run:create \\\n  --process-id methodologies/ralph \\\n  --entry library/methodologies/ralph.js#process\n```\n\n### Built-in Advanced Example\n\n```bash\nbabysitter run:create \\\n  --process-id tdd-quality-convergence \\\n  --entry library/tdd-quality-convergence.js#process \\\n  --inputs library/examples/tdd-quality-convergence-example.json\n```\n\n### Project-Local Override\n\nIf a team copies one of those processes into `.a5c/processes/`, it can run the local copy explicitly by changing the `--entry` path to the project-local file.\n\n---\n\n## Related Current Docs\n\nUse these docs for the current public explanation of the process library:\n\n- `docs/user-guide/features/process-library.md`\n- `docs/user-guide/features/process-definitions.md`\n- `docs/user-guide/01-discovery-analysis.md`\n- `docs/reference/PROCESS_SELECTION.md`\n\n---\n\n## Historical Note\n\nThe January 2026 report captured an intermediate implementation stage. The process-library packaging and discovery model has since converged on the built-in `library/` layout plus project-local `.a5c/` copies. References to `.a5c/processes/` in older implementation notes should therefore be interpreted as local override examples, not as the repository’s canonical built-in library path.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-reference",
      "to": "page:docs-reference-standard-process-library-2026-01-20",
      "kind": "contains_page"
    }
  ]
}