Temporal stock implementation checklist

Documentation status: tutorial — see Maturity and evidence.

A developer should be able to complete the case study without the PDF when every item below is satisfied.

• The business specification names objects, policies, observations and invariants without implementation terms.
• Canonical vocabulary and synonyms are recorded.
• Identity choices for movements, positions and policies are explicit.
• The movement-kind vocabulary is either deliberately closed or deliberately extensible.
• Time is carried through positions, policies and derived conclusions.
• Arithmetic dependencies are visible through typed support relations.
• Invalid conditions produce explicit diagnostic facts when they must remain observable.
• Query-oriented projections are justified by real access patterns.
• Reference facts and expected deductions exist before model generation.
• Parser acceptance and semantic behavior are reported separately.
• Propagation, justification, retraction and projection-cycle tests are included.
• A reviewed generation policy covers persistence, caches, publication, views, indexes and diagnostics.
• Generated artifacts retain links back to requirements and semantic constructs.
• The generated application passes compilation, loading and behavioral-equivalence tests.

Continue with From validated semantics to declarative models for the general generation discipline.