Workspace
Automation — Turn Repetitive Work into Structured Workflows
Plan, organize and manage recurring infrastructure work with Guardian-assisted automation workflows and connected AI agents.
Move from an insight to a controlled next step.
Plan, organize and manage recurring infrastructure work with Guardian-assisted automation workflows and connected AI agents.
Automation keeps three different things separate: the automation definition, the deployment instructions prepared for an agent, and any result that agent later reports. A definition is not proof that work ran.
Overview and versions
Overview summarizes the latest deployment, Guardian's latest completed analysis for the project, proposal counts, and schedule counts. Opening Guardian from this page does not approve or run a proposal.
Versions is the deployment history for the project. Each row shows the deployment number, when it was created, and its status. You can open the log for that deployment.
This history is a record of architecture deployments already prepared in SPECTRALE. It is not a release manager, and it does not roll the infrastructure back to an earlier version.
Create an automation with Guardian
Create Automation opens a Guardian conversation for this project. Guardian asks for the intended action, how often it should be considered, the conditions, and an authorized external agent.
The result is a structured specification and, when it is complete, an automation record. It is not an execution. Selecting an agent names who may retrieve the work. It does not start that agent.
When the specification is ready, Deploy in Guardian opens the workspace deployment dialog. A person still reviews the pending change, the eligible agent, and the token cost before confirming.
One accepted deployment request consumes one SPECTRALE deployment token. Guardian's own replies use model inference, which is separate from that token.
Schedules
Schedules lists recurring automations that have been configured, including frequency, assigned agent, last result, and whether the schedule is active.
Suggest a review interval asks Guardian for an interval. The suggestion does not create a schedule and it does not enable one. A schedule must stay unchanged until you save it.
Security-sensitive schedules stay inactive until they are approved. Read-only access cannot change a schedule. A schedule whose execution is not supported cannot be switched on. Do not treat a saved frequency as verified recurring execution.
Pause and delete
Pause and Delete do not change the automation by themselves. Each action opens a Guardian conversation and asks you to confirm before the change is added to the deployment draft.
The automation is paused or deleted only after an authorized agent deploys that change. Deleting keeps the audit record.
Status and limits
Proposals show whether more information is required, whether approval is still needed, and when a result was last verified. Approval, when the proposal requires it, stays with a person who is allowed to approve. Preparing a proposal does not execute it.
Do not expect fully autonomous remediation, provider-side edits, or SPECTRALE starting an external agent. Agent work still depends on a connected agent retrieving that work, and on the permissions that agent holds. See Fleet.
Availability
Automation is included in Growth and Architect.
Important to know
Important. Automation does not grant unrestricted access to connected infrastructure, and it does not turn on scheduled model inference by itself.