OR-001a — Developer Operations

Go to OR-001 — Operation by Identified User Categories

Statement

Crucible SHALL perform each Crucible operation invoked by a Developer in accordance with the applicable operational scenario.

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 perform each operation invoked by a Developer in accordance with the applicable operational scenario.

The separate requirements derived from OR-001 address:

Rationale

The Original Requirement combines six independently testable user categories within one normative statement.

OR-001a separates Developer operations from operations associated with the other identified user categories. The separate requirement provides a stable identifier for verification and Traceability.

The applicable operational scenario identifies:

The Crucible operations available to a DeveloperThe conditions under which a Developer invokes each operationThe Controlled Inputs provided by a DeveloperThe status and results presented to a DeveloperThe completion conditions applicable to each operationThe failure and exception conditions applicable to each operationThe Artifacts and Evidence produced by each operationThe Crucible Concept of Operations [C2] identifies Build, Capture, and Deploy as high-level Crucible operations.

OR-001a does not establish that:

Every Crucible operation applies to a DeveloperEvery Developer invokes the same Crucible operationsEvery operational scenario identifies the same Developer operationsDeveloper constitutes an Operational RoleA particular role-assignment mechanism appliesA particular authorization or access-control model appliesA particular interface supports Developer operationsSeparate operational and functional requirements define the detailed behavior, inputs, outputs, completion conditions, failures, exceptions, Artifacts, and Evidence associated with each Crucible operation.

Applies To

This requirement applies to:

DevelopersOperational scenarios applicable to DevelopersCrucible operations identified for DevelopersDeveloper invocation of Crucible operationsControlled InputsOperation statusOperation resultsOperation failuresOperation exceptionsArtifactsEvidenceProvenanceTraceabilityConnected EnvironmentsDisconnected EnvironmentsAir-Gapped Environments

Verification

Verification confirms that:

The applicable operational scenario identifies each Crucible operation that a Developer can invokeThe applicable operational scenario identifies the conditions under which the Developer can invoke each operationThe Developer can invoke each identified Crucible operation under the specified conditionsCrucible performs each operation invoked by the DeveloperThe performed operation corresponds to the operation invoked by the DeveloperCrucible produces each status, result, failure indication, exception indication, Artifact, Evidence item, or other output specified for the operationThe verification record preserves Traceability among the applicable operational scenario, the Developer invocation, and the performed Crucible operationVerification includes:

Inspection of the applicable operational scenarioInspection of the Crucible operations identified for the DeveloperInspection of the invocation conditionsInvocation of each identified Crucible operationObservation of Crucible performance of each invoked operationComparison of each invoked operation with the corresponding performed operationInspection of operation status and resultsFailure-condition testingException-condition testingArtifact inspectionEvidence inspectionProvenance inspectionTraceability inspection

Related Architecture Sections

No related architecture sections have been identified.

Referenced By

The following pages reference this requirement:

Delivery Phase

To Be Determined

Implementation Status

Not Assessed

Implementation status requires verification that the current Crucible implementation performs each Crucible operation invoked by a Developer in accordance with the applicable operational scenario.

Requirement Status

Draft

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

Issues

The following unresolved issues affect this requirement:

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.

The parent OR-001 page is a non-leaf page and retains a trailing :start in its namespace.

Changes to the Statement should preserve:

as the responsible actorDeveloper as the applicable user categoryThe applicable operational scenario as the source of the operational contextInvocation of the operation by the DeveloperPerformance of the invoked operation by CrucibleThe unresolved meaning of Developer should remain recorded in the Issues section until an authoritative definition or classification resolves the issue.

Material changes should receive review and should update the verification criteria, related architecture sections, source records, and Issues section.

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.