> ## Documentation Index
> Fetch the complete documentation index at: https://archie.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Strategy

> The Technical Strategy spec — architecture sections plus Mermaid diagrams that document and drive the generated codebase.

The Technical Strategy spec is the architecture reference for your project. Archie generates it from your plan and uses it when making structural decisions during code generation. It also doubles as the engineering README for anyone joining the project later.

## What it covers

Each section is a short prose block; some sections also have a generated Mermaid diagram alongside. The full set:

* **Executive Summary** — one-paragraph view of what the system does and why
* **System Overview** — the major components and how they interact
* **Architectural Principles** — guiding rules (e.g. "single source of truth", "fail loudly")
* **Tenancy Architecture** — single-tenant vs. multi-tenant, isolation strategy
* **Archie BaaS Integration** — how the app uses Archie Core (database, auth, storage, hosting)
* **Custom Function Design** — patterns for server-side logic the agents generate or you write
* **Core Components** — the major code modules and their responsibilities
* **API Strategy** — REST, GraphQL, or both; auth, versioning, pagination defaults
* **Data Architecture** — how data flows; database engine; caching strategy
* **Frontend Architecture** — module structure, state management, routing
* **Security Framework** — auth, encryption, input validation, audit logging posture
* **Scalability Design** — vertical vs. horizontal scaling assumptions
* **Custom Function Specifications** — per-function specifications referenced from custom-function code
* **Database Strategy** — schema management, migrations, backup posture
* **Risk Assessment** — known risks and mitigation patterns

## Diagrams

Archie generates Mermaid diagrams for the major views:

* **System Diagram** — the major components and their relationships
* **Integration Diagram** — third-party services and data flow between them
* **Components Diagram** — internal module breakdown
* **Data Diagram** — entity relationships, foreign keys, denormalization choices
* **Security Diagram** — auth flows, trust boundaries, encryption points

You can regenerate any diagram individually if your strategy evolves. Archie writes the Mermaid source directly into the spec, so you can edit the diagrams by hand if you need precision.

## What this drives

* The build agents read the strategy when making architecture-level decisions during code generation
* The diagrams ship into the generated repo's `/docs` folder for engineering reference
* The risk assessment surfaces in code-review prompts when you regenerate code

## FAQ

<AccordionGroup>
  <Accordion title="Can I edit individual sections without regenerating the whole strategy?">
    Yes. Each section is independently editable. Archie does not regenerate sections you haven't touched, and edits don't cascade unless you ask.
  </Accordion>

  <Accordion title="What if a generated diagram is wrong?">
    Edit the Mermaid source directly. Archie stores diagrams as Mermaid text in the spec, so they're as editable as the prose around them. You can also regenerate just that one diagram.
  </Accordion>

  <Accordion title="Does the strategy affect existing generated code?">
    Strategy edits affect the next code generation, not the existing code. Archie surfaces the diff before applying so you can review what's about to change.
  </Accordion>

  <Accordion title="Can I export the strategy as a PDF for stakeholders?">
    Yes — strategy export uses the same PDF flow as the plan export. Useful for handoffs, investor diligence, and onboarding documents.
  </Accordion>
</AccordionGroup>