iiRecord
Agentic AI Atlas · Process Authoring Policy
page:docs-agent-reference-process-authoringa5c.ai
II.
Page JSON

page:docs-agent-reference-process-authoring

Structured · live

Process Authoring Policy json

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

File · wiki/docs/agent-reference/process-authoring.mdCluster · wiki
Record JSON
{
  "id": "page:docs-agent-reference-process-authoring",
  "_kind": "Page",
  "_file": "wiki/docs/agent-reference/process-authoring.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/agent-reference/process-authoring.md",
    "sourceKind": "repo-docs",
    "title": "Process Authoring Policy",
    "displayName": "Process Authoring Policy",
    "slug": "docs/agent-reference/process-authoring",
    "articlePath": "wiki/docs/agent-reference/process-authoring.md",
    "article": "\n# Process Authoring Policy\n\nThese rules are specific to this repository and override more generic process-authoring guidance when they conflict.\n\n## Default Stance\n\n- Always use the Babysitter skill to fulfill user requests in this repo, but not agent-to-agent delegated requests.\n- Keep the orchestration model intact. Do not replace it with helper scripts or ad hoc wrappers.\n- Keep process code aligned with the process-library style and repo conventions.\n\n## `babysitter:call` Override For This Repo\n\nWhen authoring a Babysitter process for a direct user request in this repository:\n\n- Do not generate `kind: 'shell'` subtasks unless the user explicitly asks for a shell-oriented workflow.\n- Prefer `agent` and `skill` tasks for implementation, review, synthesis, and verification steps.\n- Keep breakpoints sparse. Use them only when user input is genuinely critical or the situation is ambiguous.\n- Still include an interview phase up front when requirements or constraints are unclear.\n\nThis is a deliberate repo-specific override of more general guidance that may recommend shell tasks for objective verification.\n\n## Stability Rules\n\n- Do not use the babysit skill inside delegated subtasks.\n- Do not rely on auto-hooks to continue a run in environments where hooks are unavailable; drive the loop explicitly when required.\n- Keep completion criteria explicit and tied to run status, not to optimistic summaries.\n\n## Where To Look Next\n\n- [Runtime And Layout](./runtime-and-layout.md) for replay and run-state behavior\n- [Command Surfaces](./command-surfaces.md) for CLI boundaries\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": []
}