Glossary

Canonical glossary for jinflow. Generated from terminology/terminology.yaml.

◆ marks first-class citizens — terms actively used in the model and in every conversation about jinflow. The other entries are architectural or substrate concepts that support the model but aren’t in daily use.

Product Terms

◆ 50cents

A tenant-level kind of Subject Matter — knowledge specific to this tenant’s reality, not shared with other tenants of the pack. Display label ‘50cents’ (untranslated); the tooltip ‘Field Note’ provides a per-locale gloss for non-domain readers.

Aliases: 50cents, fiftycents, fifty-cents, tenant-level subject matter, tenant wisdom, field note

Anchor

One of the two universal substrate slots every pack instantiates: an Anchor names who or where (Material, Case, Person, Parcel — pack-specific). Reserved engine vocabulary; the shape is fixed, the names vary by pack.

Aliases: anchor, who, where

Contract

DE: Vertrag | FR: Contrat

A JSON schema that defines the required fields, types, and constraints for a layer’s output, enforcing interface stability.

Aliases: contract, vertrag, contrat, schema

◆ Contributing Factor

An individual causal element that composes an Explanation. May adopt a Verdict from the Sense 14 chain as a starting point and signed by an expert. Per Sense 15.

Aliases: contributing factor, factor, mitwirkender Faktor

◆ Data

The name of the diamond that carries what the data says. The diagnostic cascade — Signals scan, Perspectives aggregate, Theses ask, Verdicts judge — all runs here, emitting Findings and Verdicts into Understanding. Theses and Verdicts themselves are pack-shipped Knowledge patterns engaged when Data runs. One of the three feeders into Understanding. Per Sense 14.

Is: one of the three feeders into Understanding, carrying what the data says

Is not: raw source data. Data (the name) covers signals + perspectives + theses + verdicts running against a validated substrate (Sense 42’s Garden)

Aliases: data, analysis, analytical tier

◆ Direction

The steering noun inside Progress — the attitude, goals, intent that suggestions, interventions, and scenarios are validated against. More employee happiness, or less salary spend? Direction is what tells you which Suggestion to act on when several are technically valid. Whether Direction is a peer of Suggestion or a quality each Suggestion carries is an anatomy question held open for its own working session.

Is: the steering concept inside Progress — what makes one Suggestion the one to act on

Is not: the same as a Suggestion. Direction filters or shapes suggestions; it doesn’t replace them

Aliases: direction, intent, bearing, strategic direction

◆ Dossier

A human-curated narrative grouping of related Subject Matter — the story layer on top of atomic expert knowledge.

Is: a narrative wrapper that connects related Subject Matter

Is not: a perspective or automated grouping. Dossiers are hand-curated by a named curator

Aliases: dossier, bitbundle, bundle, use case

Entity

DE: Entität | FR: Entité

A domain object with identity — the thing being examined. Every pack defines its own Anchors (who/where) and Facts (what happened, when). The names vary across packs; the shape (Anchor + Fact) is reserved engine vocabulary.

Aliases: entity, entität, entité, dimension

Evidence

DE: Evidenz | FR: Évidence

A weighted reference to a signal or Subject Matter entry that contributes to a thesis evaluation. Each evidence link has a role (primary, supporting, context, counter).

Is: a scored link between a thesis and its supporting/contradicting data

Is not: the raw data itself. Evidence is the connection, not the finding

Aliases: evidence, evidenz, preuve, evidence chain

Evidence Score

DE: Evidenz-Score | FR: Score d’évidence

A numeric value (0.0–1.0) that summarizes the total weighted evidence for a thesis, determining its thesis status.

Aliases: evidence score, evidenz-score

◆ Explanation

A signed causal theory composed of Contributing Factors that may adopt a Verdict as a starting point. Per Sense 15.

Aliases: explanation, causal theory, signed explanation

Fact

One of the two universal substrate slots every pack instantiates: a Fact names what happened, when, and according to whom (BillingEvent, Assignment, Harvest — pack-specific). Reserved engine vocabulary; the shape is fixed, the names vary by pack.

Aliases: fact, event, observation-event, what happened

◆ Finding

DE: Befund | FR: Constat

A single anomaly or pattern instance detected by a signal — with a continuous score (0-100), affected entity, and impact assessment.

Is: a specific, attributable detection event

Is not: a “result” or “alert.” Use “finding” consistently — never “signal result”

Aliases: finding, signal instance, befund, résultat, constat

Health Score

DE: Gesundheitsscore | FR: Score de santé

An entity-level numeric score (0–100) produced by perspectives, aggregating scores and finding count across multiple signals.

Aliases: health score, gesundheitsscore

Impact

DE: Auswirkung

The estimated exposure associated with a finding, expressed as a value with unit and dimension. Generalizes the former money_at_risk field to cover financial, operational, quality, cultural, and strategic effects.

Aliases: impact, money at risk, risikobetrag, montant à risque, money_at_risk, mar, auswirkung, exposure

Instrument

Generic term for any declarative analytical artifact: signal, perspective, thesis, verdict, Subject Matter, or Dossier.

Is: the umbrella term for the six artifact types

Is not: used in user-facing UI. The Explorer shows signals, theses, etc. by their specific names

Aliases: instrument, artifact, artefakt

Interpretation

FR: Interprétation

A human-readable explanation of a finding — what happened, why it matters, and what to look at next.

Aliases: interpretation, interprétation, erklärung

◆ Intervention

A committed, structured action that changes the organisation’s state. Second link in the Sense 19 Progress chain (Suggestion → Intervention → Scenario → Simulation). Replaces the legacy term ‘Treatment’.

Aliases: intervention, treatment, action

◆ Knowledge

The name of the diamond that carries what the system already holds — before Data ever runs. Two kinds of inhabitants: Subject Matter (always-on: Wisdom from the pack, 50cents from the tenant, Dossiers grouping them) and activatable patterns (opt-in: Theses and Verdicts shipped pre-formed by the pack). Every artifact carries a provenance state (pack-original, pack-modified, tenant-original). One of the three feeders into Understanding.

Is: one of the three feeders into Understanding, carrying what the system already holds

Is not: the tacit knowledge in someone’s head. Knowledge in jinflow is codified — either as Subject Matter or as activatable patterns

Aliases: knowledge, expertise, subject matter expertise

◆ Lens

A declarative queryable view — a named slice of the data with its preset filters, layout, and entity focus. Per Sense 27.

Aliases: lens, queryable view, viewport

◆ Observation

A signed notice by a named person about the reality of a tenant. The Observation is the entity, with Explanation and Contributing Factor as facets it carries — Contributing Factors cite specific Findings or Verdicts, grounding the narrative in Understanding. Sits in the Observations name of the diamond (Sense 15).

Aliases: observation, signed observation, strategic observation

◆ Observations

The name of the diamond that carries what humans notice. Signed notices by named people, with state (suspected → validated / refuted / inconclusive → resolved). The Observation is the entity; Explanation and Contributing Factor are facets it carries. One of the three feeders into Understanding. Per Sense 15.

Is: one of the three feeders into Understanding, carrying what humans notice

Is not: the same as an Observation (the entity). Observations names the layer; Observation names the artifact

Aliases: observations, strategy, strategic tier, notice, notices

Pass

A capability token attached to a Principal that gates what they can read, write, and run on a tenant. Per Sense 25.

Aliases: pass, capability, role

Passport

FR: Passeport

Everything the platform knows about a DEFINITION — a column or a term: its meaning, type, unit, standard, lineage. Opens on hover or a deliberate keystroke.

Aliases: passport, column passport, term passport, spaltenpassport, passeport

◆ Perspective

DE: Perspektive

An entity-level health score aggregating findings from multiple signals. Perspectives answer: “How healthy is this entity overall?”

Is: a structured, multi-signal aggregation with scoring rules

Is not: a subjective interpretation. Perspectives are deterministic given their source signals

Aliases: perspective, assessment, bewertung, évaluation

◆ Portrait

DE: Porträt

A likeness of ONE subject — the telling fields of a single feature or row, held in one place while the subject travels with your focus.

Aliases: portrait, porträt, portraet, ritratto, feature portrait

Presentation

DE: Präsentation | FR: Présentation

A fullscreen, executive-ready view of a thesis evaluation with narrative, trend charts, and evidence chain visualization.

Aliases: presentation, präsentation, executive brief

Principal

An authenticated identity acting on a tenant — a person, a service account, or an agent. Carries a set of Passes that gate capabilities. Per Sense 25.

Aliases: principal, identity, user, agent

◆ Progress

The name of the diamond that carries what we’ll do. Downstream of Understanding — directed change, not drift. The Sense 19 chain (Suggestion → Intervention → Scenario → Simulation) plus Direction (the attitude, goals, intent that everything is validated against). The forward arm of jinflow.

Is: the forward arm — where validated truth becomes directed change

Is not: any output. Progress is directed change, not drift; every Suggestion traces back through Contributing Factors → Understanding → Data

Aliases: progress, evolution, action, change, downstream

Qty at Risk

DE: Risikomenge | FR: Quantité à risque

The estimated quantity exposure of a finding — how many units are affected. Complements impact for volume-sensitive signals.

Aliases: qty at risk, risikomenge, quantité à risque, quantity

Registry

FR: Registre

A dbt model (SQL table) storing metadata for all instruments of a given type, generated by the compiler from YAML definitions.

Aliases: registry, registre, register

Report

DE: Bericht | FR: Rapport

A structured document generated from pipeline data. Types: data quality, financial risk, analytics readiness, and health.

Aliases: report, bericht, rapport, pdf

Risk Tier

DE: Risikostufe | FR: Niveau de risque

A tiered financial risk classification assigned to each signal, used to prioritize findings in reports and the Explorer.

Aliases: risk tier, risikostufe, niveau de risque

Root Cause

DE: Grundursache | FR: Cause racine

The underlying reason why a problem exists. Structured into six categories: process, system, data quality, behavioral, structural, external.

Aliases: root cause, grundursache, cause racine, ursache

◆ Scenario

A counter-factual built by applying one or more Interventions to a branched tenant AFS and rebuilding the KLS against it. Third link in the Sense 19 Progress chain. Runs CLI-first via jin scenario create / build / list.

Aliases: scenario, what-if, branch

Score

DE: Punktzahl

A continuous numeric value (0-100) quantifying the significance of a signal finding. Replaces the former discrete severity levels (high/medium/low). Display labels are derived from score ranges for human readability.

Aliases: score, severity, schweregrad, sévérité, punktzahl, significance score

◆ Signal

A declarative analytical query that detects a specific pattern in Gold data. Signals produce standardized findings with a continuous score (0-100), impact, polarity, and direction.

Is: a repeatable, question-driven analytical intervention with rich output metadata

Is not: an ad-hoc query or a report. Signals are defined declaratively, compiled to SQL, and produce contract-compliant output

Aliases: signal, probe, sonde, diagnostik

◆ Simulation

The realised run of a Scenario — the rebuilt KLS plus its findings, theses, and verdicts on the counter-factual data. Fourth link in the Sense 19 Progress chain.

Aliases: simulation, run, modelled outcome

◆ Subject Matter

An atomic, attributed piece of subject matter expert knowledge — a single statement, insight, or known exception contributed by a named expert.

Is: structured, first-class expert knowledge with optional data validation

Is not: a comment, annotation, or wiki page. Subject Matter is versioned artifact with identity, lifecycle, and attribution

Aliases: subject matter, smebit, statement, check, expert knowledge, expertenwissen, connaissance

◆ Suggestion

The first link in the Sense 19 Progress chain (Suggestion → Intervention → Scenario → Simulation): a proposed change in response to a confirmed Verdict, not yet committed to action.

Aliases: suggestion, hint, recommendation

◆ The jinflow

DE: Das jinflow | FR: Le jinflow

The mental model of the product. Five names — Observations, Knowledge, Data, Understanding, Progress — arranged as a diamond around Understanding at the centre. Captured in one sentence: jinflow fosters Progress by gaining Understanding through Observations, Knowledge, and Data.

Is: the canonical diagram of how Observations, Knowledge, Data, Understanding, and Progress relate

Is not: a pipeline or a hierarchy — none of the five names sits above any other; they hold each other in tension

Aliases: the jinflow, jinflow, diamond, raute, losange, hourglass, sanduhr, sablier, pyramid, pyramide, stack, analytical stack, analysis, strategy, expertise

◆ Thesis

DE: These | FR: Thèse

A testable business question evaluated against signal evidence. Theses translate technical findings into CFO-ready language. Status: confirmed, plausible, not observed, insufficient data.

Is: a testable business question with evidence scoring

Is not: a guess or assumption. Every thesis is grounded in signal findings

Aliases: thesis, hypothesis, these, thèse, hypothese, hypothèse

Thesis Status

DE: These-Status | FR: Statut de thèse

The per-tenant evaluation of a thesis or a Subject Matter Check (Level 1). Status: confirmed, plausible, not observed, or insufficient.

Is: a deterministic evaluation result

Is not: a finding (findings come from signals; thesis status comes from the evidence chain)

Aliases: thesis status, verdict, verdikt, urteil

◆ Understanding

The centre of the diamond. The shared currency where Observations, Knowledge, and Data agree on what’s true. Two shapes: Findings (atomic — one row, one observation) and Verdicts (aggregate — one row per tenant × thesis). Every feeder writes here; Progress draws from here.

Is: the truth-bearing centre — findings + verdicts

Is not: a report or a dashboard. Understanding is the shared currency between feeders and Progress, not a display surface

Aliases: understanding, insight, resolution, shared currency

◆ Validation

The ratification moment — the gate that lets an Observation move from suspected to validated (or refuted / inconclusive) by testing it against Understanding. Validation is the prerequisite for an Explanation to be authored: no Explanation may be written before its Observation is validated. Per Sense 15.

Aliases: validation, ratification, empirical proof

◆ Verdict

DE: Verdikt

A structured root-cause explanation for a confirmed thesis — root cause category, confidence, and recommendation. Distinct from a thesis status (confirmed / plausible / not observed / insufficient), which is also colloquially called a thesis verdict.

Is: a causal explanation with confidence scoring and actionable recommendations

Is not: a treatment or action — verdicts explain why, they don’t prescribe next steps (that’s the Treatment layer)

Aliases: verdict, diagnosis, verdikt, diagnose, diagnostic

◆ Wisdom

A pack-level kind of Subject Matter — knowledge codified at the pack and true across every tenant of that pack. Display label ‘Wisdom’ (untranslated); the tooltip ‘Field Note’ provides a per-locale gloss for non-domain readers.

Aliases: wisdom, pack-level subject matter, pack wisdom, field note

Architecture Terms

AFS

Artefact Store. The per-tenant git repository holding every declarative artefact: signals, theses, verdicts, Subject Matter, Dossiers, lenses, pipeline.yml, entities, contracts. The source of truth for what should be computed.

Aliases: afs, artefact store, framework store

Atelier

The Explorer’s writable surface for AFS artefacts. Six edit surfaces — signals, theses, verdicts, perspectives, Subject Matter, Dossiers — each validating against the pack contract and routing every save through the Scribe. Per Sense 29.

Aliases: atelier, workshop, writable explorer

Bell

The pub/sub channel between writers (make, Atelier, evolve) and readers (the Explorer’s Inbox). Rings persist in the KLS; per-Principal resolutions persist in the SIS. Every commit through the Scribe boundary can raise a ring. Per Sense 33.

Aliases: bell, ring, pub-sub channel

Bronze

Raw intake layer. Immutable copy of source system data — traceability over correctness. No interpretation, no filtering.

Aliases: bronze

Compilation vs Build

DE: Kompilierung vs Build

Two distinct phases: Compile (YAML → SQL, code generation) and Build (SQL → DuckDB, per-tenant execution).

Aliases: compile, build, kompilierung, compilation

Course

Proposed (The Courses, docs/design/the_courses.md, 2026-07-23). An additive processing block that adds one contract on the shoulder of the prior course, never masking a lower one. Course 0 is Gold (the base build); course 1 is signals; course 2 is theses. A course reads the prior course’s complete KLS as a typed input and is a pure KLS-to-KLS build — course 0 alone ingests Delivered data. One of the three coordinates (generation, course, variation) that identify a KLS.

Aliases: course, course 0, processing block, build course

DLZ

Data Landing Zone. The trust boundary for source data: every CSV crossing it is declared in pipeline.yml, pinned by SHA-256, verified on every run, and logged in an append-only extract_log.jsonl. Per Sense 31 The Inlet.

Aliases: dlz, data landing zone, source intake

Domain Pack

A self-contained analytical framework for a specific industry. Each pack bundles signals, perspectives, theses, verdicts, Subject Matter, dbt models, contracts, and source-system adapters.

Aliases: domain pack, paket

DPH (Domain Pack Hub)

The Domain Pack Hub — where the Domain Packs live, and the name jin status gives the pack side of its three-party drift view: AFS (the tenant instance) ↔ DPH (the pack it was created from) ↔ engine.

Aliases: dph, domain pack hub, packhub, pack hub

Ephemeral Database

DE: Ephemere Datenbank | FR: Base de données éphémère

The DuckDB file (dev.duckdb) is disposable — rm + rebuild recreates everything from CSVs. The database is a derived artifact.

Aliases: ephemeral, duckdb, dev.duckdb

Extraction Contract

DE: Extraktionsvertrag | FR: Contrat d’extraction

A pipeline.yml file at the tenant AFS root that lists every file crossing the extract layer with a SHA-256 pin, source type, and expected schema. The configuration IS the contract, and the contract is the audit trail.

Aliases: pipeline.yml, extract contract, trust boundary contract

Generation

FR: Génération

A delivery of source data — a new generation of the Delivered stratum — arriving anywhere from yearly to near-realtime. Already real in the pipeline as gen00 dated members (generational OPALE delivery). A new generation changes no configuration, but every course and variation reprocesses it into a new generation of KLSs. One of the three coordinates (generation, course, variation) that identify a KLS. Not a course: generation is the data (temporal) axis, course is the build-depth axis — historically conflated, separated by The Courses (docs/design/the_courses.md).

Aliases: generation, gen00, data delivery, delivery, generational

Gold

Consumption layer. Source-system-agnostic views filtering Silver to is_valid = true. This is the product contract — signals operate exclusively on Gold.

Aliases: gold

Heartbeat

The loop between the Explorer’s mutable workspace (SIS) and the durable git-backed AFS. Three beats live today: SIS-cell hydration into KLS, Atelier writes via the Scribe, and jin publish draining SIS into AFS commits. Per Sense 21.

Aliases: heartbeat, pulse, system rhythm

Inspect

Read-only view of the extraction surface declared in pipeline.yml. Renders the contract, verifies SHA-256 hashes, and reports source-file status without ever running extraction.

Aliases: jin inspect, jinflow inspect

jinflow

The analytical engine: CLI, compilers, validators, Explorer, and orchestration. Domain packs plug into jinflow to provide industry-specific analytics.

Aliases: jinflow, core, erp, numetrix layer

KLS

Knowledge Store. A per-tenant DuckDB file containing every Gold table, every signal_findings, every thesis_verdict, every verdict_finding, plus the AFS as an embedded zip archive. The KLS is the built picture — read-only, snapshottable, immutable once frozen. Sole output of jin make, sole input for jin explore.

Aliases: kls, knowledge store, built picture

Make

The single build command. Phase 0 extracts source data under the pipeline.yml contract; Phase 1d publishes pending SIS notes and bookmarks into the AFS; the remaining phases enrich, compile, and run dbt deterministically from the complete AFS to produce the KLS.

Aliases: jin make, jinflow make

Medallion Architecture

DE: Medallion-Architektur | FR: Architecture Medallion

The Bronze → Silver → Gold layering pattern, based on the medallion architecture popularized by Databricks. Each layer has a strict responsibility: structure, validation, consumption.

Aliases: medallion, medal, medaillon, bronze silver gold

Operating Mode

DE: Betriebsmodus | FR: Mode opérationnel

One of five deployment topologies: Local, Proxy (P2P2P), Cloud (R2), Semi-Cloud, Make-as-a-Service. Same product, different placement of AFS, KLS, SIS, and the make runner.

Aliases: deployment mode, deployment topology

P2P2P

Peer-to-Peer-to-People. Deployment mode where the KLS stays on the data owner’s machine and the cloud Explorer routes queries via a tunnel. Your data. Your machine. Their browser.

Aliases: peer-to-peer-to-people, proxy mode, data sovereignty

Phase

An internal build step of a single course — extract, sync, validate, enrich, compile, build, materialize, inspect. make already names these phase_0 through phase_4. A phase is not one of the identifying coordinates: (generation, course, variation) identify a KLS, while phases produce it. Course 0 alone carries the ingestion phases (it touches Delivered data); later courses are pure KLS-to-KLS.

Aliases: phase, build phase, make phase

Rebuildable

DE: Wiederherstellbar | FR: Reconstructible

A table or view that can be fully recreated from source files (CSVs) and YAML definitions at any time.

Aliases: rebuildable, rebuild, wiederherstellbar

Scribe

The attribution layer at every AFS write boundary. Each boundary (make, Atelier, evolve, publish, Bell, action-runner, cloud-make) routes its commits through a per-layer resolver: tenant jinflow.yml → ~/.jinflow/config.yml → engine jinflow.yml. Every Atelier save and every Beat 3 publish carries Scribe attribution. Per Sense 38.

Aliases: scribe, attribution, commit author

Silver

Validated facts layer. Normalized, type-cast, with is_valid flag and invalid_reason. Invalid rows are flagged, not dropped.

Aliases: silver, silber, argent

SIS

System Information Store. A per-tenant DuckDB file holding operational state: notes-in-progress, bookmarks, bell events, scenario state, transient drafts. The Explorer owns its write path exclusively.

Aliases: sis, system information store, workspace

Source Taxonomy

DE: Quell-Taxonomie | FR: Taxonomie des sources

The classification of the six source types that can cross the extract layer: curated spreadsheet, system export, delimited file, API pull, database query, and flat drop. Each has its own governance rules.

Aliases: six source types

Source-System Dispatch

DE: Quellsystem-Dispatch | FR: Dispatch système source

The macro-based mechanism that maps source-system-specific column names (OPALE, SAP, Navision) to the canonical nuMetrix schema.

Aliases: dispatch, source system, quellsystem, opale, sap, navision

Sovereignty Principle

DE: Souveränitätsprinzip | FR: Principe de souveraineté

Data sovereignty means the owner decides, moment by moment, whether their data is accessible. The decision is physical, not administrative. You don’t revoke a permission — you unplug.

Aliases: data sovereignty, physical access control

Tenant

DE: Mandant | FR: Locataire

A business or organization running jinflow against its own data — typically built on a domain pack. Each tenant is isolated in its own DuckDB schema, defined by tenant.yml in the live root.

Aliases: tenant, mandant, locataire, business, organisation, organization

The Cycle

DE: Der Zyklus | FR: Le Cycle

The closed loop of jinflow’s four verbs through three stores: make builds (AFS→KLS), explore reveals (KLS+SIS), evolve drafts (AFS+KLS→AFS), publish commits (SIS→AFS). The Jinflow gives the shape; the Cycle gives the motion.

Aliases: the cycle, cycle, loop, motion

The Double Circle

DE: Der Doppelkreis | FR: Le Double Cercle

The build read as two independent circles that touch at one point: the River (data → Gold) and the Garden (Gold → findings). They share exactly one membrane — the Gold contract — carrying two signals: the contract changed, and new data arrived. Instruments read Gold only, so the circles never entangle and one River can nurture many Gardens, each on its own clock. Per Sense 59.

Is: the two-cycle shape of make, meeting only at the Gold contract

Is not: one monolithic DAG — that is how make runs today; the Double Circle is the shape it wants to take

Aliases: double circle, two cycles, river and garden, gold contract

The Garden

DE: Der Garten | FR: Le jardin

The post-Gold half of the Landscape. A tenant’s analytical instruments — signals, perspectives, theses, verdicts, Subject Matter, Dossiers — rendered as a navigable topology. A garden is tended, not built: you can see what’s growing, what’s overgrown, what hasn’t bloomed yet.

Aliases: garden, garten, jardin

The Landscape

DE: Die Landscape | FR: Le Landscape

The umbrella pipeline-shape view of a tenant, composed of two halves: the River (sources through Bronze → Silver → Gold) and the Garden (the analytical instruments that consume Gold). Per Sense 42 The Landscape; renamed from ‘The Pipes’ in May 2026.

Aliases: landscape, the landscape, pipeline graph, pipeline view, system overview

The River

DE: Der Fluss | FR: La rivière

The pre-Gold half of the Landscape. A tenant’s data pipeline from source CSVs through Bronze → Silver → Gold, rendered as a navigable flow. Together with the Garden, the River makes up the Landscape (Sense 42).

Aliases: river, fluss, fleuve, data flow, ingestion view

Variation

Proposed (The Courses, docs/design/the_courses.md, 2026-07-23). The same course, differently configured — a saved or declared configuration of a course’s block (Sense 43 config). Several variations of one course fan out several KLSs at the same (generation, course). A variation crystallizes when its config is saved/declared; adjusting a config in place without saving is the Lab / L4 transient override (‘playing around’), which has no name and touches neither the AFS nor a build. One of the three coordinates (generation, course, variation) that identify a KLS.

Aliases: variation, variant, variante, config variant