Automation

The agentic workflow engine for governed operations.

Ad360 turns advertising work into composable, triggered, governed, and observable workflows. Operators compose execution as policy-aware workflows — not as ad-hoc operational handoffs across teams and systems.

Talk to engineeringRead the composition model
RUNTIME / WORKFLOW EXECUTION
Workflow engine
  • WF-1023Recurring optimization
  • WF-0991Event-triggered routing
  • WF-0772Multichannel orchestration
  • WF-0521Compliance review
  • WF-0388Telemetry reconciliation
  • W/01
    01

    Composition

    Executable workflow primitives

  • W/02
    02

    Triggers

    Event-driven activation surface

  • W/03
    03

    Orchestration

    Concurrent runtime execution

  • W/04
    04

    Governance

    Policy and approval routing

  • W/05
    05

    Synchronization

    Distributed state coherence

  • W/06
    06

    Telemetry

    Workflow observability

SECTION 01 · COMPOSITION
Workflow composition

Four workflow archetypes for operational composition.

Operators compose executable workflows from a small, well-typed set of archetypes. Each archetype is independently observable, individually governable, and composes cleanly with the others into multi-stage execution sequences.

A/01
ARCHETYPE

Linear pipeline

Sequential execution of operationally typed stages. Each stage's output is the next stage's input. Suited to deterministic ingestion-to-dispatch flows.

Sequential · deterministic
A/02
ARCHETYPE

Parallel fan-out

Concurrent execution across independent branches that converge at a deterministic join. Suited to multichannel dispatch and parallel signal processing.

Concurrent · joining
A/03
ARCHETYPE

Conditional routing

Branch selection driven by explicit predicates against operational state. Suited to policy-aware execution paths and exception handling.

Branching · predicate-driven
A/04
ARCHETYPE

Recurring loop

Cyclic execution with explicit interval, condition, or termination predicate. Suited to optimization feedback loops and telemetry reconciliation.

Recurring · feedback-aware
SECTION 02 · TRIGGERS
Trigger surface

Workflows activate through an explicit, governed trigger surface.

Every workflow execution begins at an explicit trigger. Triggers are themselves operational primitives — observable, policy-aware, and governed. There are no implicit activations.

T/01
TRIGGER

Scheduled

Time-based activation via cron expression, fixed interval, or operational calendar.

Cron · interval · calendar
T/02
TRIGGER

Event-driven

Activation on operational events: signal arrival, state change, threshold breach, or integration-layer message.

Event bus · state · threshold
T/03
TRIGGER

Conditional

Activation on predicate evaluation against operational telemetry, segment state, or governance context.

Predicate · telemetry · segment
T/04
TRIGGER

Manual

Operator-initiated activation with audited identity, justification, and approval routing where required.

Audited · approval-routed
SECTION 03 · ORCHESTRATION
Live orchestration

Concurrent workflow execution, observed in real time.

The orchestration runtime executes workflows concurrently across operational lanes. Each lane is an independent execution context — observable, governed, and synchronized through the platform's shared state layer.

Orchestration runtime
Live dispatchActive
  • WF-7421Optimization · pacing-controllerRunning
    DispatchRecurring · 30s
  • WF-6982Routing · multichannel-fan-outRunning
    RouteEvent · channel-bus
  • WF-6517Compliance · gdpr-gateAwaiting
    TriggerManual · operator-gated
  • WF-5882Telemetry · reconciliation-loopRecurring
    ReconcileCyclic · 5m
Concurrency state12 lanes
SECTION 04 · GOVERNANCE
Governance and approvals

Every workflow runs under explicit governance.

Governance is enforced as a transverse property of the runtime — policy is validated, approvals are routed, authority is scoped, and every operational decision is captured for audit.

G/01
POLICY

Policy enforcement

Workflows are validated against active policy at composition, trigger, and execution time. Policy violations halt execution and route to operator review.

Composition · trigger · execution
G/02
POLICY

Approval routing

Sensitive operational steps route to explicit approvers through governed approval chains. Approvals carry audited identity and explicit justification.

Audited · chained · justified
G/03
POLICY

Role authority

Operators retain explicit role-bounded authority over what runs, where, and under which constraints. Authority is enforced at runtime, not at the interface.

Role-bounded · runtime-enforced
G/04
POLICY

Audit trail

Every workflow event — composition, trigger, dispatch, approval, completion — is captured to an immutable, queryable audit log.

Immutable · queryable · complete
SECTION 05 · SYNCHRONIZATION
Synchronization and feedback

Distributed workflows stay coherent through controlled feedback.

Workflows operate across distributed runtimes. Synchronization, telemetry feedback, replay, and reconciliation keep operational state coherent without forcing centralized chokepoints into the execution path.

S/01
SYNC

State coherence

A shared operational state layer keeps distributed workflow lanes synchronized on identity, segment, and execution context.

Shared · distributed
S/02
SYNC

Telemetry feedback

Execution telemetry propagates into optimization models, routing decisions, and pacing controllers through closed feedback loops.

Closed-loop · model-aware
S/03
SYNC

Replay

Workflow events are replayable from the audit log. Replay is used for state recovery, debugging, and historical reconciliation.

Event-sourced · deterministic
S/04
SYNC

Reconciliation

Periodic reconciliation workflows resolve drift between distributed runtime state and the canonical operational state.

Recurring · drift-aware

Walk through the workflow engine.

Discuss workflow composition, governance constraints, managed execution support, or runtime behaviour directly with engineering.

Discuss workflow designReturn to overview