Answers and explanations · Route work into human review

Module 5 Pack A route key

Assume P1/F1 are active, the ledger starts empty, events are processed in order and the drafts pass validation unless an explicit failure card is added.

E001 / R101 revision 1: DRAFT_READY, within_standard_policy. Projector 2 is at the maximum. Review remains PENDING. E002 / R102 revision 1: HUMAN_REVIEW, above_standard_limit. Webcam 6 exceeds 5. E003 / R103 revision 1: HUMAN_REVIEW, guest_request. Do not approve based on the valid duration alone. E004 / R104 revision 1: NEEDS_INFO, missing_duration. Ask one duration question. E005 / R105 revision 1: HUMAN_REVIEW, instruction_bypass. No other records are disclosed. E006 / R101 revision 1: DUPLICATE_SKIPPED. Return/reference the existing queue item; no new intended queue effect. E007 / R106 revision 1: INVALID_INPUT, invalid_duration. Zero violates the positive whole-number contract. E008 / R107 revision 1: HUMAN_REVIEW, unsupported_item. A laptop is not listed in policy. E009 / R108 revision 1: HUMAN_REVIEW, extension_request. A within-limit extension is still an exception. E010 / R109 revision 1: DRAFT_READY without an injected failure. With F-B, place the operation on technical hold and reconcile to Q109 before declaring the queue write recorded. E011 / R104 revision 2: DRAFT_READY. Speaker 2 is within 3; preserve the link to revision 1. E012 / R110 revision 1: DRAFT_READY. Webcam 5 is at October's maximum.

The simplified lab filters are final_route equals DRAFT_READY; final_route equals NEEDS_INFO; fallback for all unmatched values. The base lab fallback displays a visible hold result with its original route/reason, so HUMAN_REVIEW and INVALID_INPUT remain distinguishable. Do not quietly discard the fallback. An audit-log entry is distinct from a new review-queue item: DUPLICATE_SKIPPED only references the existing queue item, and TECHNICAL_HOLD pauses the existing operation without another queue write. A fuller design can have separate exact-match branches for each allowed disposition and an invalid-status hold.

A valid R102 review record includes its identity, draft version, configuration and source versions, above-limit reason, source clause, original input reference, PENDING review state and unfilled human-review fields. I5 illustrates the right policy conclusion, but the full record needs all fields.

F-D: status APPROVED is not in the assistant contract and source_ref is missing. Block the draft, optionally request one controlled repair, revalidate and route continued failure to HUMAN_REVIEW with invalid_output. Do not treat a repair as a policy override. F-E: an edit creates a new draft version and resets its review state to PENDING. Retain the old review for the old version as history. It cannot authorise the new content.

M5 Q1: a router may process multiple matching routes. Order does not ensure exclusivity. Add all necessary conditions or branch on a single validated route value. M5 Q2: DRAFT_READY is a workflow classification; APPROVED_FOR_NEXT_STEP is a verified human decision tied to exact content and action. Neither means a loan has been booked by this course. M5 Q3: reset the changed version to pending, retain history and obtain review of the new content.