AIOS 108SYNAPSE

Part of the SYNAPSE suite

SYNAPSE Automations · Operate

Automation you can pause mid-step.

Define routine multi-step work once — scheduled or event-driven — then let it run inside bounded permissions, with human approval gates before anything consequential and an audit log kept for every run.

Request access Enter SYNAPSE Studio

Walk a run

Four moves, tap through.

A front-end walkthrough of one run. Tap each phase. Nothing executes. Nothing leaves your browser.

Starts on a schedule or an event

A run begins when its schedule arrives or a defined event occurs. Triggers are declared up front, so nothing starts for reasons you cannot see.

Three abstract permission gate arches fading into dark

How a run works

Trigger, steps, approval, audit.

Every run follows the same readable path. You can inspect, pause, or stop it at any point along the way.

  • 01 · Trigger

    Starts on a schedule or an event

    A run begins when its schedule arrives or when a defined event occurs — a new file, a new request, a status change. Triggers are declared up front, so nothing starts for reasons you cannot see.

  • 02 · Steps

    Follows declared steps, including Studio apps

    Each run executes an explicit sequence: gather, check, draft, file, notify. Steps can call Studio-built apps as individual stages, reusing the same workspace rules and permissions instead of inventing new ones.

  • 03 · Approval

    Waits where a person must decide

    Steps marked consequential — sending, publishing, deleting, sharing, spending — hold for human approval. The request states what is asked, in which workspace, with what scope, and how to undo it.

  • 04 · Audit

    Leaves a log you can replay

    Every run keeps its own audit log: trigger, steps taken, approvals granted or denied, and changes made. Pause a run, rewind through its record, and resume or close it deliberately.

Scheduled

Routine work, on a rhythm you set.

Morning triage, weekly filing, recurring checks and follow-ups. Schedules are declared per automation with a visible scope, so a routine run never quietly grows into something broader.

  • Schedule and scope declared before the first run
  • Each occurrence logged as its own run
  • Pause or close the schedule without losing history

Event-driven

Responsive work, still bounded.

Start a run when something happens: an incoming request, a new document, a status change in a Studio-built app. Events carry only the data the automation is permitted to see.

  • Subscribed events listed per automation
  • Payloads limited to least-privilege fields
  • Unexpected events ignored, never auto-absorbed

Composition

Studio-built apps plug in as steps.

Automations do not replace what you build in Studio — they orchestrate it. A published Studio app can serve as one stage inside a longer run, under the same identity and control plane.

  • Reuse

    Build once, run on rails

    Draft the behavior in SYNAPSE Studio, then reference it as a step. The automation inherits the workspace discipline instead of reimplementing it.

  • Least privilege

    Credentials scoped per automation

    Each automation receives only the credentials its declared steps need. Nothing is shared broadly, and widening access requires a new, explicit approval.

  • Reviewable

    Outputs held for a person

    Drafts, filings, and notifications produced along the run are staged for review. Nothing sends or publishes until the approval gate for that step is granted.

Control commitments

Standing promises for every run.

These hold whether a run is scheduled or event-driven, short or long. Read the philosophy for the reasoning behind them.

  • Human approval gatesConsequential steps wait for a person. The request is written to be understood in seconds: what, where, with what scope, and how to undo it.
  • Least-privilege credentialsEach automation holds the minimum access its declared steps need — files, network, tools, credentials — and nothing more.
  • Audit log per runTrigger, steps, approvals, and changes are recorded as they occur, in language a person can read and replay.
  • Stoppable by defaultPause, rewind, or close any run from its record. Closing the automation stops future runs without erasing history.

Begin

Put routine work on rails you control.

Request access to SYNAPSE Automations, or enter SYNAPSE Studio today to start building the steps.

Request access Enter SYNAPSE Studio