Every quarter, your AI agent operation has done a few thousand things. Drafted client communications. Updated CRM records. Pulled regulatory citations. Routed exceptions to humans for review. Read from systems. Written to systems. Learned from operator-promoted lessons. Added new documents to the approved knowledge base. Retired old ones.
The audit log captured all of it. The audit log is also unreadable to anyone who does not have the time to query it. Atlas Quarterly is the bridge.
What it contains
Atlas Quarterly is rendered from the substrate itself, not assembled by a marketing team. The substrate already knows everything it needs to summarize the quarter; the document is the readable view.
- Workflow inventory. Every agent in production this quarter. What it does, what data it reads, what it writes, how many cases it processed, what the approval rate was.
- People map. The operators in the approval seats. The reviewers. The escalation owners. Who approved what, by volume.
- Vendor and system map. Every external system the agents read from or wrote to. New connectors enabled this quarter. Connectors retired.
- Decision history. Lessons promoted by operators this quarter (the rejection notes that became permanent rules). Patterns the system caught and adapted to.
- Source-document changes. Knowledge base documents added, updated, retired. The version history that lets a future audit trace what the agent saw on a specific date.
- Substrate posture. Governance configuration changes (none, ideally). LLM provider changes. Audit-log retention confirmations.
- Exceptions and notable incidents. Cases the system flagged for human review at higher than expected rates. Any flagged security events. Resolution status.
Why it exists
Three readers, three reasons.
The COO needs one document. Most operations leaders cannot spend an hour a week reviewing agent dashboards. They want one quarterly document that tells them whether the AI agent operation did what it was supposed to do, what changed, and what to pay attention to next quarter.
The CIO needs proof the substrate held. The architectural promise of substrate-first AI was that governance is invariant. The CIO wants to read the quarterly and see, in plain language, that the approval gate fired on every external action, the audit log captured everything, the tenant isolation held, the model swap (if there was one) preserved every property.
The compliance officer needs the bridge to the regulator. The full SOC 2 / GDPR / FINMA evidence package is the auditable artifact. Atlas Quarterly is the document that summarizes which quarters are covered by which evidence, which incidents required notifications, and where to find the export packages when the auditor asks.
What it is not
- It is not a marketing newsletter. The substrate writes it; the customer edits it; it ships.
- It is not a replacement for the audit log. The audit log is the source of truth; the quarterly is the readable summary that points to it.
- It is not optional. Every Atlas / Enterprise tier customer gets one each quarter as part of the platform.
- It is not generated by an LLM in a freeform pass. The substrate generates it from structured data; the LLM is used to render the prose, with source receipts on every claim.
The architectural pattern this maps to
Atlas Quarterly is a worked example of the substrate-first principle applied to reporting. The substrate captures structured records of every action, every change, every approval. Rendering a quarterly summary is a query against that structured record, plus a templated rendering pass. The document is always grounded in what the system actually did because the substrate is the only thing that produced it.
Contrast: a quarterly that is assembled by a vendor team based on what they remember from the customer’s deployment, with light LLM polish. That document is unreliable the moment something happened that the vendor team did not see.
What customers do with it
The patterns we have observed:
- The COO forwards it to the executive team with one line on the highlights.
- The CIO forwards it to the security team with confirmation that the substrate posture is unchanged.
- The compliance officer files it alongside the SOC 2 evidence package as the quarter’s overview.
- The operator team uses the lessons-promoted section as the agenda for the next quarterly retro.
- The procurement team uses the vendor-and-system map to update their internal architecture inventory.
The document costs the customer about ten minutes per quarter (review, light edit, forward). The substrate-side machinery that produces it does the rest.
Where to read next
For the substrate that makes the quarterly automatic, read What Is Atlas?. For the audit-log architecture the quarterly draws from, read Audit Trail Patterns for AI Agents. For the 12-month customer pattern that produces the quarterlies, read How Legacy Went 8x in 12 Months on Atlas.