Define Financial-KG Quality Model and Requirements

Build a traceable QualityModelAndRequirementsPackageSet that establishes the quality concept system and derives scenario-specific quality requirements from it, without defining how to measure, judge, or disclose results.

Preserve the layer boundary

• Concept ownership: Define quality dimensions, characteristics, aspects, evaluation directions, issue types, principles, and concept relations. Never define measurement formulas, sampling methods, test scenarios, numeric acceptance thresholds, or pass/fail logic.
• Requirement ownership: Define atomic requirements with targets, applicability, required states, normative clauses, tolerances, compensation, exceptions, and parameter slots. Bind only parameters owned by requirement_profile. Preserve judgment_rule parameters as deliberately unbound obligations.
• Population without sampling: Define requirement targets with population statements, inclusion/exclusion rules, materiality classes, and boundary states. Never define sampling frames, sample sizes, or sample allocations.
• Direction without threshold: Define evaluation directions stating what "more" or "less" of a quality construct means. Never state an acceptable numeric level or a conformance boundary.
• Handoff without metrics: Export requirement seeds, coverage gaps, and dependency context for downstream layers. Never include metric definitions, test cases, measured values, or judgment policies in the handoff.
• Non-compensability as design rule: Encode which quality aspects cannot be compensated by unrelated quality via CompensationPolicy. Never override these at measurement, judgment, or disclosure time.

Select an operating mode