9. Crucible Interfaces

Go to Crucible

Crucible provides interfaces through which authorized users and systems perform supported Crucible operations.

The interfaces expose a shared set of operations while allowing each interface to present those operations in a form appropriate to its users and operating context.

Crucible supports:

Shared Interface OperationsA Command-Line Interface (CLI)A Web-Based User InterfaceThe CLI and Web-Based User Interface provide different means of accessing supported Crucible operations. They do not establish separate lifecycle semantics or independent implementations of the underlying operational capabilities.

Shared Operations

Shared Interface Operations define the Crucible operations available through supported interfaces.

The shared operations provide a consistent relationship among:

The requested operationThe supplied inputs and parametersThe applicable authorization controlsThe Crucible capability invokedThe operation statusThe operation resultAn interface can present an operation differently without changing the meaning or required behavior of the underlying Crucible capability.

Command-Line Access

The CLI supports text-based interaction with Crucible.

The CLI can support authorized use from:

A local terminalA remote terminal sessionAn administrative workstationAnother environment in which the approved CLI implementation is availableThe CLI provides access only to operations supported by the applicable Crucible requirements. The presence of a CLI does not independently establish unattended execution, scripting, pipeline integration, or automation capabilities.

Web-Based Access

The Web-Based User Interface supports browser-based interaction with Crucible.

The Web-Based User Interface presents supported Crucible operations through visual controls, forms, status displays, and result displays appropriate to the implemented interface.

The Web-Based User Interface does not replace the authorization, validation, or lifecycle rules governing the underlying operation.

Consistent Operational Meaning

An operation retains the same operational meaning regardless of whether an authorized user invokes it through the CLI or the Web-Based User Interface.

The interfaces can differ in:

PresentationNavigationInput collectionResult presentationHelp and guidanceInteraction sequenceThose differences do not change the applicable requirements, controlled inputs, authorization decisions, operation results, or lifecycle relationships.

Interface Boundaries

Crucible interfaces provide access to supported capabilities. They do not independently:

Grant access to an unauthorized operationOverride Security Domain restrictionsChange the meaning of a lifecycle operationReplace the applicable provider implementationEstablish new operational capabilitiesGrant Accreditation, Operational Approval, or an Authority to OperateThe applicable Crucible capability and its requirements determine the behavior performed after an interface accepts an authorized request.

Contents

Notes for Editors

The child pages describe only the interface behavior supported by the applicable canonical leaf requirements in Annex C: Requirements.

The canonical Interface Requirements remain under the existing requirement namespace:

```text dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-11-management-interfaces