====== Policy and Release State Consideration ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]]

===== Discussion =====

Policy and release-state considerations identify the logical conditions governing whether FX information qualifies for external release.

The [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_and_release_node|FX Policy and Release Node]] evaluates release requests, policy constraints, recipient context, purpose, redaction requirements, transformation requirements, marking requirements, obligations, and source information provenance. It produces an [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_decision|FX Policy Decision]] and, when the decision permits release, prepares an [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_release_package|FX Release Package]].

Policy and release-state considerations preserve the distinction between internal FX processing and authorized external disclosure. FX Data Plane information does not become externally releasable merely because the FX logical node network produced or consumed it.

Policy and release-state considerations identify the evaluated information, recipient, purpose, policy context, decision, obligations, release package reference, timestamp, and provenance reference.

===== Definition =====

//Logical conditions governing policy evaluation and authorized release of FX information.//

===== Source =====

Specialization of [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_decision|FX Policy Decision]] from Section 9.8, [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_release_package|FX Release Package]] from Section 9.9, [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_evaluation_role|Policy Evaluation Role]] from Section 7.7, [[dido:99_annexes:annex-b-terms-and-definitions:r:release_control_role|Release Control Role]] from Section 7.8, and [[dido:99_annexes:annex-b-terms-and-definitions:p:policy_and_release_plane|Policy and Release Plane]] from Part 1, Section 8.5; generalised from IEF policy-layer, release-control, redaction, obligation, and external oversight material in the original FX Demo Reference Architecture.

===== Note =====

Policy and release-state considerations do not prescribe a policy engine, access-control product, redaction tool, gateway, API, report format, file package, or delivery mechanism.

===== Example =====

An [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_cash-flow_obligation|FX Cash-Flow Obligation]] enters release evaluation when an oversight request seeks external disclosure. The [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_and_release_node|FX Policy and Release Node]] produces an [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_policy_decision|FX Policy Decision]] before preparing any [[dido:99_annexes:annex-b-terms-and-definitions:f:fx_release_package|FX Release Package]].

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>