| Both sides previous revision Previous revision Next revision | Previous revision |
| public:99_annexes:annex-b-terms-and-definitions:c:crucible [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:c:crucible [2026/09/13 15:32] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| | ====== Crucible ====== |
| | |
| | [[public:99_annexes:annex-b-terms-and-definitions:start|Return to Terms and Definitions]] |
| | |
| | ===== Discussion ===== |
| | |
| | Crucible is a DIDO Solutions DevSecOps and DevOps platform that simplifies and secures software development, deployment, and management. |
| | |
| | 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 [[public: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 [[public:99_annexes:annex-b-terms-and-definitions:f:financial_node|Nodes]], logical [[public:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoints]], logical information structures, logical [[public: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. |
| | |
| | ===== Definition ===== |
| | |
| | //DevSecOps and DevOps platform used to simplify, secure, provision, deploy, manage, and verify software development and runtime environments// |
| | |
| | ===== Source ===== |
| | |
| | Generalised from DIDO Solutions Crucible material and its use as an implementation and deployment concern in [[private:01-fxdemo:04-part:start]] and [[private:01-fxdemo:05-part:start]]. |
| | |
| | ===== Note ===== |
| | |
| | Crucible is not a logical [[public:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], logical [[public:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]], [[public:99_annexes:annex-b-terms-and-definitions:r:runtime_plane|Runtime Plane]], DDS Domain, DDS Topic, message bus, data structure, governance model, [[public:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] model, or architecture layer. |
| | |
| | ===== Example ===== |
| | |
| | [[private:01-fxdemo:05-part:start]] uses Crucible as a deployment-environment option for running Phase 0 implementation artifacts after the logical Nodes and logical Communication Endpoints have already been defined in platform-independent form. |
| |