Glossary
Distinguish to understand.
Related concepts with distinct roles. The vocabulary forms a relational system describing the ImoHarmonia conceptual model; these are not legal definitions or proof of operational software.
Relationship does not mean equivalence.
- ProvenanceFact ≠ Evidence
In the proposed model, the data considered about a project must be distinguished from the documentary evidence that substantiates it.
Relates to:- Regulatory scopeNorm ≠ Requirement
The full content of a legal source and the specific requirement applied within a given context should not be treated as identical.
Relates to:- FormalisationRequirement ≠ Computable rule
Representing a requirement as a deterministic rule is a distinct step; not all regulatory requirements admit computable formalisation.
Relates to:- EvaluationRule ≠ Verification
A computable rule and its specific application within an evaluation delimited to a project must remain distinct.
Relates to:- Technical outputVerification ≠ Result
The model separates technical evaluation from its output and from the boundaries and grounds that accompany that output.
Relates to:- Human sovereigntyResult ≠ Decision
The output of a verification does not substitute professional interpretation or the administrative decision of the competent authority.
Relates to:
Every definition requires context.
Specialised regulatory definitions will be presented with cited sources, scope, and domain review. Specific formulas, values, or statutory interpretations for individual projects are not published here.
Missing information must remain explicit. The purpose of the proposed preliminary assessment is to support professional review, never to replace it.