FR-DEP-005 — Deploy Platform Services

Go to Crucible Deployment Orchestration Requirements

Statement

Crucible SHALL deploy an identified Platform Service to a target Infrastructure Environment.

Source Statement

The system shall deploy Platform Services.

Source

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-005.

Assessment

The source statement expresses a direct functional behavior but requires terminology and normative-language normalization.

The following Specification, Discipline, and Authoring findings apply:

The system does not use the defined system nameshall does not follow the established uppercase normative conventionPlatform Services identifies a class of deployment subjects, but does not identify the target Infrastructure EnvironmentThe source statement does not define which Platform Services apply to a particular deploymentThe source statement does not prescribe a platform, provider, deployment tool, service implementation, or deployment methodThe source statement does not independently require activation, validation, rollback, compliance assessment, monitoring, or lifecycle recordingThe normalized Statement:

Replaces The system with CrucibleRetains the direct and testable verb deployIdentifies a Platform Service as the deployment subjectIdentifies the target Infrastructure EnvironmentPreserves implementation independenceRetains one primary required behaviorThe applicable Infrastructure Configuration or deployment specification identifies the Platform Service and its required configuration.

Platform Service should receive a glossary definition because it identifies a distinct deployment subject used by this requirement.

Rationale

A Platform Service supplies a shared capability used by applications, Workloads, operators, or other platform components.

Platform Services may include:

Identity servicesAuthorization servicesName-resolution servicesSecret-management servicesKey-management servicesLogging servicesMonitoring servicesMessaging servicesData servicesRepository servicesPolicy-enforcement servicesService-discovery servicesConfiguration-distribution servicesA Platform Service may operate:

As a Containerized WorkloadOn a Virtual MachineThrough a provider-managed serviceAs a component of a Kubernetes ClusterThrough another platform-specific realizationPlatform Service deployment contributes to:

Consistent shared platform capabilitiesRepeatable platform establishmentAutomated service deploymentControlled service configurationReproducibilityProvenanceTraceability

Applies To

This requirement applies to:

configurationsPlatform Servicedeployment workflowsInfrastructure EnvironmentsInfrastructure ConfigurationsContainer PlatformsKubernetes ClustersVirtual MachinesProvider ImplementationsCI/CD Pipelines

Verification

Verification SHALL confirm that Crucible executes a deployment operation for an identified Platform ServiceVerification SHALL confirm that the deployment operation targets an identified Infrastructure EnvironmentVerification SHALL confirm that the identified Platform Service exists in the target Infrastructure Environment after successful deploymentVerification may include:

deployment testingTarget-environment inspectionService-state inspectionPlatform-interface inspectionProvider-interface inspectionDeployment-output inspectionDeployment-log inspectionAutomated CI/CD Pipeline testingThe verification record SHALL identify:

The deployed Platform ServiceThe target Infrastructure EnvironmentThe deployment operationThe deployment resultThe observed Platform Service stateThe generated Evidence

Outgoing Traceability

This requirement realizes:

This requirement relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference FR-DEP-005.

Incoming Traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list.

Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship.

ConOps Relationship

The Crucible Concept of Operations describes automated infrastructure and platform deployment through a Phase 1 CI/CD Pipeline.

FR-DEP-005 establishes the required behavior for deploying an identified Platform Service to a target Infrastructure Environment.

Requirements governing infrastructure resources, Virtual Machines, Kubernetes Clusters, Containerized Workloads, rollback, and validation define separate behavior.

Delivery Phase

Phase 1

Implementation Status

Not Assessed

Implementation status requires verification that Crucible deploys an identified Platform Service to a target Infrastructure Environment.

Requirement Status

Draft

The source System Requirements Specification identifies Version 1.1 as a draft.

Notes for Editors

This requirements page should retain the stable requirement identifier 'FR-DEP-005'.

Changes to the Statement SHALL preserve the approved intent of the source requirement.

The Source Statement should preserve the original wording from the controlling System Requirements Specification.

The Statement should remain limited to the deployment of an identified Platform Service.

Requirements for service activation, availability, scaling, monitoring, rollback, validation, compliance assessment, and retirement should remain in their applicable requirement pages.

Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.

Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-005#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.