====== 9. Crucible Interfaces ======

[[dido:02-crusible:start|Go to Crucible]]

[[dido:99_annexes:annex-b-terms-and-definitions:c: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 Operations
  * A [[dido:99_annexes:annex-b-terms-and-definitions:c:cli|Command-Line Interface (CLI)]]
  * A [[dido:99_annexes:annex-b-terms-and-definitions:w:web_ui|Web-Based User Interface]]

The 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 operation
  * The supplied inputs and parameters
  * The applicable authorization controls
  * The Crucible capability invoked
  * The operation status
  * The operation result

An 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 terminal
  * A remote terminal session
  * An administrative workstation
  * Another environment in which the approved CLI implementation is available

The 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:

  * Presentation
  * Navigation
  * Input collection
  * Result presentation
  * Help and guidance
  * Interaction sequence

Those 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 operation
  * Override Security Domain restrictions
  * Change the meaning of a lifecycle operation
  * Replace the applicable provider implementation
  * Establish new operational capabilities
  * Grant Accreditation, Operational Approval, or an Authority to Operate

The applicable Crucible capability and its requirements determine the behavior performed after an interface accepts an authorized request.

===== Contents =====

{{indexmenu>dido:02-crusible:09-crucible-interfaces#1|js navbar nocookie maxjs#2 id#crucible_interfaces_nav}}

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

The child pages describe only the interface behavior supported by the applicable canonical leaf requirements in [[dido:02-crusible:99-annexes:annex-c-requirements:start|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