This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_and_release_node [2026/07/18 12:33] – external edit 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 |
|---|
| 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. | 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:n: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. | 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 ===== | ===== Definition ===== |