Purpose: reduce navigation friction for teams looking for the authoritative standards for Web, C#/.NET, and React.
Use this page when you already know the target stack and need the shortest path to the relevant Evolith standards.
Goal: give stack-focused teams the authoritative standard in one click, with zero exploratory navigation.
Objectives:
- Map each supported stack (React, .NET API, Node.js, agnostic baseline) to its single source of truth.
- Provide ordered fast paths so a team can apply a standard without reading the whole governance corpus.
- Make explicit what belongs to Evolith Core versus product repositories, so practices are promoted, not copied.
| Document | Description | Goal / Objective | Type | Mandatory |
|---|---|---|---|---|
| React Web Frontend Standard | Authoritative standard for React web frontends | Standardize React delivery | Normative standard | Yes |
| .NET API Standard | Authoritative standard for C# / .NET APIs | Standardize .NET API delivery | Normative standard | Yes |
| .NET & C# Tech Stack Profile | Approved runtime profile for .NET and C# workloads | Fix the approved .NET stack | Runtime profile | Yes |
| Agnostic Architecture Baseline | Runtime-agnostic architecture baseline for every stack | Constrain all stacks uniformly | Universal baseline | Yes |
| I am working on... | Read first | Then read | Use for |
|---|---|---|---|
| Any product or runtime | Agnostic Architecture Baseline | Reference Blueprint | Universal architecture constraints before stack-specific decisions |
| Web frontend in React | React Web Frontend Standard | React Frontend Section | React architecture, boilerplate, UI system, data access, testing, accessibility and promotion rules |
| C# / .NET API backend | .NET API Standard | .NET & C# Tech Stack Profile | ASP.NET Core APIs, host bootstrap, REST/GraphQL surface, EF Core, observability, resilience and quality gates |
| C# / .NET workers or non-HTTP runtime | .NET & C# Tech Stack Profile | Agnostic Architecture Baseline | Runtime stack decisions for non-API .NET workloads |
| Node.js / TypeScript backend | Node.js / TypeScript Tech Stack Profile | Agnostic Architecture Baseline | Runtime-specific backend stack decisions |
| Stack comparison or selection | All Runtime Profiles Index | Tech Stack Summary | Choosing or validating an approved runtime profile |
- Open React Web Frontend Standard.
- Confirm the product keeps product-specific details outside Evolith unless promoted.
- Apply the standard for folder structure, UI tokens, API boundaries, testing, security, and accessibility.
- Open .NET API Standard.
- Read it with the .NET & C# Tech Stack Profile.
- Apply the standard for host bootstrap, layered architecture, API surface governance, EF Core persistence, tenancy, observability, resilience, security, and quality gates.
- Start with React Web Frontend Standard when React is the target.
- Use Notification & Feedback Architecture when the work touches user feedback, toasts, drawers, errors, or mutation feedback.
- Escalate reusable UI or boilerplate decisions through ADR, governance standard, or canonical pattern before treating them as enterprise-wide.
| Concern | Source of truth |
|---|---|
| Universal architecture rules | reference/architecture/blueprints/authoritative-tech-stack-agnostic.md |
| API .NET standard | reference/governance/standards/engineering/api-dotnet/ |
| Runtime-specific backend choices | reference/architecture/blueprints/authoritative-tech-stack-*.md |
| React frontend rules | reference/governance/standards/engineering/web-frontend/react/ |
| Product-specific implementation | Child repository or UMS applied reference |
| Reusable promoted practice | Evolith ADR, governance standard, or canonical pattern |
Do not copy a product-specific practice into Evolith just because it exists in UMS or another satellite repository. Promote it only when it is reusable, documented, validated, and approved through the promotion path.