fxdemo:01-part:11-conceptual-rules-and-constraints:11-7-deployment-artefacts-do-not-redefine-implementation-artefacts

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
fxdemo:01-part:11-conceptual-rules-and-constraints:11-7-deployment-artefacts-do-not-redefine-implementation-artefacts [2026/06/29 14:31] – removed - external edit (Unknown date) 127.0.0.1fxdemo: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 1: Line 1:
 +====== 11.7 Deployment Artifacts Do Not Redefine Implementation Artifacts ======
 +[[fxdemo:01-part:start | Go to Top ]]
 +
 +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: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]].
 +----
 +
 +<WRAP centeralign>
 +
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +</WRAP>