workspace-setuplisted

# Workspace setup (create `.troika/`, write the profile) A folder of repos in, a working workspace out: `.troika/settings.json`, the state directories, and a filled-in `.troika/PROFILE.md`. Every other Troika procedure stops immediately without this, so it is the first thing run in a new workspace and the only procedure that may run outside one. **Kind** procedure · **Used by** [architect](../../agents/architect.md) · **When** Troika has just been installed, a new folder of repos is being adopted, or the profile has drifted from how the repos actually work · **Ends with** `.troika/settings.json`, the three state directories, and `$TROIKA_PROFILE` written with every anchor answered The rule that shapes it: **read before you ask.** Style, tests, commands, branches and the local stack are already written down in the repos — derive them from the code and show the draft. Ask only what no file records: which repos are in scope, who reviews, which tracker, which tools, and how the team sounds. | Step | What it does | Advance only when | | --- | --- | --- | | [1](#root) | fix the workspace root | the root holds the repos and is not itself a repo | | [2](#scope) | list every repo, **ask which ones Troika covers** | the caller has ticked the list | | [3](#scaffold) | `resolve.py --init` — settings, state dirs, `.gitignore` | the three directories exist | | [4](#derive) | derive style, tests, commands, stack, branches, layering from the code | every in-scope repo has been probed, an