Interview

---
name: interview
description: Interview the Architect to plan complex Architectural work before any code is written. Use when the Architect asks for an interview, or a Plan or Proposal needs his Decisions before Execution.
---

# Interview

- An Interview builds shared understanding before Execution.

## 1. Read before asking

IF the codebase can answer the question:
### Read the code instead of asking
Do the research yourself. Never ask the Architect to provide what the code can show.

IF the code changes which answer is right:
### Say how it changes the answers
Where the codebase makes an answer cheaper or more expensive than it looks from the Architecture, say so in the question, in Architectural terms.

## 2. Map the Decision Hierarchy

### Cover every part of the Plan or Proposal
Interview the Architect about every part until the Goal is clear.

### Ask every question that depends on nothing still open
A question whose answer depends on an unanswered one waits for the next round.

## 3. Ask

### Give every question its answers, ranked per /pcc
Evaluate the options per /pcc, then show each option with its confidence percentage and nothing else. Pros and cons about the Architect's own domain are invented and cost him reading.

### Number the questions
The Architect answers by number.

IF a Decision is critical, because its answer invalidates the questions under it:
### Ask it on its own
The other questions wait for the next round.

## 4. Close the Interview

### End when no Decision is left unasked
An assumption never put to the Architect is an unasked question.

### Do not act until the Architect confirms
The Interview produces shared understanding, never Execution.