Human In The Loop

The primitive that treats humans as durable network participants — attention surfaces, queues, decision records, routing semantics — not as ad-hoc chat receivers.

Autonomy is not the absence of humans; it is knowing when human judgment is needed and making that handoff crisp.

Use this when

• A slice closeout needs classifying: auto-continue, human gate, or park
• A real decision needs to land in front of a human (usage limits, provider auth, roadmap tradeoff, product-intent ambiguity)
• Designing a human queue/dashboard surface
• Returning a hot potato to orchestration after human approval

Don't use this when