Domain Modeling

Overview

Resolve shared business language and rules from authoritative evidence. Default to terminology, ambiguity, rules, and boundary scenarios. Load lifecycle or bounded-context depth only when the business complexity actually requires it; do not turn the result into technical DDD, API, database, frontend, or backend design.

Consume urn:skills:task-request:v1; the portable typed handoff is urn:skills:domain-contract:v1. A durable domain document remains the business-language authority; the handoff references confirmed terms, rules, conflicts, decisions, and authority assets without copying product, interface, or delivery state.

Workflow