← knowledge.oriz.in

Tag tasks AFK vs HITL; humans stay in loop for alignment, agents run AFK for implementation

rule rulesagenttasksplanningworkflow

AFK vs HITL tasks

Two modes. Tag every task. Wrong mode = wasted turn.

Modes

Mode Meaning Required for
HITL human-in-the-loop Alignment, PRD-shaping, MCQ answers, QA, code review, ambiguous scope
AFK away-from-keyboard Well-specified implementation with working feedback loops

Phase → mode

Phase Mode Why
Idea → aligned understanding HITL Only humans know taste
PRD writing HITL Trade-off decisions
Task splitting (vertical slices) HITL-lite Human reviews split; agent proposes
Implementation of one slice AFK Feedback loops carry load
QA / functional review HITL Multimodal (eyes, feel, taste)
Code review pass AFK-then-HITL Agent flags, human decides

TaskCreate convention

TaskCreate(..., metadata: { mode: "afk" | "hitl" })

Missing mode = treat as HITL by default. Fail loud, not silent.

AFK task requirements (all must hold)

HITL task requirements

Anti-patterns

Source

Matt Pocock workshop 2026-07-03 — "day shift and night shift" framing. HITL = day shift (human present); AFK = night shift (agent solo).

Cross-refs