Context runtime
Use business meaning during execution, not only in a diagram.
Ask in the architecture design
- Question
- Relevant business concepts
- Follow ontology relationships
- Retrieve source data
- Apply relevant rules
- Answer
- Attach evidence
Run in the architecture design
A saved instruction identifies relevant context. When relevant information changes, the runtime evaluates that context and surfaces the resulting findings. Ask and Run share the ontology; their trigger and execution timing differ.
- Instruction
- Relevant ontology
- New information
- Context evaluation
- Result / exception
Why the runtime matters
For “Which customer orders are affected by Supplier A?”, the intended runtime follows Supplier → Material → Product → Order → Customer. The ontology defines meaningful relationships; source connections provide facts; evidence grounds the result.
What executes now
The current runtime performs keyword excerpt search or supported invoice comparisons against saved snapshots. Ask executes on demand. A Run executes on creation and when a source is connected. General ontology traversal, LLM reasoning and exception-only filtering are not implemented.