PKPEEK Docs
Docs/Agents & governors

Automation overview and agent templates

Screens 5.1 and 5.2 — review the permitted automation portfolio per tenant and release agent templates for agency adoption.

PEEK Platform Administrator · PEEK Technical Reviewer

/peek/customers/tenant-a/5-1
Live walkthrough · Automation overview and agent templates
/peek/customers/tenant-a/5-1
/peek/customers/tenant-a/5-2

Agents are governed automations built from templates. 5.1 shows approved templates, agency enablement, SI dependency and current governors per tenant. 5.2 publishes templates (catalog type agent_template) with purpose, trigger, action manifest, dependencies and human decision gates.

Two different off switches — SI Off stops SI-dependent agents only. All Automation Off stops every agent, including deterministic templates — which then must not appear executable.
Heads up — Publishing a template never authorizes execution: no agency schedule or run is created automatically. Templates with undeclared actions, destinations or ambiguous execution identity are rejected.

5.1 · Agency Automation Overview

Review the permitted automation portfolio. Open it at /peek/customers/tenant-a/5-1 (any tenant ID you can access works in place of tenant-a). The primary action is Open agent profile, which requires agent_governance.read.

How 5.1 works

  1. 1. Show approved templates, agency enablement, SI dependency and current governors per tenant

Screen 5.1 contract

Fields shown
Agent class, SI dependency, agency enablement, governors
Primary action
Open agent profile
Required capability
agent_governance.read
Validation
Separate SI Off from All Automation Off; counts and status are sanitized and versioned.
Successful outcome
Open eligible agent governance without launching a live agency run.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.5.1.action (acceptance test AT-UI-5.1)
Requirements
R02, R06, R10, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-5.1
Boundary — SI Off and All Automation Off are distinct controls.
Rejected even if the browser allows it — With all automation stopped, a deterministic template must not appear executable.

5.2 · Recommended Agent Templates

Release agent templates for agency adoption. Open it at /peek/customers/tenant-a/5-2 (any tenant ID you can access works in place of tenant-a). The primary action is Publish recommended template, which requires agent_template.publish.

How 5.2 works

  1. 1. Define purpose, trigger, action manifest, dependencies and human decision gates

  2. 2. Release for agency adoption

Screen 5.2 contract

Fields shown
Template version, trigger, action manifest, dependencies
Primary action
Publish recommended template
Required capability
agent_template.publish
Validation
Reject undeclared actions or destinations and ambiguous execution identity. Template publication is not execution approval.
Successful outcome
Versioned template becomes available under agency permissions and purchased capabilities.
Screen states
Loading; empty; ready; restricted; stale; error; review pending
Audit event
admin.screen.5.2.action (acceptance test AT-UI-5.2)
Requirements
R02, R06, R28, SYS02, SYS04, SYS06, SYS10, SYS11, SYS20, SYS23, UI-5.2
Boundary — Template release does not authorize agency execution.
Rejected even if the browser allows it — Publish an agent template; confirm that no agency schedule or run is created automatically.

Related guides

Governors and execution identity

Screens 5.3 and 5.4 — bound allowed operations, destinations, quotas and approvals; define who an agent runs as.

Communication rules and simulation

Screens 5.5 and 5.6 — govern outbound messages with exact-content approval, and test templates against synthetic cases before release.

Catalog lifecycle: draft, review, publish

How every “Publish …” screen works: draft, validation, independent technical review bound to the diff hash, then publish.