====== FR-BAS-003 — Process Predeployment and Postdeployment Steps ======

[[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-09-baseline-composition-and-workspace:start|Go to C.3.9 Baseline Composition and Workspace]]

===== Statement =====

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL process predeployment and postdeployment steps.

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

This requirement derives from:

  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-BAS-003

The Original Requirement states:

> //The system shall process predeployment and postdeployment steps.//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]

FR-BAS-003:

  * 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**
  * Retains the direct behavior **process**
  * Retains both predeployment and postdeployment steps as source-defined subjects

No other substantive normalization is required.

===== Rationale =====

Predeployment steps perform activities required before a [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operation]] begins.

Postdeployment steps perform activities required after a Deployment Operation completes.

These steps allow a [[dido:99_annexes:annex-b-terms-and-definitions:w:workspace|Workspace]] execution to coordinate activities that occur immediately before and after deployment without embedding those activities into the Deployment Operation itself.

Predeployment steps can include:

  * Preparing deployment inputs
  * Evaluating prerequisites
  * Resolving Workspace content
  * Generating configuration
  * Preparing credentials or access information
  * Evaluating deployment conditions

Postdeployment steps can include:

  * Collecting deployment results
  * Recording deployment status
  * Performing cleanup
  * Generating [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]]
  * Initiating a [[dido:99_annexes:annex-b-terms-and-definitions:v:validation_operation|Validation Operation]]
  * Publishing execution results

This requirement establishes processing of predeployment and postdeployment steps without prescribing:

  * Particular predeployment steps
  * Particular postdeployment steps
  * A required number of steps
  * A step definition format
  * Step ordering beyond their relationship to deployment
  * A step execution engine
  * A scripting language
  * A particular [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operation]]
  * A particular [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Target]]
  * Failure-handling behavior
  * Rollback behavior
  * Validation behavior

Separate requirements, architecture specifications, Workflow definitions, and deployment profiles govern those subjects and behaviors.

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

This requirement applies to:

  * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
  * Predeployment steps
  * Postdeployment steps
  * [[dido:99_annexes:annex-b-terms-and-definitions:w:workspace|Workspace]] execution
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operations]]

===== Verification =====

Verification confirms that:

  - A Workspace execution containing at least one predeployment step and at least one postdeployment step is selected for testing
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] processes the selected predeployment step before the associated [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operation]]
  - Crucible processes the associated Deployment Operation
  - Crucible processes the selected postdeployment step after the associated Deployment Operation
  - The result of each processed step can be identified
  - The observed execution order distinguishes the predeployment and postdeployment steps

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

The following pages reference this requirement:

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

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

Implemented and Verified

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

<todo>Review and approve FR-BAS-003 as a leaf requirement.</todo>

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

<todo>Determine whether Predeployment Step and Postdeployment Step require controlled definitions in the shared Terms and Definitions corpus.</todo>

<todo>Determine whether separate requirements define the representation, ordering, inputs, outputs, and status of deployment-related steps.</todo>

<todo>Determine whether separate requirements govern step failure handling, retry behavior, rollback, and continuation.</todo>

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

This requirement page retains the stable requirement identifier ''FR-BAS-003''.

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

The Statement addresses processing of both predeployment and postdeployment steps.

Predeployment steps execute before the associated [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operation]]. Postdeployment steps execute after the associated Deployment Operation.

FR-BAS-001 governs consumption of Baseline Repositories from a Workspace.

FR-BAS-002 governs composition of selected Baselines.

FR-BAS-004 governs noninteractive Workspace execution.

Do not add particular deployment-related steps, execution engines, scripting languages, ordering rules, failure-handling behavior, rollback behavior, or validation obligations unless the controlling requirement changes through an approved requirements process.

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-09-baseline-composition-and-workspace:fr-bas-003#Statement&noheader&nofooter&noeditbtn}}
</code>

----

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