mino-domain-model-completeness

Domain Model Completeness

Outcome Contract

Return the missing requirements, models, and paths of a fixed use case, and the obligations to pass to contracts and tests. Separate screening from the actual coverage of the model. The root of the authoritative package iscompleteness_package. Supported modes: design, review.

Reference Routing

• The first time, readskills/mino-core/references/shared-policies.mdand apply Evidence, approval, and judgment. If already read in the same context, do not read again. Make ordinary judgments using the main body and these common rules.
• When missing terms, contexts, or implicit concepts determine the judgment, readskills/mino-core/references/domain-discovery.mdand verify the difference in meaning using the same example.
• If there are requirements for file/process/test execution on the target system or multiple OSes, readskills/mino-core/references/platform-compatibility.mdand separate host, target, and verification layer. Do not read additionally merely to save a record of answers.
• Only when asked to create, update, or hand over the authoritative package, readskills/mino-domain-model-completeness/schemas/package.mdand preserve required fields and actual references.

Workflow

1. Fix the actor, use case, context, requirements, and out of scope. Do not decide necessary concepts from DB items or existing nouns alone.
2. Screen each requirement once across the 12 viewpoints: term_context, concept, constraint, state, transition, behavior, relationship, failure, time, writer, reader, and authority. Make each cell either a link to a model element with Evidence or an N/A with a reason. Only N/As with the same reason and Evidence can share a profile.
3. Distinguish necessary but absent elements as missing, unverified as unknown, and contradictory as conflicting. Separate having a definition in the requirements from actually existing and being guaranteed in the target model. present requires Evidence in the audited definitions, code, or observations, and a requirement alone must not be counted as satisfaction. Do not turn unknown into N/A. Use concept_kind only for concept.
4. Using constructors/setters, serializers, persistence, APIs/events, batch/admin, import, migration, and manual work as search candidates, trace writers/readers that reach the scope. Separate actual paths from unexplored areas, and do not fabricate the existence or absence of paths not in the provided materials.
5. Distinguish the owner of meaning, the owner of invariants, the authority for state transitions, and the source of truth for state. Check each writer's bypass, each reader's misinterpretation, leakage of business rules into UI/adapters, and the failure meaning for each relationship. Keep selection of the entire system to references and obligations. Multiple writers during migration require the period, conflict rules, reconciliation, deletion conditions, and owner.
6. Using thought experiments or disposable fixtures, trace entry → destructive input/order → propagation → business impact → expected invariants. Choose applicable counterexamples from boundary values, null, prohibited combinations, transition skips/reversals, concurrent writers, stale readers, and external success/internal failure. Judge observed results and defenses independently.
7. Attach CO / TO obligations to each necessary contract and test. If the downstream does not yet exist, do not issue a CI / T ID, and connect only if it actually exists.
8. screen denominator = number of requirements × 12, numerator = number of cells whose treatment was recorded as a link with evidence/N/A. Unknowns are also connected to unknown model elements, and if what is unconfirmed is recorded with evidence, it counts as screened. model denominator = number of cells other than N/A, numerator = number of cells that have Evidence in which all required elements are present and are not unknown/contradiction. missing/unknown/conflicting are not counted as present.

Hard Gates

• Do not treat a filled-in table as model complete. Do not treat unconfirmed writers/readers or bypass paths as audited.
• Do not perform destructive probes on production data. Not executed is not_executed, not prevented. Connect necessary probes to both the contract and test obligations.
• Do not modify the target code or operational data. Make correction requests as a handover that preserves authority.

Completion

If the required model and paths for a fixed scope are aligned with evidence, it is complete; if there is a known gap, it is incomplete; if it cannot be determined due to important unconfirmed matters, it is indeterminate. If a known gap and an unknown coexist, return both as incomplete. An audit artifact can become ready while reporting defects.