{
  "schema_version": "h2kg-chameo-fair-characterization-contract/v5",
  "source_manifest_sha256": "C3A66E75FABDAF61C60949FFC7B0E08AAD324A1F77D6137BDE60FA20797001E6",
  "requirement_count": 13,
  "selection_strata": {
    "analysis_lineage": 1,
    "data_processing": 1,
    "measurement_context": 1,
    "measurement_settings": 2,
    "methodology_description": 1,
    "result_provenance": 1,
    "result_semantics": 2,
    "selected_profile_vocabulary": 1,
    "software_traceability": 1,
    "specimen_preparation": 1,
    "workflow_structure": 1
  },
  "contract_sha256": "1DF11D480C1CC8AFAE618B5C7299C20E4EA0DB9FCD6B6188413B32CC373A352E",
  "selection_protocol": [
    "Enumerate the specimen-to-result information lifecycle present in the sanitized workbook.",
    "Score each scientific relation or value pattern once over the full eight-record population; do not repeat it as global and per-record questions.",
    "Derive every requirement from information present in the application lifecycle and label it by scientific function, never by ontology origin.",
    "Include selected-profile native vocabulary coverage as an explicit scored requirement rather than an unscored post hoc argument.",
    "Generate expected rows from the manifest before executing ontology-specific SPARQL or native-pattern assessment.",
    "Compare deduplicated result sets after normalizing numeric lexical forms only; preserve all other selected values exactly.",
    "Treat numeric parsing and recognized-unit mapping separately from rule-based property/unit compatibility screening.",
    "Disallow local semantic bridge predicates and report shared standards and declared imports separately.",
    "Credit generic native patterns as successful while reporting their semantic specificity separately from specialised native patterns."
  ],
  "inference_scope": "The resulting requirement-satisfaction decisions apply only to these thirteen frozen retrieval, native-pattern, and vocabulary-coverage assessments over eight source records representing seven unique profiles.",
  "conclusion_rules": [
    {
      "id": "r1_chameo_broad_methodology",
      "criterion": "CHAMEO is exact for measurement context, setting identity, preparation, processing, software, analysis lineage, result generation, workflow/task grouping, and technique/occurrence separation."
    },
    {
      "id": "r2_chameo_unique_methodology_patterns",
      "criterion": "CHAMEO supplies specialised workflow/task and technique-description patterns; H2KG can group activities generically but lacks a separate technique-description pattern."
    },
    {
      "id": "r3_h2kg_valued_settings",
      "criterion": "H2KG is exact, while no declared ancestry-compatible path from a CHAMEO measurement-parameter record to a distinct valued scientific characteristic was identified under the benchmark's permitted native-encoding rules."
    },
    {
      "id": "r4_h2kg_individual_results",
      "criterion": "H2KG is exact for individual result/property/bearer associations and parsed numeric values with recognized units, while CHAMEO is not exact for the individual association contract."
    },
    {
      "id": "r5_h2kg_method_specificity",
      "criterion": "H2KG has greater native class coverage at the predefined profile granularity than CHAMEO for the selected source records."
    }
  ],
  "requirements": [
    {
      "id": "b01_measurement_context",
      "question": "Which specimen, instrument, and raw dataset belong to each measurement?",
      "selection_stratum": "measurement_context",
      "assessment_type": "query_based_retrieval",
      "source_basis": "Case identity, specimen field, method family, and raw-data output in the sanitized manifest.",
      "variables": [
        "caseKey",
        "measurementLabel",
        "specimenLabel",
        "instrumentLabel",
        "rawDatasetLabel"
      ]
    },
    {
      "id": "b02_measurement_setting_identity",
      "question": "Which named measurement settings are associated with each measurement?",
      "selection_stratum": "measurement_settings",
      "assessment_type": "query_based_retrieval",
      "source_basis": "All characteristic and instrument fields classified as measurement settings in the sanitized manifest.",
      "variables": [
        "caseKey",
        "parameterLabel"
      ]
    },
    {
      "id": "b03_valued_measurement_setting",
      "question": "Which measurement-setting record denotes which scientific characteristic, with what parsed numeric value and recognized unit?",
      "selection_stratum": "measurement_settings",
      "assessment_type": "query_retrieval_and_native_pattern_assessment",
      "source_basis": "Reported measurement settings with a distinct scientific characteristic, a parseable numeric value, and a recognized unit in the sanitized manifest.",
      "variables": [
        "caseKey",
        "parameterLabel",
        "propertyLabel",
        "value",
        "unit"
      ]
    },
    {
      "id": "b04_preparation_input_output",
      "question": "Which material input and output are connected by each specimen-preparation step?",
      "selection_stratum": "specimen_preparation",
      "assessment_type": "query_based_retrieval",
      "source_basis": "Synthesis and specimen-preparation rows in all eight source records.",
      "variables": [
        "caseKey",
        "processLabel",
        "inputMaterialLabel",
        "outputMaterialLabel"
      ]
    },
    {
      "id": "b05_processing_input_output",
      "question": "Which input and output datasets are connected by each preprocessing step?",
      "selection_stratum": "data_processing",
      "assessment_type": "query_based_retrieval",
      "source_basis": "Preprocessing rows in all eight source records.",
      "variables": [
        "caseKey",
        "processLabel",
        "inputDataLabel",
        "outputDataLabel"
      ]
    },
    {
      "id": "b06_software_association",
      "question": "Which software is associated with each preparation, processing, or analysis step?",
      "selection_stratum": "software_traceability",
      "assessment_type": "query_based_retrieval",
      "source_basis": "Software fields in all workflow-table sections.",
      "variables": [
        "caseKey",
        "processLabel",
        "softwareLabel"
      ]
    },
    {
      "id": "b07_analysis_lineage",
      "question": "Which input dataset, analysis step, software, and result form each analysis lineage?",
      "selection_stratum": "analysis_lineage",
      "assessment_type": "query_based_retrieval",
      "source_basis": "Analysis rows and software fields in all eight source records.",
      "variables": [
        "caseKey",
        "analysisLabel",
        "inputDataLabel",
        "resultLabel",
        "softwareLabel"
      ]
    },
    {
      "id": "b08_individual_result_property_bearer",
      "question": "Which property and specimen are linked to each individual reported result?",
      "selection_stratum": "result_semantics",
      "assessment_type": "query_based_retrieval",
      "source_basis": "Every analysis target and the case specimen in the sanitized manifest.",
      "variables": [
        "caseKey",
        "resultLabel",
        "propertyLabel",
        "bearerLabel"
      ]
    },
    {
      "id": "b09_parsed_result_value_and_unit",
      "question": "Which reported result properties have a parsed numeric value and recognized unit?",
      "selection_stratum": "result_semantics",
      "assessment_type": "query_based_retrieval",
      "source_basis": "Analysis outputs with a parseable numeric value and recognized unit in the sanitized manifest; property-unit compatibility is audited separately.",
      "variables": [
        "caseKey",
        "propertyLabel",
        "value",
        "unit"
      ]
    },
    {
      "id": "b10_result_generation",
      "question": "Which analysis step generated each individual result?",
      "selection_stratum": "result_provenance",
      "assessment_type": "query_based_retrieval",
      "source_basis": "Analysis-step and target pairs in all eight source records.",
      "variables": [
        "caseKey",
        "analysisLabel",
        "resultLabel"
      ]
    },
    {
      "id": "b11_workflow_task_grouping",
      "question": "Which named workflow groups the measurement and processing tasks for each case?",
      "selection_stratum": "workflow_structure",
      "assessment_type": "query_based_retrieval",
      "source_basis": "Each case is one bounded characterization workflow containing one measurement and its distinct source-defined steps.",
      "variables": [
        "caseKey",
        "workflowLabel",
        "taskCount"
      ]
    },
    {
      "id": "b12_technique_occurrence_separation",
      "question": "Which technique description is explicitly distinguished from, and linked to, each measurement occurrence?",
      "selection_stratum": "methodology_description",
      "assessment_type": "query_retrieval_and_native_pattern_assessment",
      "source_basis": "The method-family descriptor and measurement occurrence recorded for every case.",
      "variables": [
        "caseKey",
        "techniqueLabel",
        "measurementLabel"
      ]
    },
    {
      "id": "b13_case_method_specificity",
      "question": "Does each source record resolve to a dedicated native ontology class at the specificity of its selected characterization profile?",
      "selection_stratum": "selected_profile_vocabulary",
      "assessment_type": "native_vocabulary_coverage",
      "source_basis": "The curated characterization-profile identity recorded for each of the eight workbook records.",
      "variables": [
        "caseKey",
        "methodLabel"
      ]
    }
  ]
}