← Full mapCurated public summary
Index
Entry 07PUBLIC HANDBOOK

Architecture, stack, and technology ecosystem

Separates Architecture, Stack, Runtime, Environment, Infrastructure, and Tooling; covers Runtime Profiles, provider neutrality, IaC, CI/CD, observability, Tool Catalog, and domain ownership versus orchestration.

Source & authority

Public explanation

PUBLIC HANDBOOK
Based on
Human Handbook 07 — Architecture, stack, and technology ecosystem
Related normative sources
  • NORMATIVE SOURCEStandard · Development Methodology
  • NORMATIVE SOURCEStandard · API / Orchestration Boundary
Authority
Public explanation — NON-NORMATIVE
Summary

Separates Architecture, Stack, Runtime, Environment, Infrastructure, and Tooling; covers Runtime Profiles, provider neutrality, IaC, CI/CD, observability, Tool Catalog, and domain ownership versus orchestration.

DCP Flow avoids treating architecture, stack, runtime, infrastructure, and tooling as synonyms. Each layer answers different questions and can evolve at a different pace.

Decision layers

Architecture defines structure and responsibilities; Stack names technologies; Runtime explains how software executes; Environment identifies contexts such as dev or production; Infrastructure provides resources; Tooling supports building, operating, and observing.

Key points
  • Architecture.
  • Stack.
  • Runtime and Runtime Profile.
  • Environment, Infrastructure, and Tooling.

A governed ecosystem

Provider neutrality, IaC, Configuration Drift, CI/CD, Observability, Automation, Orchestration, and the Tool Catalog keep technology subordinate to the solution. Tools are adopted by evidence rather than trend.

Key points
  • Cloud/provider neutrality.
  • IaC and drift.
  • CI/CD and observability.
  • Tool Catalog and Vendor Intelligence.

Domain ownership and orchestration

DCP Flow separates business truth from coordination. The backend/API or domain-owning system keeps durable truth; n8n or another orchestrator coordinates flows without becoming a parallel database or rebuilding business rules.

flowchart LR
A[User / System] --> B[API / Backend]
B --> C[(Domain Truth)]
B --> D[Persist / Accept]
D --> E[Outbox / Event]
E --> F[n8n Orchestrator]
F --> G[CRM / Provider / Channel]
G --> H[Outcome / Correlation]
H --> B
Diagram source
flowchart LR
A[User / System] --> B[API / Backend]
B --> C[(Domain Truth)]
B --> D[Persist / Accept]
D --> E[Outbox / Event]
E --> F[n8n Orchestrator]
F --> G[CRM / Provider / Channel]
G --> H[Outcome / Correlation]
H --> B
Key points
  • Domain Truth Ownership.
  • API/backend owns business truth.
  • Orchestrator coordinates flow.
  • SAVE FIRST → AUTOMATE AFTER when applicable.

EspoCRM as an ADOPTED lightweight CRM

EspoCRM is DCP Flow’s adopted lightweight CRM option when a decoupled commercial lifecycle is needed without introducing a full ERP or building a CRM from scratch. ADOPTED does not mean mandatory: Solution Discovery and Project Truth still determine fit.

Key points
  • Own Blueprint.
  • Own Runtime Profile.
  • Core/vendor read-only.
  • CRM entities remain contextual.

Architecture, Stack, Runtime, Environment, and Tooling answer different questions

Architecture describes structure, responsibilities, and boundaries; Stack identifies primary technologies; Runtime explains how they execute; Environment defines the operating context; Infrastructure provides resources; Tooling helps build, deploy, and observe. DCP Flow governs these choices without becoming a technology itself.

flowchart TB
A[Architecture
responsibilities and boundaries] --> B[Stack
technologies]
B --> C[Runtime
how it executes]
C --> D[Environment
where and under what context]
D --> E[Infrastructure
resources]
E --> F[Tooling
build operate observe]
Diagram source
flowchart TB
A[Architecture
responsibilities and boundaries] --> B[Stack
technologies]
B --> C[Runtime
how it executes]
C --> D[Environment
where and under what context]
D --> E[Infrastructure
resources]
E --> F[Tooling
build operate observe]
Key points
  • Architecture ≠ tool inventory.
  • Stack ≠ Runtime.
  • Branch ≠ Environment.
  • Tooling serves the methodology.

Runtime Profiles and provider neutrality make deployment boundaries explicit

Each active Blueprint should express a proportional Runtime Profile covering local execution, cloud target, CI/testing compatibility, shared hosting, persistence, health, and recovery. Architecture separates the needed capability — such as object storage — from a provider-specific service. IaC helps version infrastructure and detect drift, but does not remove Human Gates.

Key points
  • Shared hosting: SUPPORTED / CONDITIONAL / NOT_SUPPORTED.
  • Capability ≠ provider service.
  • Runtime divergence must be known.
  • Reproducible IaC does not mean automatically authorized.

CI, observability, and vendor knowledge are capabilities, not authority

CI automates repeatable evidence, but a green pipeline is not Human Acceptance. Observability asks which signals are needed to detect and diagnose, not which product must be installed. Vendor Intelligence supplies official version-aware knowledge without allowing vendor documentation to define governance. The Tool Catalog reduces repeated research and separates adoption from experimentation.

Key points
  • CI result ≠ Human Acceptance.
  • Observability ≠ installing a tool.
  • Vendor knowledge complements; it does not govern.
  • EXPERIMENTAL ≠ ADOPTED.

Fullstack TypeScript: another option, not a mandate

DCP Flow now includes an EVOLVING Fullstack TypeScript Blueprint for interactive applications with a dedicated API. React/Vite, Hono/Node, Zod and PostgreSQL/Drizzle form a reference architecture, while product selection still follows its actual needs. Astro remains appropriate for content-first websites and Laravel for applications where it fits better.

Key points
  • Solution Discovery and Golden Flow before stack selection.
  • Five focused skills that reuse cross-stack Quality Gates.
  • Independent repositories and databases when product ownership requires it.
  • EVOLVING does not mean production-proven.

Technology layers and proportional choices

DCP Flow is not a technology stack: it distinguishes methodology, architecture, stack, runtime, tooling, and infrastructure. Choose each component for capability fit, total cost, maintenance, and evidence rather than because another project uses it.

Key points
  • Review the applicable Blueprint and version during Foundation.
  • Observed runtime is stronger evidence than README claims.
  • Rewi's stack is not mandatory for Astro sites or adopted ERP platforms.
Contextual glossary+
Architecture

Structure of responsibilities, boundaries, and relationships in a solution.

Stack

Set of concrete technologies used to implement an architecture.

Runtime Profile

Reproducible profile of the runtime environment required by a solution.

IaC

Infrastructure as code: versioned, reproducible infrastructure definition.

Observability

Ability to understand system state through logs, metrics, traces, and signals.

Domain Truth Ownership

Explicit assignment of which system owns durable truth for each domain; avoids treating one tool as the source of truth for everything.

Orchestration

Coordination of steps, systems, or agents. The orchestrator coordinates flow; it should not own business truth that belongs to the backend or domain-owning system.