public:99_annexes:annex-b-terms-and-definitions:c:controlled_input

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:c:controlled_input [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:c:controlled_input [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Controlled Input ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Controlled Input is an identifiable input governed by defined controls before and during its use in an activity, process, workflow, or system operation.
 +
 +The controls may govern:
 +
 +  * Identification
 +  * Revision
 +  * Source
 +  * Authorization
 +  * Integrity
 +  * Availability
 +  * Validation
 +  * Applicability
 +  * Retention
 +  * [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
 +
 +A Controlled Input may include:
 +
 +  * An [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]]
 +  * An [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprint]]
 +  * A [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]]
 +  * A policy
 +  * A schema
 +  * A parameter set
 +  * A source-code revision
 +  * A build specification
 +  * A deployment specification
 +  * A test specification
 +  * A data set
 +
 +A Controlled Input differs from an uncontrolled input:
 +
 +  * A Controlled Input has an identifiable state and applicable governance controls
 +  * An uncontrolled input lacks one or more controls required to establish its suitability for the activity
 +
 +The designation **controlled** does not by itself mean that the input is approved, valid, secure, or suitable for every use. Applicable requirements determine the controls and acceptance conditions.
 +
 +===== Definition =====
 +
 +//identifiable input governed by defined controls that establish its state and suitability for use in an activity//
 +
 +===== Source =====
 +
 +Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +===== Note =====
 +
 +A Controlled Input may be human-readable, machine-readable, physical, or digital.
 +
 +The applicable controls determine whether the input requires:
 +
 +  * An identifier
 +  * A revision identifier
 +  * An authoritative source
 +  * Validation
 +  * Approval
 +  * Authorization
 +  * Integrity verification
 +  * A retention period
 +
 +A [[public:99_annexes:annex-b-terms-and-definitions:v:version-controlled_artifact|Version-Controlled Artifact]] may serve as a Controlled Input when the applicable controls establish its suitability for the intended activity.
 +
 +===== Example =====
 +
 +An identified revision of an Infrastructure Configuration retrieved from a [[public:99_annexes:annex-b-terms-and-definitions:v:version_control_system|Version Control System]] and accepted for use by a [[public:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] is a Controlled Input.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>