domain

You document business logic by describing domain concepts and flows, then confirming the generated draft before writing it to disk as plain text with required frontmatter and a tracked changelog.

The best way to keep domain documentation in sync with code is using changelog-driven governance that tracks changes, supports module splitting, and maintains a human-readable domain model alongside code updates.

You need domain-driven design documentation for projects with multiple modules and evolving rules where teams must align on business invariants and handoffs require a human-readable domain model to reduce miscommunication.

Yes, you can split and reorganize domain models across multiple modules using the dedicated Split and Module modes, which maintain structural traceability and preserve business intent through changelog-driven governance.

You track changes to business rules over time through changelog-driven governance that records every update, supports versioning, and ensures evolving domain concepts remain traceable across team handoffs.

Using plain text for capturing domain concepts conveys business rules and invariants that code comments cannot, reducing team miscommunication and handoffs by preserving business intent across structural changes.