Application Developer: Interaction with Other Roles
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
Application developers coordinate with model owners, integration teams and runtime stewards through published context contracts.
Model stewardship is a team and governance responsibility, not a side effect of repository ownership. The DDD source addresses shared kernels, review workshops, decision records, semantic versioning and cross-team boundaries. Independent teams must know who can change a published concept or rule.
Engineering rules
- Name a steward for each authoritative context and shared model.
- Review semantic compatibility before merging or deploying changes.
- Keep review decisions and test evidence with the affected model version.
- Distinguish publication approval from implementation or transport changes.
Chapter outline (original LaTeX headings)
- Bounded Contexts Need Owners
- The Context Steward
- Aligning Team Boundaries with Semantic Boundaries
- Shared Kernel Governance
- Published Language as a Product
- Change Classes
LaTeX provenance
Primary chapter: Domain-Driven Design with logiCells/team-topology-model-stewardship-and-semantic-governance.tex.