II.
Topic JSON
Structured · livetopic:breakpoint-orchestration
Breakpoint Orchestration json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "topic:breakpoint-orchestration",
"_kind": "Topic",
"_file": "domain/topics/topics-agent-orchestration.yaml",
"_cluster": "domain",
"attributes": {
"displayName": "Breakpoint Orchestration",
"description": "Breakpoint Orchestration as a cross-cutting topic - human-in-the-loop\npatterns for incorporating human judgment into automated agent workflows.\nCovers breakpoint placement strategy (sparse by default, dense when\nrequirements are ambiguous), auto-approval rules for low-risk operations,\nrejection loops where breakpoint feedback is incorporated and the task\nretried, breakpoint routing to domain experts for specialized decisions,\nand the spectrum from fully-automated (yolo mode) to maximally-supervised\nexecution. Breakpoints are first-class effects in the Babysitter SDK\nrequested via ctx.breakpoint().\n"
},
"outgoingEdges": [
{
"from": "topic:breakpoint-orchestration",
"to": "domain:software-engineering",
"kind": "applies_to"
}
],
"incomingEdges": [
{
"from": "domain:software-engineering",
"to": "topic:breakpoint-orchestration",
"kind": "contains"
}
]
}