An FX Policy Decision represents the outcome of evaluating policy constraints for access, disclosure, safeguarding, redaction, transformation, release, marking, obligations, or controlled movement of FX information.
The FX Policy Decision identifies the information subject to evaluation, the requested recipient, the purpose, the decision result, the rationale, the policy context, the obligations, the redaction or transformation requirements, the producing FX logical Node, the timestamp, and the provenance reference.
The FX Policy Decision participates primarily in the FX Logical Policy and Release Plane. It also supports the FX Logical Audit and Provenance Plane because policy decisions require reviewable context, rationale, obligations, and evidence expectations.
outcome of policy evaluation for governed FX information handling or release
Specialization of Logical Assertion from Part 2: Distributed Node-Based Logical Architecture, Section 8.8, Logical Policy Constraints from Part 2: Distributed Node-Based Logical Architecture, Section 11.7, and Policy and Release Plane from Part 1: Conceptual Architecture, Section 8.5; generalised from IEF policy-decision and release-control material in the original FX Demo Reference Architecture.
An FX Policy Decision is not a policy-engine output format, access-control result, API response, gateway decision, rule-engine result, log entry, or implementation-specific authorization token.
An FX Policy Decision states that selected transaction and cash-flow information qualifies for release to an External Oversight Participant only after redaction and obligation marking.