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

Demonstrate and transfer

Show what has been verified, state its scope and leave the knowledge required to continue.

01 / 04

Evidence

Definition: An observable, verifiable element that supports a claim within a defined scope.
Nuance: Evidence must state its method, date and limit; it does not turn a local check into a universal conclusion.
Concrete situation: A matching hash establishes that served bytes are identical, not the semantic quality or security of the whole system.
Associated terms: Observation, measurement, scope, method, traceability.
Avoid: Using “proven” without scope, date or method; confusing a statement, illustration and evidence.

02 / 04

Limit

Definition: The explicit boundary of what evidence, a capability, a system or a promise actually covers.
Nuance: Stating a limit does not weaken credibility; it prevents a claim from exceeding what can be defended.
Concrete situation: A PageSpeed measurement for one URL at one time does not automatically qualify every page or future visit.
Associated terms: Scope, condition, unknown, validity, risk.
Avoid: A limit relegated to fine print after an absolute promise; failure to distinguish known from unknown.

03 / 04

Documentation

Definition: Current, organised information that enables people to understand, operate, verify and evolve the system.
Nuance: The presence of files is not enough; documentation must be findable, versioned, connected to reality and tested by its reader.
Concrete situation: A recovery guide states prerequisites, decisions, commands, positive checks and expected failures, then another person runs it.
Associated terms: Memory, decision, version, operations, recovery.
Avoid: Saying “it is documented” because code or a folder exists; a document with no owner or date.

04 / 04

Knowledge transfer

Definition: Transfer of the knowledge, bearings, skills and authority another team needs to act and take over.
Nuance: Delivery is not enough; knowledge transfer is effective when the recipient can understand, decide and act without a hidden dependency.
Concrete situation: The receiving team performs a recovery, explains the decision points and knows where to verify system state without the original author.
Associated terms: Handover, autonomy, capability, documentation, continuity.
Avoid: Equating delivery with knowledge transfer; dropping an archive with no exercise or accountable contact.

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