human-checkpoint

You can implement a human-in-the-loop checkpoint by requiring explicit sign-off recorded in a DECISIONS.md file, which allows the pipeline to pause execution and resume only after human approval is documented.

Human-in-the-loop sign-off works by pausing the pipeline at a designated checkpoint and waiting for a human to provide explicit approval, which is then recorded as an auditable entry in DECISIONS.md before the pipeline resumes.

You record human sign-off by ticking the approval checkbox in the DECISIONS.md file, ensuring the pipeline checkpoint decision is explicitly documented and auditable for future review.

Yes, pipeline checkpoints can optionally use STATUS.md or UNITS.csv to identify the blocked stage, while DECISIONS.md is required to record the explicit human approval needed for pipeline resumption.

You need a human-in-the-loop checkpoint when a pipeline stage requires expert review, such as approving a research protocol or draft outline, ensuring critical decisions are explicitly signed off before the next automated stage begins.