Bilingual navigation: Español
This area captures applied evidence: how the Evolith constitution behaves in real products, experiments, and research.
Goal: collect the evidence that validates (or challenges) Core decisions before lessons are promoted upstream.
Objectives:
- Keep the UMS applied reference as the canonical demonstration of the standard.
- Record adoption cases, PoCs, and research with enough detail to inform Core changes.
- Separate evidence (this area) from policy (Core), so products never mistake examples for rules.
Ordered from the canonical applied reference to exploratory research:
| Document | Description | Goal / Objective | Type | Mandatory |
|---|---|---|---|---|
| UMS Reference Hub | UMS reference models, comparisons, and architecture portal | Demonstrate real implementation | Applied reference | Yes |
| Adoption Cases | Documented platform adoption successes and lessons | Showcase success and learning | Applied reference | No |
| Rules Summary | Condensed view of the governing rules | Summarize the rule corpus | Reference | No |
| Architecture Intelligence | AI-consumable architecture knowledge catalog | Make knowledge machine-consumable | Area hub | No |
| Proofs of Concept | Experimental validations (e.g., Traefik Gateway) | De-risk decisions with experiments | Area hub | No |
| Research | Ongoing research notes | Explore future directions | Area hub | No |
The EN/ES pairing status for every knowledge document is tracked in the Bilingual Index.