What a team gets
Everything in the personal app, shared.
Shared workspaces with roles
Owner, admin, editor, commenter, viewer, beside each person's private space. Nothing private is shown to the team.
Live co-editing
Shared notes edit together in real time, and every page keeps a history of who changed what.
Alignment, briefings, and audits
How every project ladders up to a pillar, who owns it, and where the gaps are. Briefings, client status and risk registers written from the team's own work.
Assignments and decisions on the record
Assign a task or request a decision on a page and get told in the app. Decisions file under their project.
An admin console
Members, an access matrix across every space and person, and the audit trail. Enterprise adds single sign-on and SCIM. Security has the detail.
Agents, with a person in the loop
Connect any agent over MCP. Its work arrives as proposals you approve, narrow, or deny. The loop is below.
The alignment view · captured from a demo workspace
A project page · owner, stage, deadline, decisions filed where the work lives
Everyone also keeps the personal app: their own vault, offline, free. What one person gets →
Agent work
Your agents propose. You decide.
Hand work to any agent that speaks MCP and it proposes instead of writing. A person with the right role approves, narrows, or denies, and the decision is recorded with who, when, and why.
Connect
One endpoint, one key, resolving to one agent in one workspace. Your agent keeps its own tools.
Remote MCP · Live
Land
Its writes arrive as proposals: what it wants to do, its evidence, and its confidence. Nothing has moved yet.
Proposal queue · Live
Decide
Approve it, untick the parts you do not want, or deny it and remember the answer as a standing rule. Your verdict is the write.
Web and desktop · Live
One real turn: it reads the workspace, names the risk and its owner, and says what it could not reach
Nothing lands until a decision is recorded.
The proposal
The proposal, up close.
confidence 0.82
Draft the v0.1.42 release note and file three follow-ups
- Create pageRelease notes / v0.1.42
- Add taskChase the Windows signing ticketdue 2026-08-27
- Add taskRe-run the updater canarydue 2026-08-22
- Update pageChangelogbody replaced
You can narrow it. Untick a line and only what is left runs. An approval can remove items and never add one.
You can say why. A verdict carries your reason, who gave it, and when.
A denial can stick. Remember an answer for a set number of days and matching proposals are refused at submission.
You can let the safe ones through. Auto-approve is off until you switch it on. Set a confidence floor and a batch that clears it applies straight away, recorded as approved by your policy rather than by a person, with the reason on the row.
The record
What happened, and who said yes.
Every proposal keeps what was asked for and what was approved, side by side.
Every verdict records who decided, when, and why.
Applied and approved are different facts. A proposal that applied three of five changes says so.
An agent key is capped at viewer, commenter, or editor. It can never manage members or delete a workspace.
Aurum holds no compliance certification today. This is what the product records, not an attestation. See Security.
Running an agent already? Connect it over MCP →