Validation and test plan

Documentation status: tutorial — see Maturity and evidence.

Use small fact sets with explicit expected deductions before generating application models.

Reference scenario

For product P1, warehouse W1 and time T1, suppose on-hand is 10, reserved is 4, available is 6 and the reorder threshold is 7. The support relations establish subtraction and comparison. The expected conceptual results are ConsistentStockPosition, BelowReorderThreshold, ReorderRequired and the corresponding indexed alert projection.

For an invalid state with on-hand 5 and reserved 7, the expected diagnostic is InvalidStockPosition.

Engine validation campaign

Test movement classification, arithmetic relation evaluation, temporal unification between position and policy, reorder propagation, invalid-state propagation, indexed tuple creation, duplicate handling during repeated propagation, multiple justifications for one derived fact, retraction after the final justification disappears, and absence of self-recreating projection cycles.

A domain reviewer must also confirm time semantics, whether availability is stored or derived, whether invalid positions are diagnostic or blocking, whether query orders match real usage, and whether reorder recommendations need additional supplier or lead-time context.

Record status explicitly: parser accepted, semantic resolution passed, propagation passed, or remaining capability pending.