{
    "decisions": [
        {
            "candidate_id": "refc_55843a707cb908ee",
            "decision": "accept",
            "reason_codes": [
                "semantic_supported",
                "exact_on_snapshot"
            ],
            "grounds": [
                "entity_meaning",
                "role_meaning"
            ],
            "cited_evidence_ids": [
                "refm_5f5a10a4b78353aa",
                "keycert_96d597ef28a0a8a2",
                "exm_01facb48cfc73ff4",
                "exm_edfe6b4c8ff544c1"
            ],
            "claims": [
                {
                    "fact": "matched_rows",
                    "value": 1809
                },
                {
                    "fact": "unmatched_rows",
                    "value": 0
                }
            ],
            "rationale": "Returns Data.TerritoryKey is a territory identifier and the Territory Lookup holds one row per sales territory keyed by SalesTerritoryKey, so the reference is semantically sound. All 1809 return rows match, and the parent key is unique on its 10 rows."
        },
        {
            "candidate_id": "refc_9463df49861c8ac5",
            "decision": "reject",
            "reason_codes": [
                "coincidental_overlap",
                "role_conflict"
            ],
            "grounds": [
                "entity_meaning",
                "role_meaning"
            ],
            "cited_evidence_ids": [
                "refm_92938a768edd90cf",
                "exm_84b03919f844ad6f",
                "exm_01facb48cfc73ff4"
            ],
            "claims": [
                {
                    "fact": "parent_rows",
                    "value": 37
                }
            ],
            "rationale": "A territory key does not identify a product subcategory. The small integers 1..37 overlap only because both are numbered from 1, and the territory lookup is the correct parent."
        }
    ],
    "suggestions": []
}