Template Architecture

Praxis Template Architecture

Template Architecture documents the repositories Praxis produces: file ownership, framework entry points, request flow, dependency construction, capability integration, process lifecycle, and infrastructure topology.

flowchart LR
    Config[praxis.config.json] --> Modules[resolved template modules]
    Modules --> Files[framework-native source]
    Modules --> Runtime[dependency and lifecycle wiring]
    Modules --> Compose[Docker Compose]
    Modules --> K8s[Kubernetes when selected]
    Modules --> TF[Terraform when selected]

Loading

Standard Praxis

• Standard-Frontend-Architecture
• Express-Architecture
• Fullstack-Architecture
• Compose-Architecture

Standard projects compose independent frontend, backend, integration, and deployment modules. Express integration is functional and uses stable lifecycle/route anchors; it is not a class hierarchy.

Praxis Pro

• Django-Architecture
• Gin-Architecture
• Capability-Architecture
• Compose-Architecture
• Kubernetes-Architecture
• Terraform-Architecture

Praxis Pro always generates a backend stack and local Compose topology. Selected capabilities add framework-specific application code and may add Compose, Kubernetes, or Terraform resources. Terraform requires a chosen cloud.

Working safely

Use Extending-Generated-Projects when modifying an output. Agents changing templates must start with the Template-Agent-Guide and load the bounded context returned by scripts/resolve-template-context.mjs.

Generator boundary

Template modules are selected and composed by Praxis Core, but the output runs without Praxis. To understand selection or patch mechanics, use Core-Internals; to understand runtime behavior, remain in this domain.