extract-domain-logic

A module-level domain logic document captures per-module behaviors, inputs, and outputs to support object-sketch handoffs. It maintains an auditable record of domain behaviors through Extract and Domain-logic sections, including Unallocated and Rejected modules.

Capturing domain logic in clear prose involves applying a seed file and template to produce a structured document. This approach preserves module order and maintains an auditable record of domain behaviors, including support for Unallocated and Rejected modules.

You generate an extracted domain logic document by copying your seed file into the designated path and refining it using a template. This process preserves module order and captures per-module domain behaviors, including Unallocated and Rejected modules, for downstream handoffs.

Yes, domain logic extraction explicitly supports Unallocated and Rejected modules through its template-driven formatting. This maintains an auditable record of all domain behaviors, including modules set aside during the partitioning and analysis process.

You need a structured domain logic document during per-module domain analysis workflows to enable downstream hand-offs to object-sketch and business-logic artifacts. It provides traceability to seeds and sources before or after key-abstraction steps.