II.
Page JSON
Structured · livepage:docs-assimilation-harness
Harness Integration json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "page:docs-assimilation-harness",
"_kind": "Page",
"_file": "wiki/docs/assimilation/harness.md",
"_cluster": "wiki",
"attributes": {
"nodeKind": "Page",
"sourcePath": "docs/assimilation/harness/index.md",
"sourceKind": "repo-docs",
"title": "Harness Integration",
"displayName": "Harness Integration",
"slug": "docs/assimilation/harness",
"articlePath": "wiki/docs/assimilation/harness/index.md",
"article": "\n# Harness Integration\n\nThis section explains how to connect a real harness to Babysitter and what each integration guide is responsible for.\n\n## Audience\n\n- Harness maintainers and adapter authors\n- Teams wiring Babysitter into CI or hosted execution flows\n- Operators validating that session binding, task execution, and approvals work the same way across harnesses\n\n## Start Here\n\n1. [Generic Harness Guide](./generic-harness-guide.md) for the shared integration contract\n2. [Claude Code Integration](./claude-code-integration.md) for the current first-class harness example\n\n## Related Entry Points\n\n- Need the higher-level map? Start at [Harness Assimilation](../index.md).\n- Need GitHub-hosted orchestration? Use the top-level GitHub Actions setup guides in the sidebar.\n- Need plugin packaging rather than harness integration? Go to [Plugins](../../plugins.md).\n",
"documents": []
},
"outgoingEdges": [
{
"from": "page:docs-assimilation-harness",
"to": "page:docs-assimilation-harness-accomplish-integration",
"kind": "contains_page"
},
{
"from": "page:docs-assimilation-harness",
"to": "page:docs-assimilation-harness-claude-code-integration",
"kind": "contains_page"
},
{
"from": "page:docs-assimilation-harness",
"to": "page:docs-assimilation-harness-generic-harness-guide",
"kind": "contains_page"
}
],
"incomingEdges": [
{
"from": "page:docs-assimilation",
"to": "page:docs-assimilation-harness",
"kind": "contains_page"
}
]
}