OR-001a — Developer Operations

Go to OR-001 — Operation by Identified User Categories

Statement

Crucible SHALL execute each Crucible operation allocated to a Developer by the applicable Operational Scenario upon receipt of the initiating input specified by that 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 execute each operation allocated to a Developer by the applicable Operational Scenario.

The separate requirements derived from OR-001 address:

Assessment

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

The meaning of DeveloperThe characteristics that distinguish a Developer from the other listed user categoriesThe Crucible operations allocated to a DeveloperThe Operational Scenarios in which a Developer participatesThe initiating input associated with each allocated operationThe interfaces through which a Developer provides the initiating inputThe inputs required for each operationThe outputs produced for each operationThe completion conditions for each operationThe failure and exception conditions for each operationThe Evidence required to demonstrate execution of each operationThe phrase support operation by Developers does not identify an observable Crucible behavior.

OR-001a:

Identifies Crucible as the responsible actorSeparates Developer participation from participation by the other listed user categoriesRequires the applicable Operational Scenario to allocate the Crucible operation to a DeveloperRequires the applicable Operational Scenario to identify the initiating inputRequires Crucible to execute the allocated operation upon receipt of the specified initiating inputOR-001a does not establish:

A definition of DeveloperThat every Crucible operation applies to a DeveloperThat every Developer participates in the same Crucible operationsThat every Operational Scenario allocates the same operations to a DeveloperA role-assignment mechanismA role-based authorization modelA particular access-control modelA particular interfaceA particular form of initiating inputPermissions not established by another controlling requirement

Rationale

Separating Developer operations from operations associated with the other listed user categories provides an independently testable and traceable requirement.

The applicable Operational Scenario provides the context required to determine:

Which Crucible operations apply to a DeveloperWhich initiating input applies to each operationWhich interfaces receive the initiating inputWhich additional inputs applyWhich outputs Crucible producesWhich completion conditions applyWhich failure and exception conditions applyWhich Artifacts and Evidence demonstrate execution of the operationThe Crucible Concept of Operations [C2] identifies Build, Capture, and Deploy as high-level Crucible operations.

The Concept of Operations does not identify:

Which of these operations apply to a DeveloperWhether additional Crucible operations apply to a DeveloperHow a Developer participates in each operationWhich initiating input applies to each operationThe applicable Operational Scenario must identify these allocations and interactions.

This requirement does not define the internal 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 allocated to DevelopersInitiating inputs specified for Developer operationsInterfaces that receive Developer inputsOperation statusOperation resultsOperation failuresOperation exceptionsArtifactsEvidenceProvenanceTraceability

Verification

Verification confirms that:

# The applicable Operational Scenario identifies the Developer
# The applicable Operational Scenario identifies each Crucible operation allocated to the Developer
# The applicable Operational Scenario identifies the initiating input for each allocated operation
# Crucible receives the initiating input specified for the allocated operation
# Crucible executes the operation allocated to the Developer
# The executed operation corresponds to the operation identified by the applicable Operational Scenario
# Crucible produces each status, result, failure indication, exception indication, Artifact, Evidence item, or other output specified for the operation
# The verification record preserves Traceability among the applicable Operational Scenario, the Developer, the initiating input, and the executed operation

Verification includes:

Inspection of the applicable Operational ScenarioInspection of the operation allocationInspection of the specified initiating inputSubmission of the specified initiating inputObservation of Crucible executionInspection of operation statusInspection of operation resultsFailure-condition testingException-condition testingArtifact inspectionEvidence inspectionProvenance inspectionTraceability inspectionThe verification record identifies:

# The applicable Operational Scenario
# The Developer
# The allocated Crucible operation
# The specified initiating input
# The interface that received the initiating 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

No realizing requirements have been identified.

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 executes each Crucible operation allocated to a Developer upon receipt of the initiating input specified by 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 categoryAllocation of the operation by the applicable Operational ScenarioIdentification of the initiating input by the applicable Operational ScenarioExecution of the allocated 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, requirements realization, 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.