Differences

This shows you the differences between two versions of the page.

--- dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_and_release_node [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_and_release_node [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== FX Policy and Release Node ======
+[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+===== Discussion =====
+The FX Policy and Release Node evaluates release conditions and controls the governed disclosure of FX information.
+The FX Policy and Release Node performs policy evaluation and release control responsibilities. It receives release requests, evaluates policy constraints, determines whether information qualifies for release, identifies required redaction, masking, transformation, aggregation, marking, or packaging, records obligations, produces FX Policy Decisions, and prepares FX Release Packages for authorized recipients.
+The FX Policy and Release Node supports sovereignty-aware and residency-aware release at the FX logical profile level. Full FX transaction detail may remain within an authorized institutional, local, national, or other residency domain. Authorized metadata, aggregate summaries, derived indicators, redacted views, masked views, exception views, or recipient-specific release products may be prepared for broader oversight only when policy decisions permit that release.
+The FX Policy and Release Node participates primarily in the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]]. It also participates in the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] by recording policy decisions, release rationale, source information references, release obligations, release package lineage, and release provenance.
+A later phase profile may specialize this logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] into distributed policy enforcement, policy decision, policy administration, policy information, metadata or aggregate view builder, release gateway, and audit/evidence capabilities. Those later capabilities specialize the FX Policy and Release Node responsibilities. They do not require all FX transaction data to pass through a single central policy server or gateway.
+===== Definition =====
+//responsible for evaluating release conditions and controlling governed disclosure, sovereignty-aware release, residency-aware movement, metadata or aggregate release, and authorized release products for FX information//
+===== Source =====
+Specialization of Logical Node from [[fxdemo:02-part:start]], Section 6.2, Logical Policy Constraints from [[fxdemo:02-part:start]], Section 11.7, and [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] from [[fxdemo:01-part:start]], Section 8.5; generalised from IEF policy-layer, release-control, redaction, obligation, release-package, and policy-mediated release material in the original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
+===== Note =====
+The FX Policy and Release Node does not prescribe a policy engine, access-control product, redaction tool, aggregation service, gateway, release service, API, cache, deployment boundary, or central transaction-data router.
+===== Example =====
+The FX Policy and Release Node evaluates whether an External Oversight Participant may receive an aggregate currency-pair-and-denomination summary while the full transaction details remain within the originating national domain.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>