1.4.2 What the Wiki Contains

Go to 1.4 About the Wiki

The Crucible wiki contains the information needed to understand, specify, implement, assess, operate, maintain, and extend Crucible.

The content includes:

• Concept of Operations describing the operational purpose, context, actors, activities, information flows, environments, and expected outcomes of Crucible
• Mission Objectives identifying the organizational and operational outcomes that Crucible is expected to support
• Operational Requirements defining the capabilities and conditions required to support Crucible operations
• Functional Requirements defining the behavior that Crucible implementations SHALL provide
• Architecture Content describing the major components, responsibilities, interfaces, relationships, and extension points that realize the requirements
• Operational Lifecycles and Workflows describing how software, Baselines, Machine Images, infrastructure, dependencies, compliance results, and Evidence move through controlled activities
• Connected, Disconnected, and Air-Gapped Operations describing how Crucible supports Connected Environments, Disconnected Environments, and Air-Gapped Environments
• Implementation Guidance describing approved approaches, conventions, examples, and procedures for implementing and operating Crucible capabilities
• Interface Guidance describing the Command-Line Interface (CLI), Web-Based User Interface (Web UI), provider interfaces, and other integration points
• Controlled Terms and Definitions establishing the vocabulary used consistently throughout the wiki
• Traceability Information linking operational concepts, requirements, architecture, implementation, verification, and Evidence
• Implementation Status and Issues recording the current state of documented capabilities, unresolved matters, and editorial work
• Annexes containing requirements, controlled terminology, and other supporting material shared across the Crucible documentation

The wiki separates these content types so readers can navigate directly to the information relevant to their responsibilities. Links among the pages preserve their relationships and allow readers to move from an operational concept to its supporting requirements, architecture, implementation guidance, verification information, and Evidence.