| Both sides previous revision Previous revision Next revision | Previous revision |
| fxdemo:06-part:11-fx-demo-application:11-1-use-case:start [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido | fxdemo:06-part:11-fx-demo-application:11-1-use-case:start [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| An FX transaction enters the demo environment and triggers governed processing across several qualified Nodes. The transaction requires validation, semantic interpretation, fraud screening, anti-money-laundering review, sanctions checking, policy evaluation, persistence, and evidence retention. | An FX transaction enters the demo environment and triggers governed processing across several qualified Nodes. The transaction requires validation, semantic interpretation, fraud screening, anti-money-laundering review, sanctions checking, policy evaluation, persistence, and evidence retention. |
| |
| Each [[dido:99_annexes:annex-b-terms-and-definitions:q:qualified_node]] performs its assigned governed function and records a [[dido:99_annexes:annex-b-terms-and-definitions:w:work_performed_event]]. Each Work Performed Event identifies the work type, the applicable obligation, the performing [[dido:99_annexes:annex-b-terms-and-definitions:n:node]], the [[dido:99_annexes:annex-b-terms-and-definitions:q:qualified_service_provider]], the [[dido:99_annexes:annex-b-terms-and-definitions:c:chargeable_work_unit]], and the [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence]] Reference. The event does not expose full transaction payloads, detailed compliance findings, regulated data, or confidential business content to the cost plane. | Each [[dido:99_annexes:annex-b-terms-and-definitions:q:qualified_node]] performs its assigned governed function and records a [[dido:99_annexes:annex-b-terms-and-definitions:w:work_performed_event]]. Each Work Performed Event identifies the work type, the applicable obligation, the performing [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node]], the [[dido:99_annexes:annex-b-terms-and-definitions:q:qualified_service_provider]], the [[dido:99_annexes:annex-b-terms-and-definitions:c:chargeable_work_unit]], and the [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence]] Reference. The event does not expose full transaction payloads, detailed compliance findings, regulated data, or confidential business content to the cost plane. |
| |
| The [[dido:99_annexes:annex-b-terms-and-definitions:c:cost_recovery_compensation_and_settlement_plane]] Plane receives the cost-relevant records and applies the relevant Cost Rules. The plane produces demonstration [[dido:99_annexes:annex-b-terms-and-definitions:c:compensation_claim]], chargeback records, reimbursement records, or [[dido:99_annexes:annex-b-terms-and-definitions:s:settlement_instruction]], depending on the demo scenario. | The [[dido:99_annexes:annex-b-terms-and-definitions:c:cost_recovery_compensation_and_settlement_plane]] receives the cost-relevant records and applies the relevant Cost Rules. The plane produces an demonstration [[dido:99_annexes:annex-b-terms-and-definitions:c:compensation_claim]], chargeback records, reimbursement records, or [[dido:99_annexes:annex-b-terms-and-definitions:s:settlement_instruction]], depending on the demo scenario. |
| |
| The use case also demonstrates provider comparison. Two Qualified Nodes offer the same governed function under the same interface, semantic model, policy obligation, evidence requirement, security requirement, residency constraint, sovereignty constraint, operational expectation, and service-level context. The demo compares the cost records and shows lower-cost compliant processing when both providers satisfy the same obligations and produce the required evidence. | The use case also demonstrates provider comparison. Two Qualified Nodes offer the same governed function under the same interface, semantic model, policy obligation, evidence requirement, security requirement, residency constraint, sovereignty constraint, operational expectation, and service-level context. The demo compares the cost records and shows lower-cost compliant processing when both providers satisfy the same obligations and produce the required evidence. |