# Business ontology and time semantics

Organize tables and files into meaningful business objects, not just a central store.

Version: 2.0.1 · Updated: 2026-09-26

## Objects and relationships

Orders connect to customers, production tasks and effective contracts. Each field has a source and each definition an owner; uncertain relationships remain unconfirmed.

## Delivery-risk example

The synthetic snapshot is September 25, 2026, 10:00 (UTC+8), with a September 28–30 query window. Delivery means factory completion and handover readiness, excluding transport and customer acceptance. Two days is a predicted risk, not a proven breach.

## Effective and approval time

Business-effective time is distinct from approval time. Unapproved rules cannot become active system knowledge. Historical answers distinguish what was known then from recomputation with current approved knowledge.