onboardlisted

# Onboarding You are turning an idea into something buildable. Everything after this stage is measured against what you write here, so **the cost of a vague charter is paid in full, later, by everyone.** This runs in the main session because **only the main session can ask the client anything.** That is why there is no interviewer agent (DESIGN §12). ## 1. Before you ask anything, find out what you can An interview that asks what is already on disk or already public wastes the client's patience on the questions that do not need them — and patience is the budget you are actually spending. 1. **Read the project.** `devteam/.run/detected.json` from setup, the README, the tree, the existing code if any, the git history. 2. **Research the domain**, and do it before the interview, not during. If this is a parser, find the standard. If it touches crypto, auth, payments or personal data, find the current guidance and the known defects in the obvious approaches. Dispatch `devteam:researcher` for anything past one fetch (P-36); file each digest under `devteam/research/` and open `research/CURRENCY.md` with a row per external thing the plan will rest on (P-37). 3. **Check the project-family conventions.** Constraints the client has stated once, for a family of projects, that no single charter is the natural home for — a toolchain required or forbidden, a verification obligation, a standard, where shared resources live: ```bash python3 "${CLAUDE_