OR-001b — DevSecOps Engineer Operations

Go to OR-001 — Operation by Identified User Categories

Statement

Crucible SHALL perform each Crucible operation invoked by a DevSecOps Engineer under the conditions specified by the 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-001b preserves the intent that DevSecOps Engineers participate in Crucible operation by requiring Crucible to perform each operation invoked by a DevSecOps Engineer under the conditions specified by the operational scenario.

The separate requirements derived from OR-001 address:

Rationale

DevSecOps Engineers require access to the Crucible operations assigned to them by the operational scenario.

This requirement ensures that Crucible performs each operation invoked by a DevSecOps Engineer under the conditions defined for that operation.

Separating DevSecOps Engineer operations from the operations associated with other user categories supports independent verification, Traceability, and determination of whether Crucible satisfies the operational needs assigned to DevSecOps Engineers.

Without this requirement, Crucible could perform operations for other user categories while failing to perform the operations required by DevSecOps Engineers.

Applies To

This requirement applies to:

DevSecOps EngineersOperational scenarios that identify DevSecOps Engineer operationsCrucible operations identified for DevSecOps EngineersDevSecOps Engineer invocation of Crucible operationsControlled InputsOperation statusOperation resultsOperation failuresOperation exceptionsArtifactsEvidenceProvenanceTraceabilityConnected EnvironmentsDisconnected EnvironmentsAir-Gapped Environments

Verification

Verification confirms that:

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

Referenced By

The following pages reference this requirement:

Delivery Phase

Implementation Status

Requirement Status

Issues

The following unresolved issues affect this requirement:

Notes for Editors

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

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 actorDevSecOps Engineer as the identified user categoryThe operational scenario as the source of the operating conditionsInvocation of the operation by the DevSecOps EngineerPerformance of the invoked operation by CrucibleThe unresolved meaning of DevSecOps Engineer 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, 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-001b#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.