Skip to main content
Welcome. This site supports keyboard navigation and screen readers. Press ? at any time for keyboard shortcuts. Press [ to focus the sidebar, ] to focus the content. High-contrast themes are available via the toolbar.
serard@dev00:~/cv

Diem CMF .NET 11: Specification

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 specifies the proposed behavior that an implementation must demonstrate. Must expresses a requirement; it does not mean that a feature exists today.

The contract examples are illustrative C# declarations for review. They are not a published API, and these Markdown pages do not constitute a compilable Diem SDK.

Contracts and lifecycle

  1. Site and Domain Contracts — instance identity, addresses, prefixes and source selection.
  2. Modeling and Module Generation — model authority, validation and generated ownership.
  3. Front: Pages, Areas, Zones and Widgets — composition and rendering rules.
  4. Admin Modules and Pluggable Types — editors, operations and module contributions.
  5. Lab: Branches, Builds and Deployments — provisioning, build, readiness and activation.
  6. Workspaces, IDEs and Hot Reload — live files, save behavior and process transitions.
  7. Extension Contracts and Compatibility — nested contributions and assembly boundaries.
  8. Content, Data and Promotion — publication, migrations and optional data merging.
  9. Reference Scenario and Acceptance Criteria — traceable success and failure scenarios.
  10. Marketplace Packaging and Extension Lifecycle — acquisition, activation, updates and removal.

Common assumptions

Runtime hosts and generated applications target the selected .NET 11 toolchain. Front and admin bindings for one instance share that instance's data scope. Branch instances are isolated by default. Saved source edits apply to a workspace; commits and production activation remain explicit operations.

Code defines defaults, constraints and editability. UI, CLI and automation resolve the same effective configuration. Extensions declare which capabilities they provide and which they require.

The canonical glossary defines terms. The component inventory separates related designs from verified components. The acceptance catalogue records requirements to implement, not test results already obtained.


Previous: The Self-Describing Lab · Next: Site and Domain Contracts · Series index

⬇ Download