Skip to main content
Use this sequence before writing against an Atlas transport. It produces a small integration contract that can survive API and provider changes.
1

Define the use case

State the decision or workflow the integration enables. Name the operator, latency target, and failure consequence.
2

Identify source systems

Record each system of record or engagement, its ownership, and the direction of exchange.
3

Map objects and identities

List every exchanged object type, its stable source key, normalization rule, and system of record. Document ambiguous or missing identities.
4

Define scope with Lists

Identify which objects belong in the workflow and how membership changes.
5

Define cadence with Cycles

Describe when work repeats, which stages it follows, and who can advance it.
6

Connect API and event surfaces

Confirm the approved transport, authentication, freshness, volume, idempotency, backfill, and deletion behavior.
7

Validate outcomes

Test representative and adversarial records, compare source and Atlas results, monitor freshness and errors, and document rollback.
8

Review the audit trail

Confirm that identity changes, decisions, permissions, and execution outcomes are traceable to the responsible principal and evidence.

Integration brief template

Attach this brief when requesting Atlas v1 API or webhook access. It gives the Atlas team enough context to confirm the correct supported surface.