UMS - Enterprise User Management System

Open standards | Master index | Architecture portal | Leer en espanol

UMS is the official executable product reference for Evolith. It demonstrates how Evolith standards can be applied in a real modular monolith for unified identity, authorization, audit, governance, and enterprise user management.

UMS owns product-specific implementation evidence. Evolith owns reusable enterprise standards.

---

Start here

Need	Go to
Find React, Web, C# or .NET standards	Standards Quick Access
Understand the architecture	Architecture Portal
Review UMS architectural decisions	ADR Registry
Understand product scope	Product Vision
Review requirements	Requirements Index
Review delivery plan	MVP Product Backlog
Explore domain design	Construction Portal
Operate or observe UMS	Operations Portal
Browse all documents	Master Index

---

Quick paths by role

Role	Start with	Then read
Backend engineer	UMS API .NET Applied Reference	Construction Portal
Frontend engineer	UMS React Web Applied Reference	Evolith React Web Frontend Standard
Architect	Architecture Portal	Traceability Matrix
Product owner or QA	Functional Stories	MVP Backlog
DevOps or operations	Operations Portal	Solution Metrics Dashboard
Governance reviewer	Standards Quick Access	Architecture Portal

---

Standards and applied references

Area	UMS applied reference	Upstream Evolith standard
React Web frontend	UMS React Web Applied Reference	Evolith React Web Frontend Standard
.NET API backend	UMS API .NET Applied Reference	Evolith .NET API Standard
All standards	UMS Standards Quick Access	Evolith Quick Access by Stack

---

UMS vs Evolith

Question	UMS	Evolith
What belongs here?	Product-specific source evidence, applied examples, local decisions, routes, modules, schemas, runtime values	Reusable enterprise standards, principles, ADRs, canonical patterns, quality gates
What should not be generalized here?	Local implementation choices that only apply to UMS	Product-specific implementation evidence
How does a UMS practice become a standard?	It provides implementation evidence	It is promoted through ADR, governance standard, or canonical pattern

---

Technology snapshot

Layer	Technology
Backend	.NET 10, HotChocolate GraphQL, Minimal APIs REST
Frontend	React 18, Vite 5, TypeScript, TailwindCSS, Zustand, TanStack Query
Database	SQL Server 2022, Entity Framework Core
Monorepo	Nx, npm Workspaces
Methodology	BMAD-METHOD, Clean Architecture, DDD

---

Quick start

Prerequisites

• Node.js 20+
• .NET 10 SDK
• SQL Server 2022 or Docker

Backend

cd src/apps/ums.api
dotnet build
dotnet run

Frontend

cd src/apps/ums.web-app
npm install
npm run dev

Full stack

# Terminal 1 - Backend
cd src/apps/ums.api && dotnet run

# Terminal 2 - Frontend
cd src/apps/ums.web-app && npm run dev

---

Repository map

Area	Entry point	Purpose
Standards	docs/STANDARDS.md	Direct links to Evolith standards and UMS applied references
Architecture	docs/architecture	ADRs, blueprints, applied API/Web references, traceability
Governance	docs/governance	Product vision, scope, requirements, delivery documentation
Construction	docs/governance/construction	DDD design, bounded contexts, aggregates, events, commands
Operations	docs/operations	Metrics, runbooks, operational documentation
Source	src/apps	API and Web application source code
Full navigation	docs/MASTER_INDEX.md	Complete document tree

---

Security and quality notes

• CSP, CSRF, security headers, and runtime input validation are part of the implementation baseline.
• React Web and .NET API decisions are documented as applied references under docs/architecture/.
• Reusable enterprise standards must be promoted upstream to Evolith.

---

Contribution and governance

Before changing architecture or documentation, check:

• Standards Quick Access
• Architecture Portal
• Master Index
• AGENTS.md