Table of Contents

FR-AG-002 — Artifact Export Packages

Go to Crucible Air-Gapped Operations Requirements

Statement

Crucible SHALL create Transfer Bundles for export.

Derived From

This requirement derives from:

The Original Requirement states:

The system shall support artifact export packages.[C1]

FR-AG-002:

No other substantive normalization is required.

Rationale

A Transfer Bundle provides a controlled package for exporting Artifacts and related information from one environment for transfer to another environment.

A Transfer Bundle can contain:

This requirement establishes creation of Transfer Bundles for export without prescribing:

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

Applies To

This requirement applies to:

Verification

Verification confirms that:

  1. One or more Artifacts are selected for export
  2. Crucible creates a Transfer Bundle for the tested export
  3. The created Transfer Bundle contains or references the selected Artifacts
  4. The resulting Transfer Bundle can be identified as the output of the tested export-package operation

Referenced By

The following pages reference this requirement:

Implementation Status

Implemented and Verified

Requirement Status

Review and approve FR-AG-002 as a leaf requirement.


Issues

Determine whether separate requirements define the minimum required contents and metadata of a Transfer Bundle.

Determine whether export and import must preserve one Transfer Bundle identity or may create distinct package records.


Notes for Editors

This requirement page retains the stable requirement identifier FR-AG-002.

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

The source phrase artifact export packages maps to the defined Transfer Bundle concept.

The Statement preserves the approved source intent by requiring Crucible to create Transfer Bundles for export.

Do not introduce separate Artifact Export Package and Artifact Import Package concepts unless the controlling architecture defines different package structures or identities.

Do not add Transfer Authorization, transfer, integrity verification, import, approval, promotion, deployment, or cross-environment identity-preservation obligations unless the controlling requirement changes through an approved requirements process.

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

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

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