Core structure for Architecture documents. For full templates with examples, load architecture-format-extended.
[!NOTE] This is the CORE template for architecture documents. For full examples with JSON samples, diagrams, and detailed sections, load
architecture-format-extended.
Your architecture must contain the following sections:
Link to TASK and brief summary of requirements.
Description of the system in terms of functions it performs.
For each functional component describe:
Component Name: [Example, "User Management"]
Purpose: [Why this component is needed]
Functions:
Dependencies:
[Mermaid diagram showing connections between components]
Description of the system in terms of physical/logical components.
Which architectural pattern is used:
Justification: [Why this style was chosen]
For each system component describe:
Component Name: [Example, "User Service"]
Type: [Backend service / Frontend / Database / Message Queue / etc.]
Purpose: [Why needed]
Implemented Functions: [Links to functions from functional architecture]
Technologies: [Programming language, frameworks]
Interfaces:
Dependencies:
[Mermaid diagram showing components and their interaction]
Description of data structure in the system at a high level.
Entities:
Description: [What this entity represents]
Key Attributes:
id (UUID) — unique identifierRelationships:
Business Rules:
[!TIP] For detailed logical data model with table schemas, indexes, and NoSQL examples, load
architecture-format-extended.
[!IMPORTANT] The following sections are available in
architecture-format-extended:
- 5. Interfaces — External APIs, Internal Interfaces, Integrations
- 6. Technology Stack — Backend, Frontend, Database, Infrastructure
- 7. Security — Authentication, Authorization, Data Protection, OWASP
- 8. Scalability and Performance — Scaling, Caching, DB Optimization
- 9. Reliability and Fault Tolerance — Error Handling, Backup, Monitoring
- 10. Deployment — Environments, CI/CD, Configuration
Load
architecture-format-extendedwhen:
- Creating a NEW system from scratch
- Major architectural refactor (>3 components affected)
- Sophisticated or complex requirements
- User explicitly requests full template
List of questions requiring clarification from user.
| Condition | Load |
|---|---|
| Updating existing architecture (minor change) | core only |
| Adding new component to existing system | core only |
| Creating NEW system from scratch | extended |
| Major refactor (>3 components changed) | extended |
| Sophisticated requirement / complex task | extended |
| User explicitly requests full template | extended |