Support
Glossary
The words this documentation uses, defined once.
In short
One line each for the terms you will meet. The same definitions are used on the landing page.
- Boardroom — the adversarial review stage: an advocate interviews you, then five critic lenses challenge the idea and adjudicate your rebuttals.
- Brief — the advocate's plain-language restatement of your idea, which you ratify before the critics see it.
- Verdict — the round's result: scored dimensions that cite the objections behind them, plus open questions and a next action.
- Register — one list per project of every objection, question, assumption and blocker raised by any panel.
- Vault — the literature workspace: papers, line-anchored reading, the method, notes and the matrix.
- Trace — the link between something in your paper and its source; checked before freezing.
- Freeze / frozen version — a read-only snapshot of a draft with its compiled PDF and SyncTeX file.
- Gate — the rule that drafting is blocked while assumptions are pending.
- Engine — where a model call goes: a cloud API, a local server, or a CLI agent.
- Model ref — a stored choice written as
engine::model; a bare id means OpenRouter. - Record — the
record/folder, tracked in git, which holds your authored work. - Artifact — a notebook output (chart, figure, export) with a stable id, usable in the draft.
- Vault Vision — local detection and reading of tables, figures, charts and equations.
- Mock review — an optional AI review before submission, using the venue's form, labelled "Mock (AI)".
For technical users
Where a term has a specific meaning in the code, the internal registry is authoritative; the definitions here are for readers, not for implementers.