Implementation: ENABLED (needs-you queue, manual gates, human close) · Exposure: INTERNAL · PUBLIC PREVIEW (contract). See status labels. People are part of the system, not an afterthought. A run brings in a person at defined points, and every answer is evidence.

​
Architecture contract

A person enters a run when: Rules:
  • A person’s answer is written as a receipt before it takes effect.
  • A person may close a node as the override when evidence is incomplete. That close is receipted with their identity.
  • A person can raise a budget. A model never can.
  • Pause, resume and cancel are human controls that act at the next safe boundary.
  • A hard policy deny is not something a person can approve past.
Why: autonomy is only useful if the points where a person decides are explicit and cheap to answer. Typed requests and receipted answers make those points visible and auditable.

​
Current implementation

On main, in the work runtime:
  • The needs-you list collects nodes held on a manual wait gate and open attention requests.
  • A manual gate is resolved by a person, with their identity recorded.
  • For agency-origin work, a judge timeout, error or invalid answer moves the node to NEEDS_HUMAN, never to done, and a human close is the override when evidence is missing.
  • The drive runner parks any node it cannot or must not advance behind a manual gate instead of retrying.

​
Availability

​
Developer relevance

If your integration answers attention requests, keep the receipt_id returned with each answer. It is the evidence that you approved or supplied that input.