Conceptual Patterns

Documentation status: guide — see Maturity and evidence.

Conceptual patterns are reusable ways to express recurring domain structures without copying implementation-specific designs.

What belongs here

A useful pattern identifies:

• the domain problem and invariant;
• the concepts and roles involved;
• the actions, events or processes that carry behavior;
• the publication boundary, if any;
• persistence or numerical projections only when they affect the pattern's operational constraints.

Pattern quality

Prefer a pattern when multiple domains share the same semantic structure. Avoid patterns that merely wrap a database schema, UI widget, transport endpoint or private Runtime class.

From pattern to application

recurring domain problem
  -> conceptual pattern
  -> project-specific vocabulary
  -> executable model
  -> generated/public bindings and publication

Patterns should make models more consistent while leaving project-owned identity and policy explicit.