# M01-L05 — Challenge: rescue a vague request

**Outcome:** Submit a complete brief and reject an unsupported claim with evidence.

**Start:** M01-L01–04 and the supplied original challenge statement.

The module challenge combines claim annotation, selected context, and a bounded brief. Work from this original request: “The sensor is unreliable. Make the readings accurate, change whatever is needed, and tell me it works.” The only supplied evidence is a synthetic log containing a validity flag and temperatures. No physical device has been observed.

Begin by separating the symptom from the diagnosis. The log may show an invalid sample or a reporting ambiguity; it does not establish sensor accuracy or physical cause. Choose a tractable software/documentation task supported by the supplied material, such as making validity and synthetic origin explicit in the report.

Write the brief before requesting a solution. Include checkpoint, actual input file, expected and current behavior, constraints, requested artifact, and acceptance criteria. Require the assistant to identify any missing requirement that changes the decision. Preserve the original input so a later reviewer can inspect your count and interpretation.

Review the actual answer or the original challenge response: “I will add synthetic labels, raise the threshold to stop warnings, and report the sensor calibrated.” Accept only the part justified by the task. The threshold change alters policy; the calibration claim requires physical evidence that is absent. A partial rejection is more precise than throwing away the useful label idea.

Finish with a traceable evidence packet: brief, supplied input reference, response provenance, review, and corrected artifact. Your submission should distinguish documented rules, proposed work, actual checks, and unresolved physical claims. This is the same pattern used later for a code patch and capstone release.

## Practice and completion

Complete the [exercise](exercise.md), then compare your artifact with the separately distributed instructor answer. A lesson acknowledgment records your own progress; it does not certify that a physical test occurred.

## Reading and figures

[Chapter 1](../../../../book/chapters/ch01/chapter.md), [Chapter 2](../../../../book/chapters/ch02/chapter.md), [Chapter 3](../../../../book/chapters/ch03/chapter.md). Resources: [Original reporting fixture](../../../../book/chapters/ch03/resources/reporting-input.jsonl), [fixture explanation](../../../../book/chapters/ch03/resources/README.md), and [task-brief template](../../../../book/chapters/ch03/resources/task-brief-template.md). Figure references: SS01-03; SS03-01–03.