Differences

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

--- fxdemo:03-part:04-fx-demo-logical-profile-principles:04-9-phase-extension-without-fx-logical-design:start [2026/07/11 11:10] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:03-part:04-fx-demo-logical-profile-principles:04-9-phase-extension-without-fx-logical-design:start [2026/07/18 12:33] (current) – external edit 127.0.0.1
@@ Line 4: / Line 4: @@
 The FX Demo Logical Profile supports later phase extensions without redefining the FX logical architecture.
-A later phase may introduce additional policy-governance, sovereignty, residency, metadata, aggregate-view, release, and [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] capabilities. Those additions should specialise the FX Demo Logical Profile rather than replace it. For example, a later Phase 2 profile may add distributed policy enforcement, replicated policy decision capability, policy administration, policy information sources, metadata or aggregate view generation, release gateways, recipient-specific release products, and release [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].
+A later phase may introduce additional policy-governance, sovereignty, residency, metadata, aggregate-view, release, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] capabilities. Those additions should specialize the FX Demo Logical Profile rather than replace it. For example, a later Phase 2 profile may add distributed policy enforcement, replicated policy decision capability, policy administration, policy information sources, metadata or aggregate view generation, release gateways, recipient-specific release products, and release [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]].
-Such extensions must preserve the distinction between the [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]] and the [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:logical_policy_and_release_plane|Logical Policy and Release Plane]]. Internal FX [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]] distribution does not itself authorise external release. Likewise, release of metadata, aggregate summaries, redacted views, masked views, or exception views does not imply authorisation to release full transaction detail.
+Such extensions must preserve the distinction between the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]] and the [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_policy_and_release_plane|Logical Policy and Release Plane]]. Internal FX [[dido:99_annexes:annex-b-terms-and-definitions:l:logical_data_plane|Logical Data Plane]] distribution does not itself authorize external release. Likewise, release of metadata, aggregate summaries, redacted views, masked views, or exception views does not imply authorization to release full transaction detail.
-The FX Demo Logical Profile remains platform-independent. Later phase profiles may map these extensions to [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] topics, APIs, policy engines, gateways, caches, services, containers, or other implementation mechanisms, but those mappings do not redefine the FX logical profile.
+The FX Demo Logical Profile remains platform-independent. Later phase profiles may map these extensions to [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] topics, APIs, policy engines, gateways, caches, services, containers, or other implementation mechanisms, but those mappings do not redefine the FX logical profile.
 ----