10.1 Use Case

Return to FX Demo Application

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 qualified_node performs its assigned governed function and records a work_performed_event. Each Work Performed Event identifies the work type, the applicable obligation, the performing node, the qualified_service_provider, the chargeable_work_unit, and the evidence Reference. The event does not expose full transaction payloads, detailed compliance findings, regulated data, or confidential business content to the cost plane.

The cost_recovery_compensation_and_settlement_plane Plane receives the cost-relevant records and applies the relevant Cost Rules. The plane produces demonstration compensation_claim, chargeback records, reimbursement records, or 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 a lack of assurance. When a required work record or evidence reference does not exist, the Cost Recovery, Compensation, and Settlement Plane records a performance_indicator. The indicator identifies an evidence gap for required governance work and supports review, remediation, audit, or governance escalation.