Atrium

Atrium is where staff and their agents make things together. It holds two kinds of content — documents, written in markdown, and interactive artifacts — versions them with visible authorship, and publishes them to the staff intranet or the public web.

Built for agents first

The rule we held to: anything a person can do in Atrium, an agent can do through the same tools. There is no path that only works through the user interface. The in-app editors, agents working over MCP, scripts calling the REST API and scheduled skills are all clients of one content API, and it is the source of truth for how content is created, versioned and published.

That is what lets an agent draft a procedure, a person edit it, and the page record who wrote which part.

What it does

• Documents and artifacts. Documents are markdown that renders richly. Anything interactive is an artifact.
• Versions with authorship. Every version is kept, and you can see which changes came from a person and which from an agent.
• Permission-aware. Items are private, shared with a group, or public. Published content becomes grounding for AI Studio's assistants — scoped to who is allowed to see it.
• Fed by Atrium Capture. Record a workflow in Chrome or on a Mac and it arrives in Atrium as a draft guide.
• Publishing is a deliberate step. A document goes to the staff intranet or the public web, and can be taken down from either. Publishing to the public web takes a separate permission from publishing internally.
• Exports as Open Knowledge Format. A single item or a whole collection, in the same format this site is published in, so any agent can read it without a custom integration.