iiRecord
Agentic AI Atlas · Babysitter task outputSchema guard
output-guard:babysitter-task-output-schemaa5c.ai
II.
OutputGuard JSON

output-guard:babysitter-task-output-schema

Structured · live

Babysitter task outputSchema guard json

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

File · security/output-guards/babysitter-task-output-schema.yamlCluster · security
Record JSON
{
  "id": "output-guard:babysitter-task-output-schema",
  "_kind": "OutputGuard",
  "_file": "security/output-guards/babysitter-task-output-schema.yaml",
  "_cluster": "security",
  "attributes": {
    "displayName": "Babysitter task outputSchema guard",
    "appliesTo": "tool-result",
    "phase": "post-call",
    "detectorKinds": [
      "format-violation"
    ],
    "onTrigger": "block",
    "severity": "block-call",
    "description": "Per-task structural guard. The babysitter SDK accepts an\n`outputSchema` on agent task definitions (see\npackages/sdk/src/tasks/types.ts:46 and\npackages/sdk/src/prompts/templates/task-kinds.md). At result-posting\ntime the SDK validates the task result against the per-task JSON\nschema and rejects shape-mismatched results, surfacing a structured\nerror on the journal as part of EFFECT_RESOLVED with status=error.\nDistinct from `output-guard:claude-code-aup-refusal` (post-call\nrefusal-rewrite over assistant text) — this guard is structural over\ntool/effect results, not safety/AUP over assistant content.\n"
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "agent-runtime-impl:a5c.runtime@current",
      "to": "output-guard:babysitter-task-output-schema",
      "kind": "output_guard_applied_by",
      "attributes": {}
    }
  ]
}