Automations

Define, validate, operate, observe, and retire typed event, schedule, and manual automations with signed callback delivery while preserving the independent authority, policy, and evidence boundary of every underlying business action.

BUSINESS CASES

Where this module fits

scheduled operational checks
event-triggered evidence and notification workflows
manual validate-only or authorized runs
signed webhook delivery
callback secret rotation
failed-delivery reconciliation
automation lifecycle governance

PRIMARY CONSUMERS

Who integrates it

workflow and integration developers
operations and reliability teams
automation and orchestration agents
security and audit reviewers

PREREQUISITES

What must exist first

automations:read or automations:write in the bearer-derived workspace
a server-owned approved action profile and typed trigger schema
separate current authority from the owning domain for every consequential execution
an SSRF-safe active callback endpoint and receiver-side signature verification when callbacks are used
caller-owned policies for idempotency, concurrency, retry, deduplication, failure handling, evidence retention, and receiver processing

RECOMMENDED WORKFLOW

Compose the module safely.

01
ingest live OpenAPI and discover server-owned action profiles, trigger schemas, and workspace policy
02
register an SSRF-safe HTTPS callback endpoint when signed outcome delivery is required and secure its one-time secret
03
create a DRAFT automation with one typed trigger, approved action profile, secret-free bindings, callback reference, and bounded execution policy
04
validate configuration and bindings without invoking the domain action
05
activate or resume only after current trigger, endpoint, workspace, action-profile, and domain-policy checks pass
06
for manual EXECUTE, obtain a fresh purpose-bound authorization from the owning domain and bind the request to one exact automation version
07
distinguish run admission, domain outcome, callback attempt, and receiver acknowledgement as separate states
08
rotate endpoint signing epochs, retry only eligible failed deliveries without re-running the business action, and retire endpoints or automations with retained evidence

AGENT INTEGRATION

Machine-use boundaries

Automation never creates, stores, widens, or substitutes authority absent from the triggering principal and the current owning-domain policy. Configuration approval is not execution approval.
Never submit arbitrary API paths, internal URLs, code, shell commands, executable expressions, bearer tokens, passwords, private keys, signing secrets, regulated cleartext, or reusable domain credentials in triggers, actions, bindings, inputs, or callback metadata.
DRAFT is not active, ACTIVE only admits eligible triggers, QUEUED is not started, STARTED is not domain success, COMPLETED requires the owning-domain receipt, DELIVERED only means callback acknowledgement, and alert or callback success does not prove receiver processing.
Use VALIDATE_ONLY before EXECUTE. Bind every manual run to the current automation version, one client reference, stable idempotency key, typed inputs, and a fresh single-purpose authorization when the action owner requires it.
Verify callback signatures over the exact raw body, timestamp, delivery ID, attempt, and key epoch; enforce freshness and replay protection and retain only commitments and safe response diagnostics.
A delivery retry appends a new attempt for the original minimized payload; it never reruns the automation or underlying business action. A changed payload requires a new domain event.
Endpoint deletion blocks future delivery but does not delete automations, runs, domain results, or historical receipts. Secret rotation returns a new secret once and does not change endpoint or automation authority.
No automation contract may change trading, matching, prediction-market execution, ingress, publisher, allowlist, market status, suspension, or traffic while those controls remain frozen.
Never call a planned Automation operation until its exact contract appears in the live production OpenAPI document.

Register only production-listed routes as executable tools, and re-fetch the deployed OpenAPI before generating or sending a request. Source-ready routes awaiting deployment are preparation references; planned contracts are non-executable.

MODULE CONTRACTS

Every mapped endpoint

Each operation states whether its request shape is authoritative in OpenAPI, reviewed as a planning profile, or intentionally left as an outline pending an owner schema.