Calliops
FR·EN
Glossary · eight terms

The words Calliops uses, defined

These eight terms recur in the documents Calliops produces and across the rest of this site. They are defined once here, so the same thing carries the same name from one screen to the next.

Traceable spec

A traceable spec is a document where every line names its source: the meeting, the date, the excerpt and the timestamp. What separates it from an ordinary spec is that every claim can be checked without leaving the document.

Product space

A product space is a sealed perimeter: its meetings, its documents, its seals and its members. A team working on two distinct products takes two spaces; an agency takes one per client.

The product space is also how Calliops is billed: the price follows the number of spaces, not the number of people reviewing inside them.

Validation gate

A validation gate is a pipeline step a person has to clear explicitly. Calliops has two across its eight steps: the validation of detected items and the implementation plan.

A gate is not a notification: nothing moves until someone has sealed it.

AI draft

An AI draft is a document written by the model and not yet reviewed. It is marked with a dashed border everywhere it appears, and it cannot be written into Notion while in that state.

Feature

A feature, in Calliops, is the document stating an intent, its value and its source. It is produced at step 05 of the pipeline, once a decision has been extracted, deduplicated and sealed.

docs/features/FEA-114-filtres-file-revue.md

UX constraint

A UX constraint is an interface requirement the spec has to hold: the states, the edge cases, accessibility, the text shown when there is nothing to show. Calliops drafts these at step 06, separately from the intent.

“No card for this filter. Remove the source filter.”

Scope

Scope states what is in the delivery and what waits for the next cycle. It is written at step 07, before the implementation plan, because a plan drafted without a settled scope covers everything and commits to nothing.

Definition of done (DoD)

The definition of done is the list of conditions that make a feature finished: what has to be shipped, tested, written and reviewed. It accompanies the scope at step 07 and serves as the acceptance criterion.

Three filters shipped, state persisted, empty state written, design review done.

Where these terms apply

These definitions describe documents Calliops produces today.

Join the waitlistNext wave · September 2026