# Glossary The kit's own words, as Candor's docs use them. Each is defined once, here. Web page: https://candor.themethodic.com/glossary.md ## Terms ### Two-turn rule The order Candor's planning screens follow: in the first turn the agent asks its questions (ClarifyingQuestions: choices or a line of text) and the person answers; in the second it proposes a plan (Plan, proposed) that the person can edit, accept or send back. The agent doesn't plan before it has asked, and a plan doesn't run before it is accepted. See: [clarifying-questions](https://candor.themethodic.com/docs/clarifying-questions.md), [plan](https://candor.themethodic.com/docs/plan.md), [plan-build-review](https://candor.themethodic.com/docs/plan-build-review.md). ### Blast radius What a step of a plan would touch if it ran: each thing it creates, updates, deletes or only reads, with line counts where a diff exists. It is measured, or it is unknown and says why. It also lists the kinds of thing the agent couldn't read, because those can't be ruled out. Candor never estimates one. See: [blast-radius](https://candor.themethodic.com/docs/blast-radius.md), [review-canvas](https://candor.themethodic.com/docs/review-canvas.md). ### Drift How a running plan has left the plan the person approved, step by step: a step was added (not in the approved plan), skipped (approved, not done) or changed (done differently, with the approved version shown). It comes from your app's own records; Candor never works it out by itself. See: [plan](https://candor.themethodic.com/docs/plan.md), [review-canvas](https://candor.themethodic.com/docs/review-canvas.md). ### Change hash The SHA-256 of a change in one canonical form (object keys sorted at every depth), the same in the browser and on the server. An approval is made against a hash, so the server can check that what runs is the change the person saw. If the person edits the change before allowing it, the hash is worked out again for the edited version. See: [approval-request](https://candor.themethodic.com/docs/approval-request.md), [change-hash](https://candor.themethodic.com/docs/change-hash.md), [approval-gated-change](https://candor.themethodic.com/docs/approval-gated-change.md). ### Calm level What Candor's motion does for a person whose operating system asks for reduced motion: the highest-precedence setting, above the app's own motion level (`none`, `calm`, `subtle` or `expressive`) and the brand file. A theme tunes how a change looks, never when it happens, so nothing depends on seeing the motion. See: [motion](https://candor.themethodic.com/docs/motion.md), [theme](https://candor.themethodic.com/docs/theme.md). ## The honesty rules Every item keeps these. The full text of each, with why it matters and where the kit enforces it, is at https://candor.themethodic.com/principles. ### Model output is text, never markup A model can be talked into writing a link, a script or a fake button. If the interface renders what it writes, whoever controls the prompt controls the page. Anchor: https://candor.themethodic.com/principles#model-text-is-text ### Unknown stays unknown A guessed duration, cost or count looks exactly like a measured one. People make decisions on numbers, so a number that wasn't measured shouldn't be shown as one. Anchor: https://candor.themethodic.com/principles#unknown-stays-unknown ### A control that can't be used says why A greyed-out button with no explanation sends people looking for help, or around the rule. Saying why turns a dead end into a next step. Anchor: https://candor.themethodic.com/principles#locked-says-why ### Nothing is pre-selected in a decision A default in an approval nudges people to agree without reading. When an agent asks to change something real, the person should choose, not confirm. Anchor: https://candor.themethodic.com/principles#nothing-preselected ### Approve the exact change An approval given for one change shouldn't apply to another. If the change moves after someone looked at it, their approval no longer means what they meant. Anchor: https://candor.themethodic.com/principles#approve-the-exact-change ### Reasoning is believed, not verified A model's account of why it did something is a claim, not evidence. Presenting it as fact gives it more weight than it has earned. Anchor: https://candor.themethodic.com/principles#reasoning-is-believed ### The agent is always named, by the app People need to know who did something, and a model shouldn't get to choose its own name or speak as the system. Anchor: https://candor.themethodic.com/principles#agents-are-named ### Say what can and can't be undone Before something destructive, the question people need answered is “can I take this back?”. Hiding the answer in a confirmation they'll click through doesn't help. Anchor: https://candor.themethodic.com/principles#say-what-can-be-undone ### Motion never says something false A tick that appears before the clipboard answers, or a bar that fills before the work is done, teaches people that the interface's signals mean nothing. Motion that reports something is a claim, and a claim made early is a false one. Motion that only makes an interface feel alive claims nothing, and that is the brand's choice. Anchor: https://candor.themethodic.com/principles#motion-follows-the-outcome