--- name: document-architecture-constraints description: "Draft or review arc42 section 2 for technical, organizational, and convention-based architecture constraints." --- # Architecture Constraints For repository work, follow the [project architecture index workflow](../document-architecture/references/architecture-index.md) to verify relevant entries, find missing locations, and confirm uncertain paths before editing. 1. Read the current chapter, requirements, applicable policies, and glossary. Identify binding constraints and trace each to a source or an explicit user statement. 2. Group constraints into technical, organizational, and applicable conventions. Record the restriction, rationale or authority, affected scope, and architectural consequence. Distinguish externally imposed constraints from design choices whose rationale belongs in an ADR. 3. Test whether each restriction limits an architectural choice. Flag duplicates, conflicts, temporary constraints, and exceptions. Check local versus deployed environments separately when rules differ. 4. Edit the relevant section using existing tables and terms. For a new table use Constraint | Source or rationale | Architectural consequence. When multiple delivery targets create materially different constraints, a compact table mapping targets to restrictions can clarify the impact.