Koperateur glossary

Precise terms for decisions that hold up

We use these terms to describe observable capabilities, choices and limits. Choose a path: each definition begins with a real situation and states what it commits us to.

Choose a path

01 · Five paths

Choose a path

Nineteen terms structure how we recognise a situation, clarify a choice, decide, retain control, then demonstrate and transfer.

Each path has a stable address, so it can be opened, shared and read independently.

02 · Operational definitions

Retain control

Retain the ability to understand, operate, change, recover and exit across every layer of the system.

01 / 04

Control

Definition: The ability to see, understand, choose, verify, operate, correct, maintain, evolve, recover and transfer a system.
Nuance: Owning technology, locating data or displaying a label is not enough; control is demonstrated through observable capabilities.
Concrete situation: A team can diagnose an incident, restore the service and explain the decision without depending on the original author.
Associated terms: Observability, operations, maintenance, recovery, transfer.
Avoid: Equating ownership, local hosting or individual skill with full system control; “mastery” as the primary translation.

02 / 04

Digital sovereignty

Definition: The practical ability to decide what may be delegated while retaining credible options for control, replacement, recovery or exit.
Nuance: Digital sovereignty is neither absolute autonomy nor an automatic effect of hosting location; it is assessed layer by layer.
Concrete situation: The organisation controls its data and operations, knows which layers are entrusted to third parties and funds a realistic exit path.
Associated terms: Choice, control, dependency, continuity, exit.
Avoid: “100% sovereign” without a scope; inferring sovereignty from European hosting alone.

03 / 04

Partial digital sovereignty

Definition: An honest description of partial control when some system layers still depend on third parties.
Nuance: This Koperateur term describes a trajectory, not an institutional label: it names controlled layers, residual dependencies and the conditions for progress or exit.
Concrete situation: Data, exports and operations are controlled, while a model or critical provider can only be replaced over the medium term.
Associated terms: Layer, progress, residual dependency, transparency, trajectory.
Avoid: A vague claim with no layers or measurement; presenting “partial digital sovereignty” as an official standard.

04 / 04

Reversibility

Definition: A prepared, verifiable ability to switch provider, architecture or operator without unacceptable loss of data, functionality or continuity.
Nuance: An available export is not enough; formats, interfaces, documentation, time, cost and a recovery exercise determine whether exit is real.
Concrete situation: A service exports data and metadata in a usable format, then an exercise measures restoration elsewhere.
Associated terms: Portability, switching, export, recovery, continuity.
Avoid: Equating an export button with a tested exit; promising reversibility with no time or cost.

Put the terms to work

A term matters only when it clarifies action

If your situation does not fit a ready-made definition, that is precisely where scoping begins.

Qualify your situation