Runtime observation provides an independent representation of operational evidence associated with fiscal activity.
An observation records what the operational plane can establish about an operation at a given point in time. It does not represent a fiscal authority decision.
Observation Boundary
The observation boundary begins when operational evidence associated with a fiscal operation becomes available to the EventFlow Core Runtime.
Evidence may originate during document processing, submission or result handling. Observation does not transfer ownership of the underlying fiscal operation to the runtime.
Observation Contract
An operational observation carries the context required to associate evidence with the operation that produced it.
At the public contract level, this includes:
| Information | Purpose |
|---|---|
| Operation identity | Associates evidence with a specific operation |
| Subject reference | Identifies the operational subject to which the evidence belongs |
| Evidence classification | Describes the class of operational evidence being observed |
| Observation time | Records when the evidence became observable |
| Source context | Identifies the origin or execution context of the evidence |
| Evidence context | Carries the information required to interpret the applicable observation |
| Schema/version context | Identifies the applicable public contract version |
The public contract defines the information boundary. Internal processing representations are not part of this specification.
Observed Information
Runtime observation distinguishes operational evidence from conclusions derived from that evidence. An observation may therefore preserve available information without asserting that the underlying fiscal operation succeeded, failed or reached a final authority state.
This distinction applies when external communication, delayed responses or interrupted processing leave the available evidence incomplete.
Observable Guarantees
Runtime observation exposes the following externally relevant properties:
| Property | Guarantee |
|---|---|
| Fiscal independence | Observation does not initiate or authorize SIFEN transactions |
| Execution independence | Fiscal execution does not require runtime availability |
| Traceability | Observed evidence remains associated with the operation that produced it |
| Durable continuity | Accepted operational information can participate in recovery across process interruption |
| Repeat-safe processing | Re-observation or recovery does not imply repeated external fiscal effects |
| Authority preservation | Runtime information never replaces the fiscal result established by SIFEN |
Durability and repeat-safe processing are specified in greater detail in Chapters 09 and 10.
Uncertainty and Incomplete Observation
Operational systems must distinguish lack of confirmation from confirmation of failure.
A process interruption, unavailable external response or incomplete local observation may leave the operational plane without sufficient evidence to establish the final condition of an operation.
In such cases, EventFlow FE preserves the distinction between:
- information that has been observed;
- information that has been externally confirmed; and
- information that remains unresolved.
The runtime does not assign a fiscal conclusion where the available evidence does not establish one.
This property allows later recovery or reconciliation to proceed from preserved evidence rather than from an assumed outcome.
Related Documentation
- 07. Operational Architecture — separation between fiscal execution and operational observation.
- 09. Durability & Recovery — preservation and recovery of operational information.
- 10. Idempotency & Processing Guarantees — repeat-safe processing and effect guarantees.
- 11. Failure Model & Isolation — separation and containment of operational and fiscal failures.
- 12. Production Validation — validation of these properties in the production environment.