| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:c:crucible [2026/07/18 12:33] – external edit 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:c:crucible [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| Crucible supports repeatable development and deployment environments, security-compliant application delivery, cloud-agnostic operations, Infrastructure as Code, provisioning discipline, access-control discipline, workload segmentation, and continuous verification. | Crucible supports repeatable development and deployment environments, security-compliant application delivery, cloud-agnostic operations, Infrastructure as Code, provisioning discipline, access-control discipline, workload segmentation, and continuous verification. |
| |
| In the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set, Crucible belongs to implementation, deployment, environment-management, and runtime-infrastructure concerns. Crucible does not define logical [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], or logical interaction patterns. | In the Financial Systems [[dido:99_annexes:annex-b-terms-and-definitions:a:archetype|Archetype]] document set, Crucible belongs to implementation, deployment, environment-management, and runtime-infrastructure concerns. Crucible does not define logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Planes]], or logical interaction patterns. |
| |
| An implementation or deployment profile maps selected implementation artifacts, runtime services, configuration, security, observability, and deployment concerns to Crucible-managed environments when Crucible serves as the selected DevSecOps or deployment environment platform. | An implementation or deployment profile maps selected implementation artifacts, runtime services, configuration, security, observability, and deployment concerns to Crucible-managed environments when Crucible serves as the selected DevSecOps or deployment environment platform. |
| ===== Note ===== | ===== Note ===== |
| |
| Crucible is not a logical [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]], DDS Domain, DDS Topic, message bus, data structure, governance model, [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] model, or architecture layer. | Crucible is not a logical [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], logical [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[dido:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]], DDS Domain, DDS Topic, message bus, data structure, governance model, [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] model, or architecture layer. |
| |
| ===== Example ===== | ===== Example ===== |