1.4.1 Why a Wiki

Go to 1.4 About the Wiki

Crucible includes operational concepts, controlled terminology, requirements, architecture, lifecycle activities, and implementation guidance used by several different audiences. These audiences do not always read the material in the same order or require the same level of detail.

A traditional linear document requires a reader to open the complete document, locate the appropriate chapter, and search within that chapter for the relevant subject. As the document grows, this process becomes slower and makes precise references more difficult.

The wiki assigns a distinct page and URI to each major subject. A reader can therefore access, bookmark, or reference the specific page needed without opening and searching a long document. Pages can also link directly to specific sections within another page.

This structure allows requirements, architecture pages, issues, review comments, emails, and external documents to reference precise content rather than an entire publication.

The wiki also supports canonical content. A controlled term, requirement, or other authoritative subject can reside on one maintained page and be linked or transcluded wherever the content applies. This reduces duplication and prevents independently maintained copies from becoming inconsistent.

The wiki strengthens Traceability by allowing pages to link directly to the requirements, controlled terms, architecture elements, operational scenarios, verification criteria, implementation records, and Evidence that support or depend on their content.

These links allow readers to follow relationships in both directions. A requirement can identify its source, rationale, verification criteria, related operational content, and implementation status, while backlinks can identify the pages that reference the requirement. This makes the relationships among intent, requirements, architecture, implementation, verification, and Evidence visible and navigable.

The wiki supports:

• Direct access to individual subjects through page and section URIs
• Precise references from requirements, architecture pages, issues, reviews, emails, and external documents
• Traceability among operational concepts, requirements, architecture, implementation, verification, and Evidence
• Backlinks that identify pages referring to a subject
• Role-specific navigation for executives, engineers, operators, auditors, and other stakeholders
• Stable links to controlled terms, requirements, operational concepts, and implementation guidance
• Reuse of canonical content without maintaining duplicate copies
• Independent review and maintenance of pages that change at different rates
• Expansion of the publication without requiring every reader to navigate an increasingly long linear document

The wiki remains a structured publication rather than an unorganized collection of pages. Numbered sections, the Table of Contents, parent and child navigation, controlled namespaces, and Annexes provide an ordered reading path comparable to a conventional document.

Readers can follow the publication from beginning to end or navigate directly to the page or section relevant to their responsibilities.