C.2 Operational Requirements

Go to Crucible Requirements

The Operational Requirements define the actors, deployment environments, operational classifications, concurrency needs, and management scope within which Crucible operates.

These requirements establish the operational conditions that constrain and guide the functional, security, reliability, performance, maintainability, data management, and interoperability requirements.

Contents

Notes for Editors

The individual requirement pages should retain the stable identifiers `OR-001` through `OR-005`.

The source statements should preserve the wording from the controlling System Requirements Specification.

Normalized statements should replace weak verbs such as support with direct, testable behavior.

Incoming traceability should use the wiki Backlinks function rather than a manually maintained list.

Individual requirement links should omit a trailing `:start` when the requirement record is a leaf page.

Do not rename requirement pages after external citation unless a redirect or move plan is in place.

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.