Atlas is the Guild's data, knowledge and systems agent, one of the nine Arch Wizards, listed on the About page for data engineering and infrastructure. The home page calls it the foundation carrier. Its job is to map data, knowledge, integrations and dependencies so that the Guild — people and agents alike — can act from trusted context.
What Atlas does
- Maps sources and lineage. Where data comes from, who owns it, and how each figure can be traced back to its source.
- Maps dependencies. What connects to what, across applications, integrations and cloud infrastructure, so that it is clear what moves together.
- Builds and maintains data pipelines. Keeps data flowing reliably and manages warehouse operations.
- Prepares knowledge and context for agents. On AI engineering missions, Atlas is responsible for knowledge and context: what an agent knows, and where it came from.
On a data engagement the first step is a landscape audit — sources, gaps, owners and decision needs — and Atlas's part of the team is the sources and their lineage. On cloud work, its part is the map of what depends on what.
Atlas note — A knowledge system is not a database with a vector index. It is a living system that connects your organisation's knowledge with the operational context where decisions are made.
Working with the Human Wizards
Atlas's human checkpoint is the Platform Wizard — on the Guild's council, the lead accountable for architecture, code quality, infrastructure and reliability. Atlas maps and maintains; people decide the target state. On cloud missions the site says it directly: cloud architects govern the target state while Atlas maps the dependencies. On data missions, data engineers and domain owners work with Atlas and Oracle to make definitions explicit and keep every insight connected to its source.
Like every agent the Guild deploys, Atlas has a role, an identity, approved tools, explicit limits, evaluation criteria and a named Human Wizard.
Where you meet Atlas
| Mission | Atlas's part |
|---|---|
| Data & intelligence | Sources and lineage |
| AI engineering | Knowledge and context |
| Cloud & DevOps | Cloud map and dependencies — keeps every bridge visible and resilient |
| Software development | Dependencies and systems |
| SaaS & platforms | Systems and integration |
| Managed operations | Systems and dependencies |
| Media intelligence | Catalogue and lineage |
| Voice & customer experience | Customer and system context |
Works with
- Oracle — on data missions Atlas takes sources and lineage, Oracle quality and insight.
- Sentinel — Atlas maps the dependencies, Sentinel watches every production boundary.
- Hephaestus — Hephaestus builds while Atlas maps the dependencies.
- Athena — shares the AI engineering, SaaS, software and voice missions.
Writing
Atlas writes about knowledge systems, retrieval and the cost of systems that do not talk to each other.
- Field Guide 017: Building a Production AI Knowledge System — the Guild Library names Atlas as the agent that prepared it: architecture, patterns and practical guidance for knowledge systems that power agents in real business environments.
- RAG architecture — why retrieval-augmented generation is a retrieval problem before it is a generation problem, and when it is the wrong pattern.
- The hidden cost of disconnected business systems — re-keying, reconciliation, waiting and risk, and why agents make that cost larger rather than smaller.
It also introduces the Data and Knowledge Systems topics.
