Differences

This shows you the differences between two versions of the page.

--- dido:02-crusible:01-introduction:01-03-intended-audience:start [2026/08/01 04:11] – removed - external edit (Unknown date) 127.0.0.1
+++ dido:02-crusible:01-introduction:01-03-intended-audience:start [2026/08/01 04:11] (current) – ↷ Page moved and renamed from dido:02-crusible:01-introduction:01-03-intended-audience to dido:02-crusible:01-introduction:01-03-intended-audience:start nick_dido
@@ Line 1: / Line 1: @@
+====== 1.3 Intended Audience ======
+[[dido:02-crusible:01-introduction:start|Go to 1. Introduction]]
+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] addresses the needs of organizations and stakeholders responsible for designing, funding, governing, building, assessing, authorizing, deploying, operating, maintaining, or auditing controlled software and [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]].
+The intended audience includes:
+  * **Executives** and **Organizational Leaders** who allocate resources, establish shared capabilities, evaluate organizational risk, and seek to reduce duplicated engineering and lifecycle costs across multiple products
+  * **Program Managers** and **Product Managers** who evaluate business value, implementation status, delivery risk, provider support, resource needs, and roadmap priorities
+  * **System Owners** who define the mission, operational, security, compliance, and lifecycle expectations for deployed systems and environments
+  * **Governance Bodies** that establish policies, controls, approval criteria, technical direction, and organizational responsibilities
+  * **[[dido:99_annexes:annex-b-terms-and-definitions:a:authorizing_authority|Authorizing Authorities]]** that evaluate risk, assessment results, and supporting [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] when making authorization or [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_approval|Operational Approval]] decisions
+  * **Enterprise Architects**, **System Architects**, and **Solution Architects** who define architectural boundaries, shared responsibilities, provider contracts, interfaces, and lifecycle controls
+  * **Platform Engineers** who construct and maintain reusable [[dido:99_annexes:annex-b-terms-and-definitions:p:platform|Platforms]], deployment environments, provider integrations, and automation services
+  * **DevSecOps Engineers** who integrate image construction, infrastructure deployment, [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_assessment|Compliance Assessment]], [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_capture|Dependency Capture]], and Evidence generation into automated workflows and pipelines
+  * **Software Factory Engineers** who establish and operate [[dido:99_annexes:annex-b-terms-and-definitions:s:software_factory|Software Factories]]
+  * **Infrastructure Engineers** who define and deploy resources through [[dido:99_annexes:annex-b-terms-and-definitions:i:iac|Infrastructure as Code (IaC)]]
+  * **Image Engineers** who construct, harden, sign, verify, promote, and maintain [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]]
+  * **Cybersecurity Engineers** who select security and compliance criteria, apply hardening, assess configurations, review [[dido:99_annexes:annex-b-terms-and-definitions:c:compliance_finding|Compliance Findings]], and evaluate security controls
+  * **Compliance Officers** who evaluate compliance criteria, assessment results, findings, exceptions, claims, and supporting Evidence
+  * **Auditors** who examine [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]], [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]], assessment results, lifecycle records, and [[dido:99_annexes:annex-b-terms-and-definitions:a:auditability|Auditability]]
+  * **Enclave Operators** who import, deploy, operate, and maintain approved content within [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]] and [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]]
+  * **Infrastructure Providers**, **Cloud Providers**, **Platform Providers**, **Image Providers**, and **Compliance Providers** that implement provider-specific behavior through controlled extension points
+  * **Application Teams** and **Product Teams** that consume approved images, infrastructure resources, platform services, Baselines, and deployment environments
+  * **Developers** and **Maintainers** who extend Crucible subsystems, providers, plugins, compliance integrations, or tooling interfaces
+Different audiences require different levels of detail.
+**Executives**, **Organizational Leaders**, **Program Managers**, **Product Managers**, **System Owners**, and **Governance Bodies** can focus on the purpose, scope, operational mission, organizational value, actors, responsibilities, operational outcomes, and authorization boundaries.
+**Architects** and **Engineers** can focus on the operational context, Baseline Composition, image construction, infrastructure deployment, provider abstraction, dependency capture, compliance operations, connected and disconnected workflows, and interface behavior.
+**Cybersecurity Engineers**, **Compliance Officers**, **Auditors**, and **Authorizing Authorities** can focus on Compliance Assessments, Compliance Findings, Evidence, Provenance, Traceability, transfer controls, and support for authorization activities.
+**Operators**, **Application Teams**, **Product Teams**, and **Automated Systems** can focus on the operational sequences, required inputs, produced outputs, deployment activities, disconnected operations, and the [[dido:99_annexes:annex-b-terms-and-definitions:c:cli|Command-Line Interface (CLI)]] or [[dido:99_annexes:annex-b-terms-and-definitions:w:web_ui|Web-Based User Interface (Web UI)]] through which they interact with Crucible.
+The Crucible documentation distinguishes operational concepts, normative requirements, controlled terminology, and implementation guidance so each audience can identify the information relevant to its responsibilities.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>