EVENTFLOW FE · TECHNICAL DOCUMENTATION · 02
System Scope & Boundaries
Defines the operational perimeter of EventFlow FE and assigns responsibility across the fiscal product, SIFEN, the product integration boundary and the independent operational runtime.
Scope definition
EventFlow FE owns product-side fiscal execution; SIFEN owns the fiscal authority decision.
EventFlow FE begins with the product representation of a fiscal transaction and extends through preparation, electronic document generation, signing, QR generation, SIFEN interoperability and representation of the authority outcome within the product.
Independent operational processing begins outside the fiscal transaction boundary. Product activity may be observed through the integration layer without extending runtime responsibility into fiscal execution.
Responsibility boundaries
| Domain | Primary responsibility | Boundary |
|---|---|---|
| EventFlow FE | Product-side fiscal execution and fiscal state representation | Owns the transaction path inside the product |
| SIFEN | Fiscal authority processing and authoritative outcome | External fiscal authority |
| Product Integration Layer | Observation and translation of product activity | Separates domain semantics from shared runtime processing |
| Operational Runtime | Independent processing of operational evidence | Outside the fiscal transaction path |
In scope
- Product-side representation of fiscal transactions
- Fiscal document preparation and validation
- Electronic fiscal document generation
- Digital signing within the configured fiscal process
- QR generation associated with the fiscal document
- Submission and consultation through the applicable SIFEN integration path
- Processing and representation of SIFEN responses
- Product state associated with the fiscal document lifecycle
- Exposure of operational evidence through the product integration boundary
Out of scope
- Issuance of the fiscal authority decision
- Modification of an authority response returned by SIFEN
- Transfer of fiscal authorization authority to the operational runtime
- Requirement for runtime availability before a fiscal document can execute
- Execution of SIFEN transactions by the operational runtime
- Replacement of product-specific fiscal rules by shared runtime logic
Boundary model
Integration boundary
The Product Integration Layer translates EventFlow FE activity for shared runtime processing. Fiscal rules, SIFEN communication and document execution remain inside EventFlow FE.
Runtime boundary
Runtime availability is not a prerequisite for fiscal document execution.
The runtime processes operational evidence independently from the fiscal transaction that produced it. Runtime persistence, idempotency and recovery remain operational concerns rather than fiscal execution requirements.
Failure-domain ownership
Failures in document construction, signing, QR generation or SIFEN communication belong to the fiscal product domain. Failures in operational observation, runtime persistence or runtime continuation belong to the operational runtime domain.