Facts and decisions
What you were told, and what you decided - kept apart from what you remember.
A client said Saturdays. A supplier said six weeks. You decided to cap it at twelve. Record each with who said it, when and why, and your team's AI sees them before anything else - and nobody can quietly change them.
What the source told you
A client, a supplier, or one of your own people speaking for the business. A fact carries who said it, when, and how they told you - meeting, email, call, message, their site or their document.
Back it with evidence where you can: a memory, a page, a file or a collection in Kythene, or a web address.
What you're waiting to hear
Record who has to answer and the question word for word. While it's open, your AI knows the answer is unknown rather than absent - so nobody guesses in the meantime.
Mark it asked once it's gone. When they reply, answer it, and the same record becomes a fact with the question kept on it.
What was decided, and why
Who decided, when, and the reasoning - so it outlives the meeting it was taken in. An assumption you're working to is a decision you took, not a fact, and is recorded as one.
Decisions are replaced or corrected exactly like facts.
Never quietly changed
Two ways to change a record, and both keep the history.
Memory gets rewritten as your team's understanding improves. That's right for memory. It's wrong for what a client told you, so these aren't overwritten - they're replaced or corrected.
The source changed their mind
The old record is kept, marked Replaced and linked to the new one. Your AI sees only the new one; you can still read what used to be true.
You wrote it down wrong
The record is fixed in place and marked Corrected, with what was wrong. Every earlier version is kept.
Only whoever recorded a settled fact or a decision, or an admin, can correct or delete it. A question's wording can be edited by anyone who can write, since nothing has been claimed yet.
For their AI
Your AI sees them first.
Recall puts facts and decisions in a block of their own, above the memories. An agent checks what you were already told before it asks a client again, and when it doesn't know something it asks a question rather than recording a guess.
Any MCP client works - Claude, Cursor, Codex, Copilot and the rest - and your team need not all use the same one. Connect yours →
Where you record them
- On screen
- The Facts screen has tabs for facts, open questions and decisions, filtered by project and area.
- From your AI
- Over MCP: record a fact, ask a question, answer it, record a decision, replace or correct a record, and list what's there.
- From the terminal
- The
kytheCLI does the same, for scripts and for people who live there. - Per project, or for everything
- A record applies to one project, or to the whole team when it has none. An area names the part of the work it's about.
One place for the team and their AI
Facts and decisions are one part of it.
Work in flight
A draft, a result, a report - published, versioned and reviewed paragraph by paragraph.
What the team settled
The durable pages, in a tree a person can browse - written by your agents, approved by you.
What the AI applies
The agreed thing, recalled in the flow of work by every teammate's agent. Facts and decisions are its most trusted part.
Stop re-asking what you were already told.
Sign in, connect your AI, and record the first fact. It's free to start.
Sign in with GitHub or Google. No card.