architecture-model-bootstrap

# Architecture Model Bootstrap Turn the deterministic candidate the Impact pane generates into a model a reader can confirm. The server already derives a bounded, grounded skeleton from the worktree (one SoftwareSystem, a Container per workspace, Components for source directories). This skill does the **semantic** half a static analyzer cannot: naming, grouping, kinding, describing, and proposing the external systems the code only hints at — without inventing structure the evidence does not support. Default to the repository's reply language. Keep edits grounded and reversible: the output is a *proposal* a human saves, never a fact you assert. ## When to use - A project declares no model and the Impact pane falls back to a generated one. - A reader wants the generated skeleton refined before saving it as declared. - An existing declared model needs elements renamed, merged, split, re-kinded, or described against current code. Do not use it to invent business capabilities, runtime traffic, or external systems that no evidence supports. L1 system context and external systems stay **proposed and human-confirmed**, per the parent spec's non-goal. ## Inputs (the evidence pack) Gather these before proposing anything: 1. **The generated candidate.** Open the Impact pane on any commit, or read the model the server would generate — one SoftwareSystem, Containers per workspace manifest, Components per source directory, every element tagged `generated`, plus bindings ...