Learn DCL

DCL is a language for expressing architectural intent. The learning path starts with modelling tasks, then deepens into language constructs and reference material.

The useful question is not “what does this term mean?” It is:

How do I express this system responsibility, decision, integration, policy, or lifecycle in DCL source?

Learning Path

1. Start With One Responsibility

Write a capability that names a responsibility, the intent that starts it, and the outcomes it can produce.

• How do I define a capability?
• Capability concept
• Intent concept
• Outcome concept

2. Add Meaningful Decisions

Use rules and outcome causation to model validation and authorisation as language semantics rather than prose or hidden code paths.

• How do I model validation?
• How do I model authorisation?

3. Model Observable Work

Declare the effects, integrations, events, and observations that make behaviour visible and analyzable.

• How do I model effects and integrations?
• How do I observe a capability?
• Effects concept
• Events concept

4. Add Operational Intent

Attach policies to the right semantic boundary so reliability, security, governance, and performance requirements become part of the model.

• How do I define reliability policies?
• Policies concept

5. Model Progression And Composition

Use lifecycles when work progresses over time, and contexts when a model needs ownership and dependency boundaries.

• How do I define a lifecycle?
• How do I split a model into contexts?
• Lifecycles concept
• Contexts concept

After The Path

Use the Examples section for complete validated models, and the Reference when you need precise construct-level detail.