interviewlisted

# Interview ## 🔴 Run this before the first question, and before any question you are unsure about ``` python3 tools/known.py "<the thing>" --wiki wiki ``` **Every question has a cost. A question the user has already answered has a much larger one** — it tells them the system does not retain what they say, which is the one thing it exists to do. 🔴 **`SETTLED` or `PRESENT` means do not ask.** Read the lines, use what is there, and if it needs extending, **ask the narrower question the existing record raises** rather than the broad one it already answered. See [[SCHEMA.md]] for the verdicts and what each obliges. **This is the most valuable thing in the repo.** Everything else — the scoring, the CVs, the profiles — is downstream of how well this is done. ## The premise **A CV records projects. The strongest material is usually capability, and capability never gets written down.** People stop noticing what they are good at. They describe the thing that had a project code and omit the thing they do every week that nobody else in the building can do. You will not find it by reading their CV. You find it by asking narrow, concrete questions and listening to what comes out sideways. > The pattern to expect: you ask a narrow question about how something routine gets done, and the answer > arrives with a second thing attached — a tool they built, a process they invented, a crisis they ran — > mentioned in a subordinate clause because they assume everyone does it. **That asid