OR-004 — Concurrent Environment Deployment and Management

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

The Original Requirement identifies concurrent deployment and management of multiple environments but does not express independently testable behaviors.

The following findings apply:

  • The system does not use the defined system name Crucible
  • Support is a weak verb that does not identify observable behavior
  • Deployment and management combines two independently testable behaviors
  • Multiple environments does not specify the minimum number of environments
  • Simultaneously does not clearly distinguish concurrent activity from sequential activity

The decomposition replaces support with the observable verbs deploy and manage, defines multiple as two or more, and replaces simultaneously with concurrently.

The decomposition separates:

  • Concurrent deployment of two or more Infrastructure Environments
  • Concurrent management of two or more Infrastructure Environments

The Original Requirement is decomposed into the following proposed replacement requirements:

Review and approve the decomposition of OR-004 into OR-004a and OR-004b.

Confirm that OR-004a and OR-004b preserve the complete approved intent of OR-004.

Determine whether OR-004a and OR-004b supersede OR-004.


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 page retains the stable parent requirement identifier OR-004.

This page is a non-leaf requirement page and retains a trailing :start in its namespace.

The child requirements are leaf requirement pages and omit a trailing :start from their namespaces.

The proposed child Statements should preserve the following intent:

  • OR-004a requires Crucible to concurrently deploy two or more Infrastructure Environments
  • OR-004b requires Crucible to concurrently manage two or more Infrastructure Environments

The explicit child links may be removed after the child requirement pages are finalized because the indexmenu displays the pages within the OR-004 namespace.

The child requirements do not introduce separate obligations for environment identity, Operational Lifecycle State, configuration, resource, operation, or record association. Separate requirements should define those obligations when supported by the source material.

The Original Requirement should not be marked as superseded until the requirement owner approves both child requirements and confirms that they collectively preserve its complete intent.


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

  • dido/02-crusible/99-annexes/annex-c-requirements/02-operational-requirements/or-004/start.txt
  • Last modified: 2026/07/23 11:24
  • by nick_dido