EventFlow FE uses versioning to identify defined product states and revisions of its public technical documentation. Compatibility is evaluated against documented behavior, responsibility boundaries and applicable fiscal requirements.
Version Scope
| Version scope | Meaning |
|---|---|
| Product version | Identifies a released EventFlow FE product state |
| Documentation version | Identifies a revision of a public technical document or documented contract |
A documentation revision does not by itself imply a product compatibility change.
Compatibility Scope
Compatibility is evaluated across the product behaviors and boundaries on which users, connected products or fiscal processing may depend.
| Area | Compatibility concern |
|---|---|
| Fiscal document behavior | Changes that affect documented fiscal representation or processing |
| Document lifecycle | Changes to documented states or their meaning |
| SIFEN interoperability | Changes required by the applicable fiscal environment |
| Integration behavior | Changes to documented information exchange or responsibility boundaries |
| Operational guarantees | Changes to documented recovery, idempotency, isolation or observation behavior |
Change Classification
| Change class | Meaning |
|---|---|
| Compatible change | Extends or refines behavior without invalidating existing documented expectations |
| Compatibility-affecting change | Changes a documented contract, state meaning, integration expectation or guarantee on which an existing deployment may depend |
| Fiscal-required change | Introduces a change required to remain interoperable with applicable SIFEN rules or fiscal requirements |
Compatibility Principle
Compatibility is evaluated against documented behavior and fiscal requirements, not against undocumented internal implementation details.
Internal components may evolve without constituting a compatibility change when documented behavior, information semantics, lifecycle and state meaning, responsibility boundaries, integration exchange behavior and applicable fiscal behavior remain preserved.
Connected products and integrations therefore depend on the documented behavior established at the integration boundary rather than on EventFlow FE internal implementation.
Versioned Documentation
Technical documents carry their own documentation version. A documentation revision identifies a change to the published specification and does not by itself imply a product compatibility change.
When documented behavior or a public contract changes, the affected documentation is versioned accordingly.
Fiscal Compatibility
EventFlow FE compatibility includes continued interoperability with the applicable SIFEN fiscal environment. Changes required by the fiscal authority may require corresponding product changes even when existing product behavior would otherwise remain unchanged.
Authority-driven changes are treated separately from changes introduced solely by EventFlow FE.
Related Documentation
- 03. Fiscal Document Model — fiscal information represented by EventFlow FE.
- 04. Document Lifecycle — documented fiscal document states and lifecycle.
- 05. SIFEN Interoperability — interoperability with the fiscal authority.
- 10. Idempotency & Processing Guarantees — documented processing guarantees.
- 14. Integration Architecture — integration responsibilities and exchange boundaries.