Differences

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

--- fxdemo:01-part:11-conceptual-rules-and-constraints:11-7-deployment-artefacts-do-not-redefine-implementation-artefacts [2026/08/04 07:08] – ↷ Links adapted because of a move operation nick_dido
+++ fxdemo:01-part:11-conceptual-rules-and-constraints:11-7-deployment-artefacts-do-not-redefine-implementation-artefacts [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 4: / Line 4: @@
 Deployment artifacts describe how implementation artifacts run in a concrete environment. They do not redefine the implementation artifacts or the conceptual elements behind them.
-For example, a Kubernetes pod may deploy a containerised [[dido:99_annexes:annex-b-terms-and-definitions:n:financial_node|Node]] implementation. The pod does not become the [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]]. A namespace may help organize deployment resources. The namespace does not become the [[dido:99_annexes:annex-b-terms-and-definitions:d:domain|Domain]], [[dido:99_annexes:annex-b-terms-and-definitions:e:ecosystem|Ecosystem]], or [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]].
+For example, a Kubernetes pod may deploy a containerised [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]] implementation. The pod does not become the [[dido:99_annexes:annex-b-terms-and-definitions:n:node_identity|Node Identity]]. A namespace may help organize deployment resources. The namespace does not become the [[dido:99_annexes:annex-b-terms-and-definitions:d:domain|Domain]], [[dido:99_annexes:annex-b-terms-and-definitions:e:ecosystem|Ecosystem]], or [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]].
 ----