This requirement derives from:
The Original Requirement states:
The system shall integrate with GitOps workflows.[C1]
FR-DSO-002:
No other substantive normalization is required.
A GitOps Workflow records declarative desired state in a Version Control System and coordinates automated reconciliation of actual operational state with that desired state.
Integration with GitOps Workflows enables Crucible operations to participate in the controlled application of approved Declarative Configuration.
A GitOps Workflow can involve:
This requirement establishes integration with GitOps Workflows without prescribing:
Separate requirements, architecture specifications, workflow definitions, and operational policies govern those subjects and behaviors.
This requirement applies to:
Verification confirms that:
The following pages reference this requirement:
Implemented and Verified
Review and approve FR-DSO-002 as a leaf requirement.
Determine whether separate requirements identify the GitOps operations that Crucible must perform.
Determine whether separate requirements govern desired-state retrieval, drift detection, reconciliation, and reconciliation-status reporting.
Determine whether separate requirements govern repository authentication, authorization, and credential management for GitOps Workflows.
This requirement page retains the stable requirement identifier FR-DSO-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 integration with GitOps Workflows. It does not require a particular GitOps product, repository provider, branch strategy, reconciliation tool, deployment platform, or triggering mechanism.
FR-DSO-001 governs integration with general Git-based Workflows.
FR-DSO-003 governs CI/CD Pipeline integration.
FR-DSO-004 through FR-DSO-006 govern automated build, deployment, and validation execution.
Do not add particular reconciliation operations, GitOps products, hosting services, branch policies, authentication methods, or automated execution obligations 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-08-devsecops-integration:fr-dso-002#Statement&noheader&nofooter&noeditbtn}}
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.