Skip to content

Check: Evidence transfer

Knowledge check · self-test

Check: Evidence transfer

Use the checks below to decide which evidence supports each claim.

Back to the chapter →

Use the checks below to decide which evidence supports each claim.

## Try It Now {.depth-l0 data-narration="suspended-until-rerecord"} Rewrite this weak simulation result into a scoped evidence statement: > "The Wokwi project works, so the hardware design is ready." Name the code behavior, model, inputs and logs. State what the model leaves out and which bench tests must still pass.## Separate Virtual/Physical Claims {.depth-l0 data-narration="suspended-until-rerecord"} For each claim, decide whether simulation can support it, hardware must measure it, or both are needed: 1. The firmware enters a fault state when the virtual sensor is missing. 2. The I2C bus has enough timing margin with the selected pullup resistors. 3. The sleep path disables the display before the node enters low-power mode. For each answer, name the proof. It might be a log, a trace, a current test or a bench note.## Match Simulation Artifact to Claim {.depth-l0 data-narration="suspended-until-rerecord"} Match each claim to the record that can support it. Consider whether the claim concerns code in a model or a physical effect. ## Order Hardware Simulation Flow {.depth-l0 data-narration="suspended-until-rerecord"} Put the hand-off steps in order, from the model run through bench evidence and review. ## Label Simulation Evidence Loop {.depth-l0 data-narration="suspended-until-rerecord"} The labels distinguish a model result from the bench evidence needed to support a physical claim. ## Concept Check: Physical Signal Claims {.depth-l0 data-narration="suspended-until-rerecord"} A virtual transaction sequence does not measure real signal timing. Use the check to identify the needed bench evidence.

Back to Virtual Hardware: Evidence Transfer: Incremental Examples and Sensor Node Review