4.2 Automated Actors [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.
====== 4.2 Automated Actors ======

[[dido:02-crusible:04-actors-and-responsibilities:start|Go to 4. Actors and Responsibilities]]

Automated Actors are software processes outside [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] that initiate an operation, provide an input, receive a result, or respond to an operation without direct human interaction during that operation.

An automated process does not become a separately defined Crucible actor merely because Crucible can be invoked through software. A named Automated Actor belongs in this section only when an approved leaf requirement assigns that actor a specific interaction or responsibility.

Potential Automated Actors can include:

  * Continuous integration or continuous delivery pipelines
  * Scheduled automation processes
  * External orchestration workflows
  * Automated assessment processes
  * Machine clients using a supported Crucible interface

These examples do not establish required actors or capabilities. They remain outside the defined operational model until approved leaf requirements identify their required interactions with Crucible.

Automated Actors operate within the same authorization, access-control, security-domain, resource, information-handling, and transfer restrictions that apply to human-initiated operations.

Automation does not independently:

  * Grant access to an environment or resource
  * Select unauthorized inputs
  * Approve movement across a [[dido:99_annexes:annex-b-terms-and-definitions:t:transfer_boundary|Transfer Boundary]]
  * Accept operational or security risk
  * Approve deployment or operational use
  * Grant [[dido:99_annexes:annex-b-terms-and-definitions:a:accreditation|Accreditation]], [[dido:99_annexes:annex-b-terms-and-definitions:o:operational_approval|Operational Approval]], or an [[dido:99_annexes:annex-b-terms-and-definitions:a:ato|Authority to Operate (ATO)]]

===== Requirements Addressed =====

No approved leaf requirement currently identified for this page explicitly establishes a separate Automated Actor.

The page should be updated when an approved leaf requirement defines automated initiation, machine-to-machine interaction, scheduled execution, pipeline execution, or another automated actor responsibility.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>