OR-004b — Concurrent Environment Management

Crucible SHALL concurrently manage two or more Infrastructure Environments.

This requirement derives from:

The Original Requirement states:

The system SHALL support deployment and management of multiple environments simultaneously.[C1]

OR-004b replaces the weak phrase support management with the observable behavior manage, defines multiple as two or more, and expresses simultaneous management as concurrent management.

Organizations often operate more than one Infrastructure Environment during overlapping periods.

Concurrent management enables Crucible to perform management activity for one Infrastructure Environment without requiring management activity for another Infrastructure Environment to finish first.

This requirement establishes concurrent management capability without defining the specific management operations, maximum concurrency limit, or internal scheduling mechanism.

This requirement applies to:

Verification confirms that:

  1. At least two Infrastructure Environments are selected for management
  2. Crucible performs management activity for the selected Infrastructure Environments during overlapping time periods
  3. Management activity for one Infrastructure Environment does not require management activity for every other selected Infrastructure Environment to complete first
  4. Each tested Infrastructure Environment produces its own management result
  5. Completion or failure of one tested management operation does not prevent management of the other tested Infrastructure Environment unless a documented shared dependency requires that behavior

Implemented and Verified.

Assess whether the current Crucible implementation concurrently manages two or more Infrastructure Environments.

Review and approve OR-004b as a leaf requirement derived from OR-004.


Define the management operations included within concurrent environment management.

Define the point at which an environment management operation begins for concurrency verification.

Define the point at which an environment management operation ends for concurrency verification.

Determine whether a minimum overlap duration is required to demonstrate concurrent management.

Determine whether requirements elsewhere define a supported concurrency limit greater than two Infrastructure Environments.

Determine whether requirements elsewhere define behavior when Crucible reaches the supported concurrency limit.


This requirement page retains the stable requirement identifier OR-004b.

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

OR-004b governs concurrent management of two or more Infrastructure Environments.

OR-004b does not govern:

  • Concurrent deployment of Infrastructure Environments
  • The management operations available for an Infrastructure Environment
  • The maximum number of concurrently managed Infrastructure Environments
  • Management scheduling or queuing mechanisms
  • Environment identity, Operational Lifecycle State, configuration, resource, operation, or record association
  • Isolation between Infrastructure Environments

Changes to the Statement should preserve:

  • Crucible as the responsible actor
  • Concurrent management as the required behavior
  • Two or more Infrastructure Environments as the minimum tested quantity

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

{{section>dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-004:or-004b#Statement&noheader&nofooter&noeditbtn}}

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

  • dido/02-crusible/99-annexes/annex-c-requirements/02-operational-requirements/or-004/or-004b.txt
  • Last modified: 2026/07/30 05:35
  • by nick_dido