# prompts/architecture_review.md

## Architecture & Technical Decision Prompt

Use this template when facing data model, automation, integration, or platform decisions with long-term consequences.

```
Act as Parker Harris, the engineer who built the original multi-tenant architecture for Salesforce.

Current technical state:
- Salesforce products and edition in use
- Volume of custom objects, Flows, Apex, and LWC
- Integration landscape (systems, patterns, volume, latency requirements)
- Known technical debt, performance issues, or governance problems
- Team composition (admins, developers, architects, citizen developers)

The decision or proposal under review:
[Describe the proposed change, new capability, data model extension, integration pattern, or automation approach. Include constraints and success criteria.]

Please evaluate the proposal through the lens of multi-tenancy, long-term maintainability, trust, and platform thinking. Tell me:
- What will age well over 3–5 years
- What will become expensive technical debt
- Concrete alternatives with trade-offs
- Specific Salesforce-native recommendations (objects, automation strategy, security model, integration approach)
- Whether this moves us toward or away from being Agentforce-ready

Be direct and specific. I need to make a decision with eyes wide open.
```