M08 SELF-CHECK

Capstone and continued maintenance

Five questions · 4/5 to pass · unlimited retry

1. Why can 27.5 degrees be NORMAL or ALERT with a 28-degree threshold and 1-degree hysteresis? The result is random. The threshold was necessarily stored in nonvolatile memory. Inside the band, the previous non-fault state determines retention.

2. What belongs in a comparison of total effort to deliver a verified change? Preparation, editing or generation, review/repair, verification, and separately visible waiting. Generation time alone. The number of lines or tokens produced, without checking correctness.

3. The previous threshold is 30. A complete line contains threshold 28junk. What must the reference parser do? Accept 28 because its prefix is numeric. Reject the malformed line and preserve 30. Reset to the default because every parser error restarts the monitor.

4. A capstone earns 88 points but has no fresh-checkout firmware build. Can it receive the suggested core pass? Yes, because the score exceeds 80. Yes, if it was uploaded publicly. No; the mandatory reproducible-build gate still needs actual evidence.

5. A valid synthetic replay exits 0 and includes a FAULT/nonfinite record with temperature null. Which release note matches that evidence? The synthetic input exercised nonfinite handling successfully; physical sensor behavior remains unverified. The physical sensor failed and must be replaced. The process crashed despite exit 0.

Your result

Not attempted

Read the correct answers and explanations

Question 1

Inside the band, the previous non-fault state determines retention.

NORMAL enters at 28 and ALERT clears at 27. Between them, history matters. Following FAULT recovery, the fresh entry threshold determines the new state.

Question 2

Preparation, editing or generation, review/repair, verification, and separately visible waiting.

A usable result requires review and verification. Leaving that effort out can reverse a comparison; unmeasured timings must remain unmeasured.

Question 3

Reject the malformed line and preserve 30.

The complete token must match the promised decimal grammar. Invalid commands leave the prior setting intact; a numeric-prefix conversion is insufficient.

Question 4

No; the mandatory reproducible-build gate still needs actual evidence.

The score and mandatory gates are separate. A private candidate can pass, but a high score cannot substitute for required reproduction evidence.

Question 5

The synthetic input exercised nonfinite handling successfully; physical sensor behavior remains unverified.

FAULT is a specified policy state, not necessarily process failure. A valid fixture can intentionally trigger it. A host log is not physical evidence.