A failure is classified by the responsibility boundary it affects. A failure in one operational domain does not, by itself, establish failure in another.
Failure Boundary
EventFlow FE separates failures affecting fiscal transaction execution from failures affecting operational observation and runtime processing.
The presence of a runtime failure does not by itself establish that the underlying fiscal operation failed. Likewise, a fiscal communication failure does not by itself invalidate operational information already established by the runtime.
Failure Domains
| Responsibility boundary | Failure scope |
|---|---|
| Fiscal transaction | Fiscal document execution and SIFEN interoperability |
| Product integration | Observation and translation of product-domain information |
| Operational runtime | Processing, preservation and recovery of operational information |
Isolation Properties
| Property | Observable guarantee |
|---|---|
| Authority preservation | A runtime failure does not alter a fiscal result already established by SIFEN |
| Failure classification | A failure is attributed to the responsibility boundary supported by the available evidence |
| No inferred cross-domain failure | Failure in one boundary does not by itself establish failure in another |
| Evidence preservation | Previously established operational evidence is not invalidated solely because later processing fails |
| Unresolved-state preservation | Insufficient evidence after failure remains unresolved rather than being converted into an assumed outcome |
Incomplete Information After Failure
A failure may interrupt processing without establishing the final condition of the affected operation. Where the available evidence is insufficient, the operational representation remains unresolved.
Failure classification therefore follows available evidence. Interruption, absence of confirmation and confirmed failure remain distinct conditions.
Recovery Relationship
Isolation determines the responsibility boundary affected by a failure. Recovery determines what operational processing can continue from information that was durably established before the interruption.
Recovery does not change the classification of an established fiscal outcome.
Related Documentation
- 07. Operational Architecture — responsibility boundaries and separation of fiscal and operational processing.
- 08. Runtime Observation — operational evidence and incomplete observation.
- 09. Durability & Recovery — durable continuity after interruption.
- 10. Idempotency & Processing Guarantees — repeat-safe processing and external-effect restraint.
- 12. Production Validation — production validation of operational guarantees.