9.1 Shared Interface Operations

Go to 9. Crucible Interfaces

Shared Interface Operations provide a consistent set of Crucible operations through the supported user interfaces.

The Command-Line Interface (CLI) and Web-Based User Interface can present an operation differently, but both interfaces invoke the same underlying Crucible capability.

A shared operation retains the same operational meaning regardless of the interface used to invoke it.

The interfaces preserve a consistent relationship among:

• The requested operation
• The subject of the operation
• The supplied inputs
• The applicable parameters
• The authorization decision
• The Crucible capability invoked
• The operation status
• The operation result

An interface does not redefine the behavior required by the applicable operational or functional requirement.

Each supported interface accepts the inputs and parameters required by the underlying Crucible operation.

The presentation of those inputs can differ between interfaces.

For example:

• The CLI can accept an option, argument, or referenced input file
• The Web-Based User Interface can accept the same information through a form, selection control, or uploaded input

The interface-specific presentation does not change the meaning of the supplied value.

Shared Interface Operations remain subject to the same authorization and Security Domain controls.

An interface does not permit an actor to:

• Invoke an unauthorized operation
• Access an unauthorized resource
• Bypass an information-handling rule
• Override a Security Domain restriction
• Avoid an applicable validation or approval step

The applicable access-control decision governs the operation regardless of the interface used.

Each supported interface presents the status of the invoked operation in a form appropriate to that interface.

The status can identify whether the operation:

• Has been accepted
• Is in progress
• Has completed
• Has failed
• Cannot proceed
• Requires additional input

The interface presentation can differ, but the underlying operation status remains the same.

Each supported interface provides access to the result produced by the underlying Crucible operation.

The result can include:

• The operation outcome
• Identifiers assigned during the operation
• Produced artifacts
• Assessment or validation results
• Failure information
• References to related Crucible records

The CLI can present a result as terminal output or a referenced artifact. The Web-Based User Interface can present the same result through a visual display or downloadable artifact.

The interface does not change the meaning of the operation result.

The CLI and Web-Based User Interface can differ in:

• Navigation
• Command syntax
• Input collection
• Help and guidance
• Progress presentation
• Error presentation
• Result presentation

These differences support the interaction model of each interface. They do not create separate operational capabilities or separate lifecycle semantics.

A Shared Interface Operation preserves:

• The identity of the requested operation
• The supplied inputs and parameters
• The applicable authorization decision
• The invoked Crucible capability
• The operation status
• The resulting output
• The relationship between the request and result

The CLI and Web-Based User Interface can expose these elements differently while preserving their common operational meaning.

The linked leaf requirement page remains the canonical source.