ARCHITECTURE CHANGE REVIEW PROMPT
Replace bracketed fields. This is a prompt template, not an MCP client configuration.

Target organization: [organization]
Target project/model: [project and model ID]
Repository and revision: [repository, commit]
Proposed change: [for example, a new payment authorization contract]

Read the architecture before proposing code changes.
1. Identify the payment provider, its callers and the owning container.
2. Return actual model element and relationship IDs from tool results.
   Do not invent identifiers or imply a missing relationship proves no dependency.
3. Inspect repository evidence for each dependency you intend to change.
4. Separate model observations, code observations, assumptions and proposals.
5. Describe the impact on context, container and component views.
6. Present a proposed model update for review before applying it.

Return these sections:
- Model evidence: element/relationship IDs, names and observed responsibilities.
- Repository evidence: commit, file, symbol/configuration and what it establishes.
- Unresolved questions: missing evidence and the person/check needed to resolve it.
- Proposed implementation change: boundary, contract and expected behavior.
- Proposed model change: existing IDs to update and new entities, if any.
- Validation: affected views, implementation checks and expected outcomes.

If model access is unavailable, stop the architecture-dependent conclusions and
report which target or connection detail is missing. Do not treat a public viewer
as authorization to edit its source workspace.