Evolith: Progressive Architecture Reference Base

Evolith is the corporate architecture upstream for product repositories. It defines reusable architecture standards, governance rules, ADRs, patterns, and operating guidance that satellite products inherit and specialize.

Evolith solves a common enterprise problem: teams need one clear place to understand what is reusable policy, what is a product-specific implementation, and how decisions are promoted from real products back into the architecture reference.

Separate conceptually before separating physically.

Language: English | Español

---

Key Entry Points

Entry Point	What it covers	Start here
Architecture Communication & Documentation	Architecture strategy, documentation map, visual diagrams, communication narrative, role-based reading paths, Evolith inheritance model	Architecture Communication Strategy
SDLC Flow & Delivery Governance	Delivery lifecycle, phase gates, roles, quality gates, Definition of Done, documentation expectations, construction-focused SDLC, release governance	SDLC Governance Center

Quick sub-links:

• Architecture Hub · Visual Architecture Backlog · Master Index · Getting Started by Role
• Construction-Focused SDLC · Engineering Manifesto · Contract Testing Guideline · ADR Registry

---

Start Here — Choose Your Path

Path 1 — I want a 5-minute overview

Read Executive One-Pager Visual (or Spanish). It answers: What is Evolith? Why do we need it? What is UMS?

Path 2 — I have a specific role

Role	Start here	Then read
Architect	Architecture Hub	ADR Matrix
Developer	Engineering Manifesto	UMS Reference Model
DevOps / SRE	Operations Hub	Infrastructure Hub
Product / PM	UMS Reference Model	Adoption Cases
AI Contributor	AI-Augmented Standards	AGENTS.md

Path 3 — I need to make an architectural decision

1. Check the ADR Registry to see if a decision already exists
2. If not, use the ADR Template to propose one
3. Submit to the Architecture Board for review

---

Evolith vs UMS — What Goes Where

Question	Evolith	UMS
What belongs here?	Reusable standards, principles, ADRs, governance, canonical patterns, quality gates	Product-specific implementation evidence
How does a product contribute?	Propose an ADR backed by real evidence	Provide executable proof of concept
What stays local?	Product routes, schemas, seeds, branding	Enterprise policy must go through Evolith governance

UMS is the official executable reference. See Adoption Cases for real examples of product lessons promoted into standards.

---

Contribution

Before contributing, read:

• AGENTS.md — Agent rules and conventions
• Repository Taxonomy — What goes where
• Child Repository Inheritance Guide — How products inherit from Evolith

Full navigation: MASTER_INDEX.md

---

License

Published under the MIT License.

---

_{Evolith - Enterprise Architecture Platform | Progressive Reference Corpus | Spec-driven AI-DD}