9.1 Shared Interface Operations [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 9.1 Shared Interface Operations ======

[[dido:02-crusible:09-crucible-interfaces:start|Go to 9. Crucible Interfaces]]

Shared Interface Operations provide a consistent set of [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] operations through the supported user interfaces.

The [[dido:99_annexes:annex-b-terms-and-definitions:c:cli|Command-Line Interface (CLI)]] and [[dido:99_annexes:annex-b-terms-and-definitions:w:web_ui|Web-Based User Interface]] can present an operation differently, but both interfaces invoke the same underlying Crucible capability.

===== Shared Operational Meaning =====

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.

===== Shared Inputs and Parameters =====

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 Authorization Controls =====

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.

===== Shared Operation Status =====

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.

===== Shared Operation Results =====

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.

===== Interface-Specific Presentation =====

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.

===== Shared-Operation Result =====

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.

===== Requirements Addressed =====

^ Requirement ^ Statement ^
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-11-management-interfaces:fr-ui-001]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-11-management-interfaces:fr-ui-001#Statement&noheader&nofooter&noeditbtn}} |

The linked leaf requirement page remains the canonical source.

----

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