Skip to content
OBSERVE. QUESTION. VERIFY.
09CASE FILE
Getting ready

Your first case starts with a question.

Choose a small project you can inspect and one question whose answer you can verify. Prepare the repository path and your chosen model endpoint. The Windows link opens this site's configured download destination; that destination determines availability and installation requirements.

Open Windows download destination

Prepare the evidence

Check the repository state and preserve existing work. Locate a function, failing input, or unfamiliar module worth investigating. Review endpoint setup and credential storage for the software you actually use. The shared screenshots show a reference application and do not establish the features of a final branded installer.

Begin without edits

Ask the assistant to explain a small function using its implementation and callers. Require file references and a clear distinction between observation and inference. Compare the explanation with the code yourself. Only then define a change, its expected behavior, and the evidence you need before accepting it.

What should I verify after the first response?

Check that the cited files exist, the relevant branches are included, and the assistant has not claimed to run checks it only suggested. Keep unanswered questions in the case notes.

A question for your assistant

Read only. Explain [function] using its implementation and callers. Show how it handles an empty input. Cite files and symbols, distinguish inference from observation, and list unresolved questions. Do not install packages, change files, or run external requests.
Shared reference: a Getting started documentation view. Verify installation and endpoint instructions for your actual software. Reference desktop preview; final product screens may differ.
CONTINUE THE INVESTIGATIONReproduce a bug