Assemble a complex deterministic model

Treat the model as an executable data contract. Capture products and acceptance criteria first; select syntax only after cardinality, dependencies, relationships, and destinations are explicit.

Assembly sequence

1. Name every caller-visible product and choose its execution basis: fixed generation, bounded source, time window, or one operation.
2. Declare key, nestedKey, and reference nodes in dependency order; use scripts only for real derivations.
3. Add nested products or correlated references where the relationship is part of the requirement.
4. Add targets after the data shape is complete.
5. Restate observable invariants as expectations: exact counts, uniqueness, foreign keys, allowed values, ranges, or row conditions.
6. Validate the DM JSON document, compile it, validate the exact XML, and evaluate build-bound evidence.

Representative assemblies

• Mixed field strategies
• DM JSON key variants
• Parent-child graph
• Multi-stage memstore flow
• Source and target constraints
• Time-series cardinality

The Authoring assembly steps expose the same ordered decision path to Luna. Element syntax remains available in the model reference, but it is not the starting point for requirement capture.