VIII · Safety & ControlEmerging★

Two Human Touchpoints

also known as Curation + Final-Review HITL, Selection-and-Publish Touchpoints

Place exactly two human-in-the-loop checkpoints in agentic pipelines: one at content selection and one at final review before publication.

This pattern helps complete certain larger patterns —

  • specialisesHuman-in-the-Loop★★— Require explicit human approval at defined points before the agent performs an action.

Context

A team automates a content or decision pipeline (newsletter, report, recommendation). The temptation is fully-autonomous: agent does everything end-to-end. Result: technically-accurate, on-policy outputs that lack strategic narrative and feel hollow to readers / users — Bornet's 'somehow soulless' observation.

Problem

Zero-touchpoint pipelines produce outputs missing the human judgment that defines what matters. Adding too many touchpoints destroys the productivity gain (validation burden). The team needs the minimum-and-correct number of human checkpoints.

Forces

  • Each touchpoint adds latency and human-hour cost.
  • Too few and the output is soulless; too many and the automation is pointless.
  • Touchpoint placement matters as much as count — wrong placement adds cost without quality.

Example

The authors' newsletter pipeline. Zero-touchpoint attempt: fully-automated newsletter is technically accurate but readers' open rates fall and feedback says it feels 'corporate'. With Two Human Touchpoints: agents produce daily summary candidates → human editor selects which to include (Touchpoint 1) → agents compile and format → human editor reviews the assembled newsletter before publication (Touchpoint 2). Open rates recover; productivity gain preserved.

Diagram

Solution

Therefore:

Insert two human-in-the-loop checkpoints. Touchpoint 1 — Selection: after the agent has produced candidate outputs, a human reviews and selects which ones matter (this captures human judgment about value, relevance, audience fit). Touchpoint 2 — Final Review: before publication or irreversible commit, a human reviews the assembled output for context, accuracy, editorial standards. All other steps are autonomous. Pair with human-in-the-loop, approval-queue, sync-execution-plan-confirmation, three-tier-autonomy-portfolio.

What this pattern forbids. Exactly two human touchpoints — at Selection and at Final Review — for content / decision pipelines; pipelines may not collapse to zero touchpoints or expand to per-step approval.

And the patterns that stand alongside it, or against it —

  • complementsApproval Queue★★— Queue agent-proposed actions for asynchronous human review while the agent continues other work.
  • complementsSynchronous Execution-Plan Confirmation★— Agent synchronously emits its full execution plan for user confirmation before any side-effect step, and provides asynchronous operation recordings for post-hoc review.
  • complementsOne Tool, One Agent★— Design agent systems as a team of narrow single-purpose agents, each owning one tool or one capability, rather than a single super-agent that handles every tool — the agent analogue of microservices over monolith.
  • complementsCost-Aware Action Delegation★— Classify every agent action by risk/cost and route each tier to a different approval policy, bounding the autonomy surface per-action instead of by one global flag.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

References

Provenance