The Web-Based User Interface provides a browser-based interface for invoking supported Crucible operations.
The Web-Based User Interface exposes the Shared Interface Operations described in 9.1 Shared Interface Operations through visual controls appropriate to the implemented interface.
The Web-Based User Interface does not establish separate lifecycle semantics or independent Crucible capabilities. Each user action invokes an underlying operation governed by its applicable requirements.
An authorized user selects a supported Crucible operation through the Web-Based User Interface.
The interface can present operations through:
The available operations reflect the capabilities exposed by the implemented interface and permitted by the applicable access controls.
The Web-Based User Interface collects the information required by the selected Crucible operation.
Inputs can include:
The visual presentation of an input does not change the meaning of the value supplied to the underlying operation.
The Web-Based User Interface validates required inputs before submitting the operation.
Input validation can identify:
Successful interface validation establishes that the request contains the information required for submission. It does not establish that the operation is authorized or that the operation will complete successfully.
Web-Based User Interface operations remain subject to the same identity, access, Security Domain, and information-handling controls that govern the underlying Crucible capability.
The Web-Based User Interface does not permit a user to:
Access to the Web-Based User Interface does not imply access to every Crucible operation.
The Web-Based User Interface presents the status of an invoked operation through an interface-appropriate representation.
The status can indicate whether the operation:
The interface preserves the distinction between successful submission of a request and successful completion of the underlying Crucible operation.
The Web-Based User Interface provides access to the result produced by the underlying Crucible operation.
A result can include:
The interface can present the result directly or provide access to a separately produced artifact.
The Web-Based User Interface does not change the meaning of the result produced by the underlying operation.
When a request or operation cannot complete, the Web-Based User Interface presents information describing the observed condition.
Error information can identify:
The interface does not present a failed or incomplete operation as successful.
The Web-Based User Interface and the Command-Line Interface provide different interaction models for supported Shared Interface Operations.
The interfaces can differ in:
Those differences do not change the meaning, authorization, inputs, status, or result of the underlying Crucible operation.
A Web-Based User Interface interaction preserves the relationship among:
The underlying Crucible capability determines the operational result. The Web-Based User Interface provides the browser-based means of requesting and presenting that result.
| Requirement | Statement |
|---|---|
| FR-UI-003 — Web-Based User Interface |
Crucible SHALL provide a Web-Based User Interface (Web UI) for invoking Crucible operations and observing their results. |
The linked leaf requirement page remains the canonical source.
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.