11.7 Deployment Artifacts Do Not Redefine Implementation Artifacts [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== 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>