Controlled Input [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Controlled Input ======

[[dido: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
  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

A Controlled Input may include:

  * An [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]]
  * An [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprint]]
  * A [[dido: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 [[dido: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 [[dido:99_annexes:annex-b-terms-and-definitions:v:version_control_system|Version Control System]] and accepted for use by a [[dido: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>