Week 6 self-check answer guidance

Use these explanations after your first attempt. Keep every disposition tied to evidence another reader could reproduce.

Q1

A useful first note names the location, input or path, expected result, observed or traced result, and consequence. If a field is unavailable, record that boundary rather than filling it with an assumption.

Q2

Use active=False, owner=True, staff=False. Because and binds more tightly than or, the second expression returns True; the contract requires False for every inactive account. A case with an active owner or staff member does not separate the expressions.

Q3

The claim is refuted as a conclusion about the guard. An active-staff example exercises only one path. The inactive-owner input is missing and reproduces the defect, so the example cannot establish the contract.

Q4

The claim is refuted. The stated inputs are booleans, and parsing a string adds behavior outside the contract. Cite that clause and keep the review focused on the requested change.

Q5

Mark a finding confirmed after reproducing the behavior or tracing the exact path against the requirement. Mark it refuted with a counterexample or a contract clause that contradicts it. A plausible explanation without either kind of evidence remains unresolved.

Q6

Mark it cannot tell. List the diff, tests, callers, or other files inspected, identify the missing caller or documented requirement, and request the smallest safe check that would decide whether the status is relied upon.

Q7

No finding supports only the claim that nothing was reported in the supplied context. It does not establish that the change is correct, that omitted requirements are satisfied, or that unseen callers are safe. Perform your own boundary checks and record any omission.

Q8

The person with merge authority owns acceptance. That person should see the requirement, the candidate and base revisions, the independent review, each disposition with evidence, the verification commands and any unresolved question before deciding to accept, narrow, recheck or stop.

Q9

Inspect the command's paths, inputs, credential and network use, and expected outputs before running it. Stop when its scope is unclear, it requests secrets or network access, or it would alter files outside the dedicated change directory; retain the refusal as evidence.

Q10

For example: “Source: the issue's target-file requirement. Location: every path in the candidate diff. Check: each path is the named target file; any other path is a failure.” The source, location or input, and expected result make the rule reproducible.

Spaced retrieval and transfer

Retrieval 1. Review the changed requirement, tests and implementation together; the model's comment is a hypothesis until those three sources and a check support it.

Retrieval 2. A product decision and acceptance cases are required before mapping an unknown result to a failure.

Transfer. “No finding” means only that the reviewer reported none for the context it received. Add an omitted requirement as your own finding, identify its input or source, and run the smallest check that decides whether the change is acceptable.