Skip to content
EN FR

Temporal entities and support relations

Documentation status: tutorial — see Maturity and evidence.

The temporal model must keep product, warehouse and time explicit on every state or policy whose meaning changes over the lifecycle of the ERP application.

A StockMovement carries product, warehouse, movement kind, quantity and occurrence time. A StockPosition carries product, warehouse, observation time, on-hand quantity, reserved quantity and available quantity. A ReorderPolicy carries product, warehouse, effective time, threshold and target level.

Support relations

Keep calculations visible at the conceptual boundary by declaring typed support relations such as:

  • Subtract(left, right, result);
  • LessThan(left, right);
  • GreaterThan(left, right);
  • Negative(value).

These relations express the semantic dependency. Their numerical execution may be supplied by a registered runtime capability. The ontology should not hide arithmetic inside an opaque script if the calculation participates in reasoning and explanation.

Time propagation rule

When a conclusion depends on temporal state, the same time variable must flow from the source position and policy to the conclusion. This prevents combining a past position with a future policy.