OR-001a — Developer Operations

Go to OR-001 — Operation by Identified User Categories

Statement

Crucible SHALL execute each Crucible operation assigned to a Developer by the applicable operational scenario in response to the Developer interaction specified for that operation.

Derived From

This requirement derives from:

The Original Requirement states:

The system SHALL support operation by: Developers DevSecOps Engineers Platform Engineers System Administrators Security Engineers Compliance Officers[C1]

OR-001a preserves the intent that Developers participate in Crucible operation by requiring Crucible to execute each operation assigned to a Developer by the applicable operational scenario.

The separate requirements derived from OR-001 address:

Assessment

The Original Requirement identifies Developers as a category of users that participates in Crucible operation but does not identify:

The Crucible operations assigned to a DeveloperThe operational scenarios in which a Developer participatesThe Developer interaction that causes Crucible to execute an assigned operationThe inputs supplied by a DeveloperThe outputs presented to a DeveloperThe completion condition for an operation assigned to a DeveloperThe Evidence required to demonstrate successful operationThe distinction between Developer participation and participation by another identified user categoryThe phrase support operation by Developers does not identify an observable Crucible behavior.

OR-001a:

Identifies Crucible as the responsible actorIdentifies the Developer as the applicable user categoryRequires the applicable operational scenario to assign the operation to a DeveloperRequires the applicable operational scenario to specify the Developer interactionRequires Crucible to execute the assigned operation in response to the specified Developer interactionSeparates Developer operation from operation by the other identified user categoriesOR-001a does not establish:

That every Crucible operation applies to a DeveloperThat every Developer performs the same operationsThat every operational scenario assigns the same operations to a DeveloperA role-assignment mechanismA role-based authorization modelA particular access-control modelA particular user interfaceA particular interaction mechanismPermissions not established by another controlling requirement

Rationale

Separating Developer operation from operation by the other identified user categories provides an independently testable and traceable requirement.

The applicable operational scenario establishes the context needed to determine:

Which Crucible operation applies to a DeveloperWhich Developer interaction applies to the operationWhich inputs the Developer suppliesWhich outputs the Developer receives or reviewsWhich completion condition appliesWhich failures and exceptions applyWhich Evidence demonstrates execution of the operationThe Crucible Concept of Operations [C2] identifies Build, Capture, and Deploy as high-level Crucible operations.

The Concept of Operations also addresses:

Phase 1 command-line operationCI/CD pipeline integrationImage-layer baseline compositionInfrastructure baseline compositionMachine Image constructionDependency captureCompliance-finding captureInfrastructure deploymentConnected-to-disconnected transferOffline package-repository populationCompliance Evidence generationPhase 2 web managementStrategic native executionThe applicable operational scenario determines which of these operations and interactions apply to a Developer.

This requirement does not allocate every identified Crucible operation to a Developer.

This requirement does not define the detailed behavior of Build, Capture, Deploy, or another Crucible operation. Separate functional and operational requirements define those behaviors.

Applies To

This requirement applies to:

DevelopersApplicable operational scenariosCrucible operations assigned to DevelopersDeveloper interactions specified by applicable operational scenariosDeveloper inputsOperation statusOperation resultsOperation failuresOperation exceptionsBuild operations assigned to DevelopersCapture operations assigned to DevelopersDeploy operations assigned to DevelopersPhase 1 command-line operationCI/CD pipeline integrationPhase 2 web managementStrategic native executionConnected EnvironmentsDisconnected EnvironmentsAir-Gapped EnvironmentsArtifactsEvidenceProvenanceTraceability

Verification

Verification confirms that:

# The applicable operational scenario identifies the Developer
# The applicable operational scenario identifies each Crucible operation assigned to the Developer
# The applicable operational scenario identifies the Developer interaction associated with each assigned operation
# Crucible receives the specified Developer interaction
# Crucible executes the operation assigned to the Developer
# The executed operation corresponds to the operation identified by the applicable operational scenario
# Crucible produces the status, result, failure, exception, Artifact, Evidence, or other output specified for the operation
# The verification record preserves Traceability between the applicable operational scenario, Developer interaction, and executed operation

Verification includes:

Applicable operational scenario inspectionDeveloper identification inspectionAssigned-operation inspectionDeveloper-interaction inspectionDeveloper-input inspectionExecution of each operation assigned to the DeveloperOperation-status inspectionOperation-result inspectionFailure-condition testingException-condition testingArtifact inspectionEvidence inspectionProvenance inspectionTraceability inspectionThe verification record identifies:

# The applicable operational scenario
# The Developer
# The assigned Crucible operation
# The specified Developer interaction
# Each Developer input
# The executed Crucible operation
# The operation start condition
# The operation completion condition
# Each generated status or result
# Each observed failure or exception
# Each generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]]
# The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
# The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
# The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

Requirements Realized By

This requirement is realized by:

Requirements that define Build operations assigned to DevelopersRequirements that define Capture operations assigned to DevelopersRequirements that define Deploy operations assigned to DevelopersRequirements that define Phase 1 command-line interactionsRequirements that define CI/CD pipeline interactionsRequirements that define Developer inputsRequirements that define operation status and resultsRequirements that define operation failures and exceptionsRequirements that define generated Artifacts and Evidence

Related Architecture Sections

Referenced By

The following pages reference this requirement:

Delivery Phase

Phase 1 and subsequent phases

Implementation Status

Not Assessed

Implementation status requires verification that the current Crucible implementation executes each Crucible operation assigned to a Developer by the applicable operational scenario in response to the specified Developer interaction.

Requirement Status

Draft

This requirement derives from OR-001 in the Crucible System Requirements Specification, Version 1.1 Draft.

Notes for Editors

This requirement page should retain the stable requirement identifier OR-001a.

This page is a leaf requirement page and omits a trailing :start from its namespace.

Changes to the Statement should preserve:

Crucible as the responsible actorThe Developer as the applicable user categoryAssignment of the operation by the applicable operational scenarioIdentification of the Developer interaction by the applicable operational scenarioExecution of the assigned operation by CrucibleThe requirement owner should confirm:

Which Crucible operations apply to DevelopersWhich operational scenarios assign those operationsWhich Developer interaction applies to each operationWhich Developer inputs applyWhich outputs applyWhich existing requirements realize each assigned operationWhich uncovered interactions require additional atomic requirementsMaterial changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records.

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

{{section>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:or-001a#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.