Five ways work starts.
One way it's governed.

You ask a question in chat — "what's moving in our pipeline?" The agent answers from your CRM and your org's memory. You say "make that a morning briefing," and it becomes a standing scheduled job: delivered every morning, remembered in org memory, grounded in the knowledge brain. A question became an institution in one sentence.

Every morning before you're up, scheduled jobs sweep the systems you've connected — inbox, tasks, pipeline, the news that matters to you — and the briefing is in your channel of choice by the time you sit down.

The outside world touches your business and Aurora answers before you do. A candidate applies through a form the agent built when you asked for one in a sentence — the resume is read, a summary written, a clean entry filed, and the tracking app the agent also built updates itself. A booking is the same reflex: a conflict-checked calendar event with a meeting link and a plain-language note in your inbox — 85 seconds, zero approvals, fully audited.

"Get this meeting scheduled." The agent emails the counterparty, waits, nudges politely, escalates when it's stuck, verifies against the calendar before declaring itself done — and the mandate dies at close. Days-long, autonomous, on the record.

Some work should never run unattended. Workflow pipelines carry approval gates: the agent brings the work to the gate; a human waves it through — from the portal or the channel they're already in — and the pipeline continues.