One platform. Both workforces.
Documents, spreadsheets, presentations, notebooks, and dashboards — every asset agent-readable and agent-writable. Humans and agents occupy the same artifact at the same time, with full attribution on every change.
Olympus is not a chat window bolted onto your stack. It is the surface the work already lives on — and both workforces have write access.
Every asset is an API for the agents.
The same document a controller is editing is the document an agent can read, revise, and extend. No export step, no copy-paste bridge, no second system of record.
- → Real-time collaborative documents & spreadsheets
- → Presentations, notebooks & live dashboards
- → Every asset an API for the agents
- → Per-cell and per-block attribution
| Cell | Value | Edited by | Rev |
|---|---|---|---|
| B4 | $4.10M | Athena | v12 |
| B5 | 62.4% | D. Rowe | v11 |
| B6 | -1.20 | Athena | v12 |
| B7 | $0.94M | M. Okafor | v10 |
Attribution down to the cell.
Every change carries an author, human or agent, and a revision. Undo and redo apply to agent work exactly as they apply to yours — which is what makes it safe to let an agent touch the model at all.
The artifact is the interface.
Work does not leave the artifact to be processed and come back changed. It is revised in place, in front of you, with the trail intact — so review is reading a diff, not reconciling two versions.
From request to reviewed artifact.
- 01 Open
The artifact already exists — a model, a memo, a deck. No new workspace to populate.
- 02 Work
Both workforces edit the same surface at the same time, in real time.
- 03 Attribute
Every block and every cell records who changed it, agent or human, and when.
- 04 Roll back
Any revision is recoverable, so an agent's work is never a one-way door.
One system, named in parts.
See both workforces in one artifact.
The fastest way to understand Olympus is to watch an agent and a person edit the same model at the same time.