# Lesson 10 practice: State what is confirmed and what remains unknown

[中文](README.md)

Open [impact.csv](impact.csv). Write an initial update that helps a reader act, and identify what must be checked before the next update. This independent synthetic reconciliation list uses the public scenario’s 37 confirmed tasks, up to 60 potentially affected tasks, and two high-temperature cases. Row assignments, including **29 contacted tasks**, are new exercise assumptions. This is not a real incident register, and no real users have been contacted by the course.

## Fields

| Field | Meaning |
| --- | --- |
| `source_type` / `task_id` | Independent synthetic marker / task ID |
| `version_status` | `confirmed_wrong_version` or `unknown`; unknown does not mean unaffected |
| `equipment` | `current_model` or `old_model` |
| `high_temperature` | 1 when the simulation assigns a high-temperature case, otherwise 0 |
| `contacted` | 1 when the simulation records contact, otherwise 0 |
| `contact_status` | `acknowledged` or `not_contacted`; neither establishes resolved impact or approval to resume |
| `protection_status` | `withhold_steps_and_escalate`: withhold operating steps and escalate to qualified people; `pause_path_pending_reconciliation`: pause the relevant path pending checks |

Convert the two numeric boolean fields before calculations; the string `'0'` can be truthy. Protection statuses are exercise records or proposed handling, not receipts from real actions. Acknowledgment does not establish that someone read every instruction or that on-site risk has ended.

## Reconcile and write

1. Count **60 tasks in scope for investigation: 37 confirmed version mismatches and 23 unknown**. Do not report 60 confirmed impacts or remove unknown tasks from the queue. The 61.7% from 37 / 60 describes this investigation list, not an incident rate across all business tasks.
2. Within the 37 confirmed tasks, check **two high-temperature cases, 29 contacted, and eight not yet contacted**. The 78.4% from 29 / 37 is contact coverage among confirmed tasks, not a resolution rate. Unknown tasks still need investigation and contact where appropriate.
3. Draft an initial statement: “We have confirmed 37 version mismatches; 23 further tasks remain under investigation. Two confirmed tasks involve high-temperature scenarios. The relevant recommendation path should remain restricted, and qualified personnel should follow established equipment procedures. Contact is recorded for 29 confirmed tasks; follow-up remains outstanding.” Identify these as exercise figures.
4. Add owners for reconciliation, communication, and professional handoff, the next update time, evidence sources, and what will be said if questions remain open. You may choose an illustrative update time, but mark it as proposed rather than approved.
5. Define recovery evidence separately: applicable versions, affected models, source withdrawal, stop and handoff behavior, and a normally permitted task. An apology, complete contact coverage, or a high aggregate pass rate does not replace recovery conditions.

## Check your reasoning

The table does not establish real harm, total affected people, post-contact outcomes, or a specific root cause. Keep Lesson 7’s old-session access problem separate from this version mismatch. Model and temperature fields do not authorize maintenance instructions.

Submit an initial update, unresolved scope, contact priorities, and recovery conditions. In self-study, mark real contacts, execution authority, and recovery evidence as awaiting validation. A peer can read only the update and explain what is known, unknown, and next, checking that it does not imply recovery is complete.

In the next lesson, include exception handling, review, and support in costs rather than hiding this work behind “incident resolved.”