{
    "decision_rule": "Changed names, vendors, identifiers, purposes, thresholds, or workflow locations do not prove compliance. Operational effect, affected pathways, downstream use, and correction persistence control the conclusion.",
    "dimensions": [
        "renamed_fields",
        "new_vendor",
        "proxy_substitution",
        "threshold_changes",
        "model_retraining",
        "derived_labels",
        "workflow_relocation",
        "human_note_instructions",
        "queue_prioritization",
        "export_reimport",
        "subsidiary_fragmentation",
        "retention_cache_behavior"
    ],
    "individualized_action_boundary": "Functional-equivalence findings authorize institutional remedy enforcement only; they cannot establish person-level guilt, risk, or eligibility.",
    "purpose": "Determine whether a changed rule, vendor, proxy, model, workflow, or storage path reproduces substantially the same prohibited adverse effect.",
    "release": "R50",
    "required_evidence": [
        "configuration or contract diffs",
        "operational logs",
        "synthetic canary outcomes",
        "model or label lineage",
        "queue and export traces",
        "downstream acknowledgment"
    ],
    "schema": "antichrist.cx.functional-equivalence-test.v1",
    "statuses": [
        "equivalent",
        "different",
        "not_observed",
        "not_applicable"
    ]
}