| Next revision | Previous revision |
| fxdemo:06-part:01-introduction:start [2026/06/26 15:38] – created nick_dido | fxdemo:06-part:01-introduction:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| ====== Introduction ====== | ====== Introduction ====== |
| | [[fxdemo:06-part:start | Go to Top]] |
| |
| Financial systems do not process transactions without cost. Each validation step, policy decision, fraud check, anti-money-laundering review, sanctions screen, semantic interpretation, persistence action, replay capability, audit record, and authorised release activity consumes resources and creates operational responsibility. Existing FX systems often recover these costs indirectly through exchange-rate spreads, fees, commissions, internal chargeback models, or bundled service pricing. These mechanisms may hide both the true cost of governed work and the absence of required work. | Financial systems do not process transactions without cost. Each validation step, policy decision, fraud check, anti-money-laundering review, sanctions screen, semantic interpretation, persistence action, replay capability, audit record, and authorized release activity consumes resources and creates operational responsibility. Existing FX systems often recover these costs indirectly through exchange-rate spreads, fees, commissions, internal chargeback models, or bundled service pricing. These mechanisms may hide both the true cost of governed work and the absence of required work. |
| |
| The FX Demo Reference Architecture treats cost recovery as an architectural concern. A distributed financial system requires a way to identify which Nodes performed governed work, which obligations required that work, which evidence proves that the work occurred, which cost rules apply, and which accounting or settlement artefacts result. Without this visibility, participants cannot reliably distinguish efficient compliant processing from under-compliance. | The FX Demo Reference Architecture treats cost recovery as an architectural concern. A distributed financial system requires a way to identify which Nodes performed governed work, which obligations required that work, which evidence proves that the work occurred, which cost rules apply, and which accounting or settlement artifacts result. Without this visibility, participants cannot reliably distinguish efficient compliant processing from under-compliance. |
| |
| Part 6 defines the Cost Recovery, Compensation, and Settlement Plane. The plane makes the economic footprint of governed financial processing visible, attributable, auditable, comparable, and recoverable. It supports compensation for qualified Nodes, cost allocation for shared infrastructure, ordinary accounting treatment, and competition among compliant implementations. | Part 6 defines the Cost Recovery, Compensation, and Settlement Plane. The plane makes the economic footprint of governed financial processing visible, attributable, auditable, comparable, and recoverable. It supports compensation for qualified Nodes, cost allocation for shared infrastructure, ordinary accounting treatment, and competition among compliant implementations. |