Decisions

A decision is a choice someone agreed to that changes what people will do or see: picking a vendor, changing a price, dropping a feature, setting a date.

What's kept with each decision

• The choice, in one plain sentence, and the words it was made in.

• Who decided, and when.

• Why, if a reason was given.

• The expectation: what should change because of it. Expectations

• Where it came from: the chat, document, meeting or commit, or the agent that reported it.

Where decisions come from

An AI tool connected over MCP reports decisions as they're made. Exports of past chats, documents, meetings, email and code history fill in the decisions made before. How connecting works

Who can see a decision

On a hosted team, decisions are visible to the team. Each person can change that for themselves: on the Team page, Decisions you file is set to Visible to my team or Only me. The setting applies to decisions that person files from then on, through their AI tools and the console. Decisions already filed keep how they were filed.

A decision filed as Only me is seen only by the person who made it, including by admins. ZeroWidth's dreaming never reads it, and it is left out of exports and team results. Anything that rests on a private decision is hidden with it.

Correcting a decision

A decision that was read wrong is retracted, never quietly edited. The retraction stays in the record with who made it and why, and the decision no longer counts anywhere.

Decisions that relate to each other

Decisions are linked when one carries out, builds on or undoes another. When a later decision might replace an earlier one and that isn't clear, the question goes to a person on the team, and only a person can settle it. Open questions