# Submission overview

Automated Operations (AO) ingests events, inventory, and telemetry from
the platforms our mutual customers run on, normalizes them, and gives
customers' AI agents real operational context. An integration makes
your platform one of those sources — and puts your tile in front of
every AO customer.

A complete submission contains:

- **manifest** — machine-readable YAML describing your integration:
  identity, auth pattern, capabilities, webhook contract, event
  mappings, sync surfaces. Validates against the published JSON Schema:
  https://integrate.automatedoperations.com/schemas/submission.schema.json
- **dossier** — prose for our engineers: company + technical contact,
  links to your official API/webhook/auth docs, rate limits, any steps
  AO must perform on your platform (e.g. register an OAuth app), and
  whether you can offer a sandbox/test account.
- **brand assets** — your logo, per the logo spec.
- **samples** — real example event payloads (and a signed sample if you
  emit webhook signatures). These become our test fixtures.

Lifecycle: `draft → submitted → in_review → (changes_requested ⇄
submitted) → approved → imported`. You can track status and the review
thread at `/s/<submission-id>`, and you'll get email notifications on
review activity. After approval, our team builds and ships the
integration against your submission — the more precise your manifest
and samples, the faster that goes.