bootstraplisted

# Setting up the registers ## Before creating anything 1. Check whether `docs/architecture/` already exists. **If it does, do not overwrite.** Report what you found and offer to fill in what is missing. 2. Agree the **documentation language** (`pl` or `en`) with the user — it decides which set of `templates/` you use, and which file names the register gets (`fazy-realizacji.md` or `phases.md`). Record the choice in the register's `README.md` so the next session does not have to guess. The choice is **not permanent**: `/archirules:language` switches an existing project end to end. Say so, so nobody picks English "just in case" for a team that thinks in Polish. 3. Agree whether the project **starts from a process model** (rule P1). If it does, create the directory for models and the first model file — the notation is the project's choice (BPMN, a state machine, a sequence diagram); the method only requires that it be versioned rather than living in a presentation. ## What to create ``` docs/architecture/ README.md index + "binding requirements" section decisions/ (empty, for decision records) open-questions.md heading and empty numbering fazy-realizacji.md legend and empty phase table (or phases.md in English) ``` Create the verification register **only when** the first claim needs correcting. An empty verification register teaches people that it can be ignored. ## The binding-requirements section Th