Product
A decision has eight parts. Most systems keep one.
Clyreon records all eight and makes them permanent. Seven of them are the ones companies lose.
The eight parts
Each one is only worth keeping because the others are kept too.
Keep the decision but not the reasoning, and you cannot tell a good call from a lucky one. Keep the reasoning but not the facts behind it, and you cannot tell whether the thinking was wrong or the inputs were. Keep both, but never write down what would have changed anyone’s mind, and you can never settle the argument later.
What is being decided, what is at stake, and the date it has to be answered by. Someone has to open it deliberately.
A decision nobody opened is a decision nobody can be asked about later.
Each fact the decision rests on, written as a plain sentence with a source and a date. Never a raw data export. A fact is stored once and can be used by several decisions.
If the facts are kept separately from the argument, you can work out later whether the thinking was wrong or the inputs were.
The case for the position, in the words of the person making it, written down at the time.
This is the part that reliably disappears. Every system keeps what was chosen. Almost none keeps why.
Low, medium or high, stated at the moment of the decision rather than worked out afterwards.
How confident someone feels once they know the answer is a different claim, and it should not be passed off as the same one.
The thing that, if it happened, would show the position was mistaken. Written before anyone knows. Optional, and flagged against the original judgment if it does happen. The product calls this a falsifier.
It is the difference between a prediction and an opinion, and it is what makes it possible to check later whether people were right for the right reasons.
When two people record different positions on the same decision, both are kept, by name, until somebody changes their mind.
An objection averaged into a single answer throws away the most useful thing in the room. Disagreement is a fact about the company's judgment, not a problem to resolve away.
The position actually adopted, with its terms, and the moment the reasoning behind it was locked.
This is the one part almost every company already keeps, which is exactly why keeping it alone is not enough.
The outcome, added once it is known, including when the original call turned out to be wrong.
An outcome attached to the original prediction, rather than to a version tidied up afterwards, is the only way anyone learns from having been wrong.
Why the systems you already run lose it
Not because they are bad. Because none of them was built to hold what somebody believed.
A CRM keeps the outcome. It records that the account renewed at 260 seats. It has nowhere to put why 260 was the right number, and the field is overwritten the next time anyone touches it.
A document keeps a version. It can be edited afterwards to read better in hindsight, and usually is. A document saying what you now wish you had thought is worse than no document.
A chat thread keeps a conversation. It holds the reasoning for about a week, in fragments, mixed in with everything else, and nobody reads it twice.
A dashboard keeps the numbers. It shows what the figure was, not what anyone concluded from it.
Between them they hold the decision and almost none of the thinking.
Clyreon replaces none of them. It reads facts from those systems and never writes anything back.
Nothing can be edited later
These are properties of how it is built, not settings someone can turn off.
What looks like an edit, such as a changed status, is added to the history instead. What it replaced is still there to read.
Changing your mind records a second judgment, which sits beside the first. What you thought originally, and the day you stopped thinking it, is itself worth knowing.
A decision can be closed, set aside as no longer relevant, or have its evidence removed once a retention period expires. It is never deleted outright. That is the point of the product, not a missing feature.
Nothing is stored twice, so there is no second copy that can drift away from what actually happened.
Ask what the team knew on a given date and Clyreon replays the history and stops there. Facts recorded later are simply not in it, and neither are job titles people did not hold yet. Showing today’s knowledge on a view of the past would claim the company knew something it could not have known.
Not only changes. A record some people can read without leaving a trace is not a record you can trust.
The screens
The whole product, and nothing that is not in it.
Queue
What needs an answer today, soonest deadline first. One team, or all of them.
Records
Every decision, filterable by whether it is open, answered or expired, and by the team that opened it.
Record detail
One decision's whole history: the position and reasoning, any competing position, the facts cited, who owns it, and what happened when.
Evidence
Every recorded fact, on its own, showing whether it still holds and which decisions rely on it. New facts are typed in here when they did not arrive from a connected system.
Accounts
Every customer, project, supplier or team you hold facts or decisions about, each on a single timeline: what was seen, what was decided, and in what order.
Search
Decisions and facts, by their own words.
Integrations
Connect a system, watch whether it is syncing, retry a failure, disconnect it.
Import
Bring an existing decision log in as history, checked before anything is written.
Organisation
How many decisions are open and answered, how often people disagree, how often a stated warning sign actually happened, and how well calibrated each person turns out to be. Every figure clicks through to the decisions behind it.
Admin
People and their permissions, API keys, webhooks, a full export of your data, retention, and the complete access log.
How your information gets in
Any one of them works on its own.
Connect your systems
Twelve connectors, including Salesforce, HubSpot, Zendesk, Jira, Intercom, Planhat, Notion, Slack, Segment, Gmail and Microsoft 365, read from the tools you already run and record what they report. Each one keeps two dates: when the thing happened, and when Clyreon came to know it.
Bring what you already have
A decision log in a spreadsheet, a wiki or a ticketing system comes in as history. Imported decisions keep the dates they were really made on and stay marked as having come from elsewhere, so they never read as something decided in Clyreon.
Start with nothing connected
Open a question, type what you know, take a position, add the outcome when it arrives. That is the whole product, and it needs no integration project first. Connectors make it faster to fill. They are never what makes it work.
All three end up in the same place. A fact typed in by hand and one pulled from a CRM are treated identically, which is why a customer who connects a system in month three does not start over.
What Clyreon deliberately does not do
Better said now than discovered later.
No health score. Clyreon produces no single confident number standing in for reasoning nobody wrote down. That is the thing it exists to replace, and it is not an option you can switch on.
No AI deciding anything. A model can draft a position for a person to review. It can never record a claim of its own. See bring your own AI.
No quiet corrections. A judgment is never edited or deleted, for anyone, for any reason.
More of these, including the ones people ask about most, are on the questions page.