Shared vocabulary
Glossary, site and application
A prospect reads “permanent control” on this site, then opens the application and must find the same word for the same thing. This glossary fixes the vocabulary on both sides: the site publishes first, the application refers to it.
4
- 4D entitlement
- Access right along four dimensions: role × organisational scope × domain × confidentiality level. Activating a domain is an entitlement, not a code variant.
C
- Campaign
- A domain's scheduling: goal, scope, period, population, expected tasks, success criteria and owners. One-off or recurring.
- Corrective action
- A tracked response to a gap: owner, deadline, priority, cause, expected proof and final validation — distinct from the execution. Closing a critical action requires a separate validation.
D
- Delivery lot
- A wave of delivery of a domain on the engine. The site marks a domain “partly covered” when only part of its requirements is covered; a “partly covered” domain announces no further lot. Each domain page says, requirement by requirement, what is covered, partial or not covered — nothing is announced before it ships.
- Domain
- One of the seven business fields of the requirements specification: compliance, permanent control, quality, audit, network animation, commercial performance, training and competencies. A configuration of the engine — in v1.5, five ship end to end (compliance, permanent control, quality, audit, network animation) and two are partly covered (commercial performance, training).
E
- Engine
- BranchCheck's common core: referentials, campaigns, evaluations, proofs, actions, validations and reporting. The seven domains are configurations of this engine, not separate applications.
F
- Finding
- A typed outcome of a control or an audit: observation, recommendation, non-conformity, incident or critical finding. Follows a proof chain to an independent validation.
- Four-state evaluation
- Every item is judged in one of four states: compliant, non-compliant, not applicable, missing data. An aggregation that conflates them is a blocking defect.
G
- Gap
- The distance between what is expected (referential, objective) and what is observed. Every gap can generate an action: remediation, coaching or training.
K
- KPI dictionary
- One definition per indicator: name, formula, source, frequency, owner, thresholds, exclusions, validity date. Every score carries its calculation trace.
P
- Proof
- An item collected offline and sealed on submission — geolocated photo, signature, timestamp, integrity hash — verifiable forever, tied to the control point and its author.
R
- Referential
- A versioned set of requirements (regulatory or internal) with criticality, expected proof and effective date. Published, archived and dated — never hard-coded.
S
- Scope
- The organisational boundary of an object or a right: network, region, zone, branch, process, activity. Scores, campaigns and entitlements are always defined by scope.
W
- Workflow
- An object's configurable cycle: draft, submitted, in review, validated, rejected, in progress, late, closed, archived. Transitions and guards (role, justification, proof, signature) are data; everything is logged.
The single source of this vocabulary — the page is authoritative for both repositories.