Workspace
- Alder Bikes
- Fenwick Tea
- Kestrel internal
Agencies
Local-first · Built in the EU
Every agent. Approved facts only.
Your team's decisions become approved facts that Claude Code, Codex, Cursor and Claude Desktop read as soon as they are approved. Agents propose. People approve. Every change has a name on it.
macOS first · For teams of 5–50 · Your data stays on your Mac
One decision.Every agent in sync.
A decision from Tuesday's meeting becomes a proposal, a named person approves it, and the next agent that asks gets the new answer.
Proposals
Sorted by criticality and age- Launch date → 19 MarchAlder Bikes · Product · from meeting notes Medium
- Tone of voice: no exclamation marksKestrel internal · Brand · from Claude CodeLow
- Onboarding checklist, step 4Kestrel internal · Process · from CursorLow
alder.launch_date
Needs 1 approval
Launch date → 19 March
12 March→19 March
Source: Alder Bikes weekly, meeting notes · Proposed by Jonas Weber
Why Medium
- Changes a governed fact
- Client-facing date
- 3 skills read this fact
RejectEdit
Approve
Approved by Lena Brandt · 10:42 · signed
Touch ID to approve
“Launch date → 19 March” as Lena Brandt
Meeting notes · Alder Bikes weekly
Photo shoot moves to the second week.
Decision: launch moves to 19 March.
Next review on Friday.
Proposal opened> When does Alder Bikes launch?
facts.get alder.launch_date
12 March · approved 2 Oct by Jonas Weber
>
facts.get alder.launch_date
Agents propose.
People approve.
Nothing an agent writes reaches approved state on its own. A person with a name, a key and Touch ID signs every change.
01
Governed facts
Each fact has one value, one owner and its full history. Agents read the current value, never a stale copy.
02
Criticality by rules
Every proposal is scored from what it changes, not from what it says. Text inside a proposal can never lower its score.
03
Named approvals
Low changes need one approver, high changes two. Each approval is signed with the approver's own key after Touch ID.
04
Every agent tool
Claude Code, Codex, Cursor and Claude Desktop read facts and skills over MCP. Agents can propose; they can never approve.
05
History you can roll back
Every change is an entry in an append-only journal. Return to any approved state without losing what happened.
Ask anything.Change nothing unapproved.
Your agents read the same approved facts and skills, whichever tool your team uses. When an agent spots something wrong, it opens a proposal instead of changing it.
Built for teams that run on agents
For agencies and product teams of 5 to 50 people whose work already runs through AI agents.
skills/release-notes.md
- product.nameapproved
- support.hoursapproved
- tone.voiceapproved
Product teams
Specs, names and tone of voice in one approved source.
Your own medium change
Second look in 24 h
Then it applies everywhere
Solo founders
Approve your own changes, with a second look for big ones.
Lessons · team level
- A correction to support hours
- A clearer refund wording
- A new term for the glossary
Teams with a works council
Approvals are named. Lessons never are.
Your data stays on your Mac.
Facts and skills live in your own synced folder. Nothing goes to our servers. Only the model endpoint you choose and your optional Slack or Teams notice ever leave the machine.
- Local-first
- EU by design
- Works-council mode
- Your own model key
Early access
We are onboarding a small group of design partners. Founding-customer terms are agreed on a call.
Solo
For founders who run their company with agents.
- One workspace
- All four agent tools
- Approve your own proposals
- 24-hour second look for big changes
Team
For product teams of 5 to 50 people.
- Shared workspace and areas
- Criticality rules and second approver
- Slack or Teams notices
- Roles for builders, approvers and viewers
Agency
For agencies with many clients.
- One workspace per client
- Skills synced per project
- Client separation tested
- Works-council mode
Common questions
Still have a question? Write to us. A person reads every message.
It keeps every agent tool your team uses on the same approved facts and skills. Decisions and corrections become proposals; a named person approves them; agents read the result through MCP.
Claude Code, Codex, Cursor and Claude Desktop on macOS. Web-based assistants are not part of the first version.
No customer content goes to our servers. Facts live in your own synced folder. The only outbound connections are the model endpoint you choose, the meeting tool you connect and an optional Slack or Teams notice that carries only a title, an area and a criticality.
People with an approver or builder role. Low changes need one approval, high changes two. Agents can propose, but no agent can approve.
By rules you control, applied to what a proposal changes: which area, which fact, how many skills read it. Text in the proposal cannot lower the score.
No. It runs on your Macs and stores everything in a folder you already sync. You bring your own model access.
Each client gets its own workspace, and skills sync at project level. A test checks that no value from one client's workspace is readable from another client's folders.
Yes. Works-council mode is on by default. Approvals carry names, but lessons and corrections stay at team level, and no screen or report shows per-person numbers.
The first version is macOS only. Tell us what you use when you join the waitlist.
We are onboarding design partners now. Join the waitlist and we will get in touch.
Ready to put your agents on approved facts?
Join the waitlist. We onboard design partners one team at a time.