Diem CMF .NET 11: Architecture
Status: Public design proposal and product vision. This series presents Diem CMF .NET’s intended architecture and capabilities. Proposed features remain subject to implementation and validation; existing components are identified separately.
This path explains the responsibilities behind the product experience. It uses the same Acme Catalogue throughout, then applies the architecture to the Lab and the planned product site.
Reading order
- From Domain Model to Running Site follows the full flow.
- Environments, Instances and Diem Domains provides the canonical glossary.
- Models, Workspaces and Release Artifacts defines authority and provenance.
- Bounded Contexts, Shared Kernels and ACLs defines responsibility boundaries.
- Bundles, Binary Wrappers and Infrastructure identifies integration layers and related sources.
- Rendering, Generation and Live Development connects .NET 11, source generation and frontend adapters.
- The Self-Describing Lab applies the architecture to the instance that operates it.
Questions this path answers
Where does a saved model change live? Which branch does an address follow? Which data does the admin manage? What makes a package usable by a renderer? What happens when a Lab describes a service on which the Lab itself depends?
Each question has one authoritative vocabulary. The architecture separates an intended configuration from an observed process, a source revision from a deployed release, and a package's capabilities from its activation in one instance.
The interfaces shown later in the specification are proposed contracts. Existing platform behavior and FrenchExDev background articles are cited separately; neither makes the proposed Diem implementation complete.
Previous: Diem Presenting and Developing Itself · Next: From Domain Model to Running Site · Series index