OR-001a — Developer Operations

Go to OR-001 — Operation by Identified User Categories

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.

This requirement derives from:

• OR-001 — Operation by Identified User Categories

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:

• OR-001b — DevSecOps Engineer Operations
• OR-001c — Platform Engineer Operations
• OR-001d — System Administrator Operations
• OR-001e — Security Engineer Operations
• OR-001f — Compliance Officer Operations

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

• The meaning of Developer
• The characteristics that distinguish a Developer from the other listed user categories
• The Crucible operations allocated to a Developer
• The Operational Scenarios in which a Developer participates
• The initiating input associated with each allocated operation
• The interfaces through which a Developer provides the initiating input
• The inputs required for each operation
• The outputs produced for each operation
• The completion conditions for each operation
• The failure and exception conditions for each operation
• The Evidence required to demonstrate execution of each operation

The phrase support operation by Developers does not identify an observable Crucible behavior.

OR-001a:

• Identifies Crucible as the responsible actor
• Separates Developer participation from participation by the other listed user categories
• Requires the applicable Operational Scenario to allocate the Crucible operation to a Developer
• Requires the applicable Operational Scenario to identify the initiating input
• Requires Crucible to execute the allocated operation upon receipt of the specified initiating input

OR-001a does not establish:

• A definition of Developer
• That every Crucible operation applies to a Developer
• That every Developer participates in the same Crucible operations
• That every Operational Scenario allocates the same operations to a Developer
• A role-assignment mechanism
• A role-based authorization model
• A particular access-control model
• A particular interface
• A particular form of initiating input
• Permissions not established by another controlling requirement

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 Developer
• Which initiating input applies to each operation
• Which interfaces receive the initiating input
• Which additional inputs apply
• Which outputs Crucible produces
• Which completion conditions apply
• Which failure and exception conditions apply
• Which Artifacts and Evidence demonstrate execution of the operation

The 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 Developer
• Whether additional Crucible operations apply to a Developer
• How a Developer participates in each operation
• Which initiating input applies to each operation

The 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.

This requirement applies to:

• Crucible
• Developers
• Applicable Operational Scenarios
• Crucible operations allocated to Developers
• Initiating inputs specified for Developer operations
• Interfaces that receive Developer inputs
• Operation status
• Operation results
• Operation failures
• Operation exceptions
• Artifacts
• Evidence
• Provenance
• Traceability

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 Scenario
• Inspection of the operation allocation
• Inspection of the specified initiating input
• Submission of the specified initiating input
• Observation of Crucible execution
• Inspection of operation status
• Inspection of operation results
• Failure-condition testing
• Exception-condition testing
• Artifact inspection
• Evidence inspection
• Provenance inspection
• Traceability inspection

The 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]]

No realizing requirements have been identified.

No related architecture sections have been identified.

The following pages reference this requirement:

To Be Determined

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.

Draft

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

The following unresolved issues affect this requirement:

• [✓ nick_dido, 2026-07-21]Define **Developer** or reference an authoritative definition. Clarify whether Developer identifies a person, user category, organizational function, Operational Role, or another kind of actor.

• Distinguish **Developer** from **DevSecOps Engineer**, **Platform Engineer**, **System Administrator**, **Security Engineer**, and **Compliance Officer**.

• Determine whether **Operational Scenario** and **Crucible operation** require controlling Terms and Definitions entries.

• Identify the Crucible operations allocated to a Developer in each applicable Operational Scenario.

• Identify how a Developer participates in each allocated Crucible operation.

• Identify the initiating input, interface, additional inputs, outputs, completion conditions, failures, exceptions, Artifacts, and Evidence applicable to each Developer operation.

• Determine whether existing requirements already define each applicable Developer interaction and create additional atomic requirements only for confirmed coverage gaps.

• Identify the requirements that realize OR-001a.

• Identify the architecture sections related to OR-001a.

• Confirm the Delivery Phase for OR-001a.

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:

• Crucible as the responsible actor
• Developer as the applicable user category
• Allocation of the operation by the applicable Operational Scenario
• Identification of the initiating input by the applicable Operational Scenario
• Execution of the allocated operation by Crucible

The 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.