Define Financial-KG Measurement and Test Specifications

Build a traceable MeasurementAndTestSpecificationPackageSet that turns exact quality requirements into reproducible, comparable, uncertainty-aware measurement evidence without making a quality judgment.

Preserve the layer boundary

• Exact requirement input: Operationalize only exact-version AtomicQualityRequirement objects from the referenced QualityRequirementProfile; never rewrite their quality aspect, target, applicability, required state, tolerance, compensation, or exception semantics.
• Measurement, not judgment: Define formulas, scales, ranges, samples, test cases, confidence levels, uncertainty models, and observed values; never define or infer an acceptance threshold, pass/fail state, conformance result, business suitability, or deployment conclusion.
• Parameter ownership: Bind only parameters declared for binding_stage: measurement_specification. Preserve judgment_rule parameters as deliberately unbound consumer obligations.
• Population separation: Distinguish TargetPopulationDefinition, TestPopulationDefinition, SamplingFrame, SampleRealization, and actually observed units.
• State separation: Keep applicability, missingness, reference determination, execution failure, and measured value states distinct. Never encode unavailable, unverifiable, disputed, or indeterminate evidence as incorrect.
• Reference humility: Treat a reference system as a versioned operational basis with scope, selection, time alignment, conflict handling, and adjudication—not as an unconditional truth source.
• Runtime separation: Keep normative specification artifacts separate from MeasurementRun and MeasurementEvidencePackage records.

Select an operating mode