repository-architecture-reviewlisted

# Repository Architecture Review ## Goal Identify a small number of evidence-backed improvements to PM Copilot's own architecture without turning a review into an unbounded refactor or an instruction to modify a host product. ## Scope - Applies only to `task_mode: self_improvement` and this repository. - Reviews routing, canonical ownership, document locality, validation seams, prompt budget, and maintainability. - Produces recommendations first. It changes files only after the user selects a recommendation or explicitly asks for implementation. ## Workflow 1. Define the review target from the user request; otherwise use recent commits and validation failures to select one high-churn area. 2. Read the active canonical documents, nearby validators, and only the evidence necessary to understand the target. 3. Look for duplicated authority, shallow documents that force excessive cross-file reading, unclear handoffs, unvalidated routing, or rules that cannot be loaded on demand. 4. For each candidate, climb a minimality ladder before proposing a change: remove the need, reuse an existing rule or validator, use the repository's existing mechanism, then add the smallest new surface that closes the gap. Do not treat a smaller diff as success if it removes validation, security, privacy, accessibility, evidence, or approval gates. 5. Produce up to three candidates. For each, state evidence, expected benefit, affected canonical owner, risk, validation approach, and why it is pref