Reference
Glossary
Every word Adduce uses for evidence, themes, briefs, roles, seats and tokens, defined once and in one place, in one sentence each.
Every term this site uses, defined once. Where the app and the pricing page use different words for the same thing, the row says so. Nothing here is a setting you change; the how-to that uses each term is linked at the end.
Terms
The vocabulary follows the shape of the product: records become evidence, evidence clusters into a theme, a theme argues a brief, and all of it lives inside a project inside a workspace.
| Term | What it means |
|---|---|
| Admin | One of the two workspace roles. An Admin holds every workspace capability, and is a Lead on every project without being added to one |
| backfill | How far back a source's first sync reaches. It varies by tool, and each Connect page states its own |
| brief | The argument for one decision: the problem, the change it proposes, what is still open, and what was decided, with the theme it came from attached |
| Chat | Where you ask a question of one project and get an answer that cites the evidence behind it, rather than answering from general knowledge |
| Commenter | The project role that can read everything and leave comments, and change nothing |
| confidence | The grade on a finding. The server computes it from how many separate sources back the finding and whether it has recurred; the model's own judgement of evidential strength is a ceiling it cannot exceed |
| credits | The word the pricing page uses for tokens. Same unit, two audiences: the app says tokens, the pricing page says credits |
| decision | What a brief records once its team has settled the question the brief argues |
| destination | A tool Adduce writes to. A destination has no sync and produces no evidence, and nothing it holds is ever read back in |
| Editor | The project role that can edit content, manage the project's sources and use Chat, but not manage its members |
| Emerging | The label a theme carries instead of a score when it holds two pieces of evidence or fewer — too thin to grade honestly |
| evidence | One record read from a source: a survey answer, a support conversation, an error, a line someone said on a call |
| finding | Something Adduce has flagged against a theme, carrying a confidence and a severity, which are independent of each other |
| Investigate | The setting that makes Chat test hypotheses against the evidence and report a verdict on each, rather than looking one thing up |
| investigation | A saved Investigate result: the question, the answer, the quotes behind it, and every hypothesis tested |
| Lead | The project role that holds everything in a project, including its members, its settings and deleting it |
| licence | See seat |
| Member | One of the two workspace roles. A Member holds nothing at workspace level and works only in the projects they have been added to |
| open question | A question a brief leaves open, which can be assigned to a person so the brief becomes something the team owes an answer to |
| Overview | The workspace dashboard, which collects what needs you across every project as a ranked list |
| Pipeline | The project view that shows how much evidence arrived, and from which source |
| project | One product area, with its own sources, evidence, themes and briefs. Nothing crosses between projects |
| Pulse | The project dashboard: what moved, the themes and briefs that changed, and who is on the project |
| roadmap | Where planned work sits once a theme or a brief has become something the team intends to do |
| seat | A licence, not a headcount. Each member and each outstanding invitation holds one until it is released |
| sentiment | Whether the quotes in a theme read as Positive, Neutral or Negative — how the evidence feels, not how much of it there is |
| signal | Another word for one piece of evidence. A source's row in the list shows its signal count: the pieces of evidence taken from it so far |
| source | One connection between a project and a tool Adduce reads. Every piece of evidence arrived through one |
| strength | How much of a project's evidence sits in one theme, as a value out of 100 and a bar, relative to every other theme in that project |
| sync | One run of a source. Sources sync once a day, and Sync now runs one immediately |
| synthesis | The step that clusters recurring evidence into themes and scores them, run after each sync |
| theme | A cluster Adduce built from your evidence — the same thing said in different words, in different places — with a strength and a sentiment |
| token | The unit Adduce charges AI work in, spent by Chat, Investigate and synthesis. The balance sits under the composer in Chat |
| token cap | A spending limit, set for the workspace as a default and overridable for one person. Requests stop at the cap rather than overrunning it |
| verdict | The band at the top of a theme — Improvement recommended, Monitor this theme or No improvement needed — with the reason beneath it |
| Viewer | The project role that can read everything and do nothing else |
| Watcher | What checks a project's metrics each night and records anything that crossed its noise floor as a run under Watch |
| workspace | Your organisation in Adduce: the boundary that billing, membership and roles are set at. Projects live inside it |
Two words for the same thing
Four pairs recur. Each names one thing twice, so a page that uses the other word is not describing something else.
| In the app | Elsewhere | What to know |
|---|---|---|
| tokens | credits, on the pricing page | The same unit. The pricing page speaks to someone choosing a plan; the app speaks to someone spending one |
| seat | licence | The same thing. A seat is what you buy; a licence is what a member or an outstanding invitation holds |
| workspace | organisation | The same thing. Most of the product says workspace; a few settings screens say organisation |
| Admin | owner | The same role. The Delete workspace card says an owner can restore the workspace, where every other screen says Admin |
Related
- What Adduce does — the same vocabulary, in the order it happens.
- Read a theme — strength, sentiment, evidence and verdict, on a real theme.
- Roles and permissions — Admin, Member, Lead, Editor, Commenter and Viewer in full.
- Integrations A–Z — every source and destination the vocabulary above points at.
Security and data
Where a connected tool's credential is kept, what Adduce stores and what it never does, how long each thing is held, and who else processes it.
"Connection failed" when adding a source
Read the code the add-source wizard shows when a connection test is rejected, correct the field it names, and run the check again.