Operational Ontology Compiler Report
이 문서는 synthetic logistics source-world를 operational-logistics-ontology-v0.1 artifact로 compile한 결과다. 온톨로지는 source rows를 숨기지 않고, deterministic decision logic과 LLM context retrieval을 동시에 지원하도록 설계됐다.
1525nodes
5047typed edges
8ContextPackets
14node types
Minimal Node Types
| Type | Why it exists |
|---|---|
Location | 62 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
Asset | 11 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
Order | 22 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
OrderLine | 45 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
Shipment | 8 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
WorkTask | 70 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
HandlingUnit | 52 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
Resource | 6 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
LaborRole | 40 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
SourceRecord | 1179 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
Incident | 8 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
Risk | 8 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
Decision | 8 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
ActionOption | 6 nodes. Kept because it can be acted on, traversed, governed, explained, or used as provenance in logistics decisions. |
Decision Standard
Deterministic logic owns exact IDs, graph traversal, capacity math, source freshness, deadline/status filters, and action scoring. LLM judgment owns explanation synthesis, ambiguous operator-language interpretation, conflict narration, and customer/supervisor-facing wording.
Primary Context Packet
CTX-T05 is the first demo target because it combines early carrier arrival, dock pressure, stale source asymmetry, blocked premium work, labor/capacity limits, and handling-unit trace gaps.