- identityOne login per person. Organization membership sets what they and their agents can reach.Scoped
- attributionAn agent writes as the person who ran it, with the agent's own mark on the change.Recorded
- historyEvery page keeps every revision. Any change opens as a diff.Kept
- visibilityA wiki is private to its organization, or to the people and teams granted.Private
Product
Shared knowledge, kept by the people and agents who work from it.
One record, five ways in. Open it in the browser to read and review. Install the CLI to carry your identity into any agent. Run that agent in its harness and it reads the record before it works, then writes back what it decided. Mention Known in the team chat and it answers in the thread. Ask the conversational UI and the whole company gets the same answer, with sources.
01 · The Browser
The wiki, read and reviewed where the team already works.
Read, review, and keep the wiki. History, diffs, notes, and structured data on every page.
Explore the BrowserChanges
2 new since you last looked
- +18
decisions.annual-billing-refunds
pi · agent, run by Brock · 3h
- +4 −1
people.dana
pi · agent, run by Priya · 1d
- +12 −3
decisions.annual-billing
Dana · 2d
- +22 −9
runbooks.invoice-template
Priya · 5d
decisions.annual-billing-refunds · pi · agent, run by Brock
− Open: the refund window for annual plans is not yet decided.
+ Annual plans refund in full within 30 days of the term start.
+ Decided in #finance on 12 September by Dana and Brock.
02 · The CLI
One command line, signed in as you.
One command line that carries your identity into any agent. Sign in once per organization.
Explore the CLIbrock@acme ~ $ known --help
known (v0.1.0) ~ the Known CLI
- known login [--endpoint <name>]
- sign in to an org (pick it in the browser)
- known sessions
- every session on this machine
- known whoami
- who you are, in every session
- known logout
- sign out of every session
- known config
- show resolved config (tokens redacted)
- known endpoints [<url>]
- list environments / check a URL
- known <org>
- commands available for that org
- known <org> ping
- prove the session works (token, membership, policy)
- known <org> post --text "…"
- post a note (also --file, or pipe stdin)
- known <org> wiki [<cmd>]
- the org's shared wiki (get, set, tree, search, …)
- known <org> whoami
- who you are in that org
- known <org> logout
- sign out of that org
- known <org> rpc <method>
- call a JSON-RPC method as that org
brock@acme ~ $
03 · The Harness
Any harness, any model.
One memory system for your whole fleet of agents and the team that runs them. In Claude Code, Codex, Grok Build, or Pi the agent reads the record first and writes back what it decided.
Explore the Harnessbefore you touch billing: what did we decide about annual refunds?
Bash(known acme wiki get decisions.annual-billing)revision 4 · Dana · 2d ago · on file (expand)
Annual plans bill up front. Refund window: not yet decided. 1 note open · Sam: do we prorate?
Not settled. Annual plans bill up front and the refund window is still open, with Sam asking whether we prorate. Source: decisions.annual-billing, revision 4.
finance settled on 30 days this morning. is anyone else on this?
Bash(known acme wiki search "annual refund")3 pages · people/dana · decisions/annual-billing · runbooks/invoice-template (expand)
people/dana · owns billing policy · changed 1d ago by pi, run by Priya decisions/annual-billing · Dana · 2d ago runbooks/invoice-template · Priya · 5d ago
Dana owns billing policy, and Priya’s agent touched her page yesterday. I’ll write the decision as its own page and point both of theirs at it.
write it up so their agents see it too
next session, Priya’s agent reads this page before it touches billing.
? for shortcuts · click a ⏺ line to expand its output
04 · The Team Chat
Ask Known where the team already talks.
Mention Known in Slack, Microsoft Teams, or Telegram and it answers in the thread. The channels you route feed the record.
Explore the Team Chat# finance
12 members · Known added
Dana 9:41 AM
Did we ever settle the refund window for annual plans? Support has two tickets waiting on it.
Brock 9:43 AM
@Known what did we decide about annual refunds?
Known App 9:43 AM
Annual plans refund in full within 30 days of the term start. Decided in this channel on 12 September by Dana and Brock; the flag in acme/billing is still off until finance turns it on. The two support tickets can be answered with the 30-day window.
Verifieddecisions / annual-billing-refunds#finance · 12 Sepacme/billing #4122 repliesLast reply 4 minutes ago
05 · The Conversational UI
Everyone at the company can ask what the company knows.
Ask Known in the browser and get the answer the company already has, with the evidence behind it.
Explore the Conversational UIAsk Known
Acme · 41 people · answers from the record
How do I request a new laptop?
Post in #it with the model you need. The standard is a 14-inch MacBook Pro and ships within a week; anything over $2,000 needs Marta's approval first. Keep your current laptop until the new one arrives, then return it in the mailer that comes in the box. Every three years you are due a refresh without asking.
Who approves if Marta is away?
Sam. Marta's page lists Sam as her deputy for policy approvals, and the approvals policy says a deputy signs for anything a policy owner would while they are out. Post in #it as usual and mention Sam.
Asked today across Acme
- Who approves expenses over $500?Priya
- What did we decide about annual refunds?Brock
- What are the on-call handoff steps?Sam
- How long do we keep customer data?Marta
- Which repos ship on Fridays?Jonah
Trust model
Who can read what the company knows, and who wrote it.
Get started