Crucible SHALL provide a Command-Line Interface (CLI) for invoking Crucible operations.
This requirement derives from:
The Original Requirement requires the web-based interface to use the same engine and command-line capabilities as the primary command-line interface.[C1]
FR-UI-002:
FR-UI-001 separately governs operations exposed through both interfaces.
FR-UI-003 separately requires the Web-Based User Interface.
A Command-Line Interface (CLI) provides a text-based interface through which people and automated processes can invoke Crucible operations.
The Command-Line Interface supports:
Providing a Command-Line Interface allows Crucible operations to participate in repeatable and automated processes without requiring interaction through a graphical interface.
This requirement establishes a Command-Line Interface without prescribing:
Separate requirements, architecture specifications, interface specifications, security requirements, and command profiles govern those subjects.
This requirement applies to:
Verification confirms that:
The following pages reference this requirement:
Implemented and Verified
Review and approve FR-UI-002 as a leaf requirement.
Confirm which Crucible operations the Command-Line Interface must expose.
Determine whether separate requirements define command syntax, input conventions, output formats, exit status conventions, and error reporting.
Confirm whether the controlling source requires the Command-Line Interface to remain the primary Crucible interface.
This requirement page retains the stable requirement identifier FR-UI-002.
This page is a leaf requirement page and omits a trailing :start from its namespace.
The Statement uses the following controlling Terms and Definitions entries:
The Statement addresses provision of a Command-Line Interface for invoking Crucible operations.
FR-UI-001 governs operations exposed through both the Command-Line Interface and the Web-Based User Interface (Web UI).
FR-UI-003 governs provision of the Web-Based User Interface.
The term invoke does not require every operation to complete synchronously. An invoked operation can return an immediate result, initiate a longer-running activity, or provide an identifier through which its status and result can be obtained.
Do not add particular commands, syntax, options, arguments, output formats, shells, operating systems, or operation sets unless the controlling requirement changes through an approved requirements process.
To reference this requirement Statement from another wiki page, insert:
{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-11-management-interfaces:fr-ui-002#Statement&noheader&nofooter&noeditbtn}}
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.