====== FR-AG-001 — Disconnected Deployment Operations ======

[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:start|Go to Crucible Air-Gapped Operations Requirements]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL perform [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operations]] within [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]].

===== Derived From =====

This requirement derives from:

  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-AG-001

The Original Requirement states:

> //The system shall support disconnected deployment operations.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

FR-AG-001:

  * Replaces **The system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * Changes **shall** to the established uppercase normative form **SHALL**
  * Replaces the weak verb **support** with the observable behavior **perform**
  * Uses the defined [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operation]] concept
  * Uses the defined [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] concept

No other substantive normalization is required.

===== Rationale =====

A [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] operates without direct electronic communication with specified external systems, services, repositories, Providers, or networks.

Performing [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operations]] within such an environment requires the necessary software, [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency|Dependencies]], configuration information, credentials, repositories, and [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifacts]] to be locally available or otherwise accessible within the permitted operational boundary.

This requirement establishes disconnected deployment behavior without prescribing:

  * The Deployment Operation
  * The deployment subjects
  * The external systems from which the environment is disconnected
  * The transfer mechanism
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_capture|Dependency Capture]]
  * Artifact export
  * Artifact import
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_authorization|Transfer Authorization]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle_integrity|Transfer Bundle Integrity]]
  * Baseline synchronization
  * Air-gapped operation

Separate requirements, workflows, or policies define those subjects and behaviors.

===== Applies To =====

This requirement applies to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operations]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]]
  * Disconnected deployment workflows

===== Verification =====

Verification confirms that:

  - A [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] is selected for testing
  - A [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operation]] is selected for testing
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs the tested Deployment Operation within the Disconnected Environment
  - The Deployment Operation completes without relying on direct electronic communication prohibited by the defined disconnected boundary
  - The result of the tested Deployment Operation can be determined

===== Referenced By =====

The following pages reference this requirement:

{{backlinks>.#dido:02-crusible}}

===== Implementation Status =====

Implemented and Verified

===== Requirement Status =====

<todo>Review and approve FR-AG-001 as a leaf requirement.</todo>

----
===== Issues =====

<todo>Determine whether separate requirements identify the resources that must be locally available for disconnected Deployment Operations.</todo>

<todo>Determine whether separate requirements define the external communication boundaries used for each Disconnected Environment.</todo>

----
===== Notes for Editors =====

This requirement page retains the stable requirement identifier ''FR-AG-001''.

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

The Statement preserves the approved source intent by requiring Crucible to perform Deployment Operations within Disconnected Environments.

Do not add Artifact export, Artifact import, Dependency Capture, synchronization, Transfer Authorization, Transfer Bundle Integrity, specific deployment subjects, or Air-Gapped Environment obligations unless the controlling requirement changes through an approved requirements process.

A [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] can retain internal connectivity. This requirement does not equate disconnected operation with operation in an [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]].

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

<code dokuwiki>
{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:fr-ag-001#Statement&noheader&nofooter&noeditbtn}}
</code>

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>