{
  "schema_version": 1,
  "assessed_at": "2026-11-02",
  "review_process": "AI-assisted editorial scope assessment by Codex with a separate AI-assisted challenge pass; not independent human or legal review.",
  "coverage": {
    "programs": 8,
    "governance_topics": 80,
    "pairings": 640,
    "meaning": "Every current program–topic pairing has an explicit disposition. This is not exhaustive coverage of governance sources or validated research outcomes."
  },
  "basis": "Existing public research accounts and curated explorer topic summaries, questions, scopes and source references. No new full-text legal or standards review is claimed.",
  "governance_basis_sha256": "8702c43992cb313064c431ebc92756a45d2589b1f2879362511d57d45879d55e",
  "relation_definitions": {
    "direct": "Specific methodological relevance: a governance topic addresses an object or question the program examines. This does not establish a tested application, legal applicability or compliance.",
    "context": "Background context: relevant to framing a possible study, but outside the current bounded method, population, domain or tested mechanism.",
    "not_established": "The current public scope and curated topic record do not establish a specific defensible connection. Future relevance remains open."
  },
  "limits": [
    "Mappings identify possible investigation questions, not research findings, validation, legal advice or proof of effective control.",
    "No private chapter manuscript or private research artifacts are published.",
    "Revocation question 1 remains the sole active study direction; evidence trust and oversight at scale remain deferred.",
    "The five earlier MIT risk mappings remain separately sourced and retain their own October 8 review date."
  ],
  "programs": [
    {
      "id": "tae",
      "title": "Trust, Autonomy, and Evidence",
      "question": "A person appears in the workflow. What evidence shows they could understand, intervene and affect the action?",
      "scope": "A reproducible documentary assessment method, demonstrated on three selected historical cases. The approved conditional reassessment leaves all three Unresolved.",
      "limits": "One researcher assessed three purposively selected historical cases. Independent reliability, construct validity, transfer to contemporary AI systems and effects on human review remain unestablished. All 1,079 original Jev adjudications remain unresolved.",
      "evidence": [
        {
          "label": "Approved October revision and conditional findings",
          "url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md"
        },
        {
          "label": "Phase closeout and reopening boundary",
          "url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/docs/research-phase-closeout-2026-10-16.md"
        }
      ]
    },
    {
      "id": "hit",
      "title": "Human Influence Telemetry",
      "question": "What documentary evidence shows that human judgment retained practical influence, and can reviewers assess it consistently?",
      "scope": "A documentary assessment method and a preserved exercise in which two scorers agreed on seven of seven items in one case packet under the earlier scoring contract.",
      "limits": "Current-contract replication, the independent human implementation audit, broader validity and stable-release gates remain unresolved. Software checks and AI-assisted development do not supply independent human validation.",
      "evidence": [
        {
          "label": "Preserved human comparison",
          "url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md"
        },
        {
          "label": "Closeout, maintenance and separate release gates",
          "url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/docs/closeout-plan.md"
        }
      ]
    },
    {
      "id": "cec",
      "title": "Control Evidence Corpus",
      "question": "What can surviving evidence establish about whether an AI control operated, and where must an assessment remain unresolved?",
      "scope": "Evidence-linked records, three synthetic demonstrations and reproducible development tools. The empirical pilot and an approved corpus release remain forthcoming.",
      "limits": "Synthetic packets, AI-authored references, model agreement and software checks do not supply independent human validity or reliability findings. Comparative pilot roles and thresholds remain unfilled.",
      "evidence": [
        {
          "label": "Research brief and decision gates",
          "url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md"
        },
        {
          "label": "Instruction comparison and retained decision",
          "url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/experiments/jev-cec/instruction-comparison-001/LIVE-RESULTS.md"
        },
        {
          "label": "Development scope",
          "url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/README.md"
        }
      ]
    },
    {
      "id": "revocation",
      "title": "Revocation in Delegated AI Workflows",
      "question": "Does withdrawing permission prevent new protected changes while delegated work remains unfinished?",
      "scope": "Initial deterministic measurement qualification in a trusted local database with scripted workers, one authority root and one parent-to-child delegation edge. Withdrawal and protected changes use the same durable commit ordering. Only question 1 is active; evidence trust and oversight at scale remain deferred.",
      "limits": "No autonomous-agent or framework-based experiment has run; novelty, non-bypassability, institutional effectiveness and AGI readiness remain unestablished. Rescinding effects already committed is a separate requirement.",
      "evidence": [
        {
          "label": "Public study scope and timing contract (not publicly available)",
          "url": ""
        },
        {
          "label": "Public qualification methods and comparison controls (not publicly available)",
          "url": ""
        },
        {
          "label": "Public future design gates (not publicly available)",
          "url": ""
        }
      ]
    },
    {
      "id": "repair",
      "question": "What must an institution acknowledge, repair and change before it can call an AI-mediated harm resolved?",
      "scope": "Public editorial companion to the forthcoming Poenitentia Institutionum chapter. It examines prudential conditions, accountable explanation, repair and reform. It proposes an institutional analogy; neither a tested repair intervention nor access to the private chapter is asserted.",
      "evidence": [
        {
          "label": "Public companion: repair, reform and evidentiary limits",
          "url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform"
        },
        {
          "label": "Public companion: what the record can establish",
          "url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#evidence-and-its-limits"
        }
      ]
    },
    {
      "id": "cdfi",
      "question": "Which failures should disqualify an otherwise persuasive answer, and who can justify and review that judgment?",
      "scope": "A source-linked scoring architecture translated from seven AI safety publications for SAICRED. Scoring-contract reconciliation and human theological validation remain open. Literature-informed design choices do not establish the validity of particular weights, thresholds or deployment tiers. Reported model rankings and automated-judge checks do not replace human theological validation.",
      "evidence": [
        {
          "label": "Source-to-method translation, pinned public research account",
          "url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md"
        },
        {
          "label": "Public Research account: CDFI",
          "url": "https://nodeandnorm.org/research#cdfi"
        }
      ]
    },
    {
      "id": "gdi",
      "question": "An institution acts on an AI-informed recommendation. What record would let someone reconstruct its evidence, authority and obligations?",
      "scope": "A decision-record specification, gate classifier and signed-receipt demonstration. Internal checks establish limited properties of the supplied records and fixtures. A valid or signed record does not establish its factual truth, reviewer comprehension, appropriate calibration, lawful action or effective human control. Receipt interoperability is narrower than validation of the research program.",
      "evidence": [
        {
          "label": "Research scope, pinned public source",
          "url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md"
        },
        {
          "label": "Validation scope, pinned public source",
          "url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/docs/validation-and-reproducibility.md"
        }
      ]
    },
    {
      "id": "rgds",
      "question": "Why did a team proceed, stop or wait, and what evidence must close the conditions attached to its permission?",
      "scope": "A schema, validators and six illustrative decision records that make permission, unresolved conditions and closure evidence explicit. Six authored examples and successful software checks do not establish actual IND submission outcomes, regulatory acceptance, faster reconstruction or field effectiveness. Recorded owners and closure requirements still require substantive review.",
      "evidence": [
        {
          "label": "Reference implementation and historical-study boundary, pinned source",
          "url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md"
        },
        {
          "label": "Source-derived design rationale, pinned source",
          "url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/docs/why-rgds-exists.md"
        }
      ]
    }
  ],
  "assessments": [
    {
      "program_id": "tae",
      "topic_id": "reg-us-consumer",
      "relation": "context",
      "rationale": "U.S. consumer protection asks: What evidence supports the claims made to customers about this system? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by U.S. consumer protection, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for U.S. consumer protection, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.ftc.gov/legal-library/browse/statutes/federal-trade-commission-act"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-equality",
      "relation": "context",
      "rationale": "Employment equality and disability asks: Can a person challenge a technology-assisted employment decision and obtain an accessible review? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Employment equality and disability, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Employment equality and disability, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.eeoc.gov/fact-sheet/federal-laws-prohibiting-job-discrimination-questions-and-answers"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-credit",
      "relation": "context",
      "rationale": "Credit decisions and reasons asks: Can the creditor reconstruct and accurately explain the principal reasons for the adverse decision? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Credit decisions and reasons, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Credit decisions and reasons, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.consumerfinance.gov/compliance/compliance-resources/other-applicable-requirements/equal-credit-opportunity-act/"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-medical",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: FDA guidance distinguishes software functions subject to device oversight from other functions. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.fda.gov/regulatory-information/search-fda-guidance-documents/policy-device-software-functions-and-mobile-medical-applications"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-california",
      "relation": "context",
      "rationale": "California privacy and automated decisions asks: Which personal data and automated decisions are covered, and how would the business respond to a valid request? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by California privacy and automated decisions, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for California privacy and automated decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.cppa.ca.gov/regulations/"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-california-employment",
      "relation": "context",
      "rationale": "California: employment decision systems asks: Can retained records show how the system affected the employment decision and support examination of discrimination concerns? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by California: employment decision systems, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for California: employment decision systems, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://calcivilrights.ca.gov/2025/06/30/civil-rights-council-secures-approval-for-regulations-to-protect-against-employment-discrimination-related-to-artificial-intelligence/"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-california-frontier",
      "relation": "context",
      "rationale": "California: frontier-model transparency asks: What evidence connects the published framework to risk assessments, mitigations and the handling of reported concerns? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by California: frontier-model transparency, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for California: frontier-model transparency, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://oag.ca.gov/sb53"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-california-companions",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: California requires covered companion-chatbot operators to identify AI when users could reasonably mistake it for a human and maintain published protocols addressing suicide and self-harm. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260SB243"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-colorado",
      "relation": "context",
      "rationale": "Colorado: consequential decisions asks: What information would let a person understand the technology’s role and request a meaningful reconsideration? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Colorado: consequential decisions, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Colorado: consequential decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/sb26-189"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-colorado-health-review",
      "relation": "direct",
      "rationale": "The scoped health-review topic asks whether a qualified reviewer could change a proposed denial before issue, matching TAE’s documentary question about a usable opportunity to intervene.",
      "investigation_question": "What evidence would show that a qualified reviewer examined the patient’s circumstances and could change a proposed denial before it was issued?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Colorado: AI-assisted health-care review criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1139"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-colorado-psychotherapy",
      "relation": "context",
      "rationale": "Colorado: AI use in psychotherapy asks: What evidence distinguishes active professional participation from later review, and shows that refusing or withdrawing recording consent changed system behavior? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Colorado: AI use in psychotherapy, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Colorado: AI use in psychotherapy, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1195"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-colorado-conversational-ai",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Colorado’s law establishes duties for covered conversational AI operators, including AI disclosures, crisis referral and escalation protocols, and restrictions on claims of professional equivalence. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1263"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-connecticut-employment",
      "relation": "context",
      "rationale": "Connecticut: automated employment decisions asks: What connects the notice, the system’s actual role in the decision and the institution’s response to testing findings? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Connecticut: automated employment decisions, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Connecticut: automated employment decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.cga.ct.gov/2026/ACT/PA/PDF/2026PA-00015-R00SB-00005-PA.PDF"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-illinois-employment",
      "relation": "context",
      "rationale": "Illinois: AI in employment decisions asks: Can the employer trace the tool’s role, examine discriminatory effects and show that required notice was provided? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Illinois: AI in employment decisions, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: AI in employment decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://ilga.gov/legislation/PublicActs/View/103-0804"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-illinois-psychological",
      "relation": "context",
      "rationale": "Illinois: AI support in psychological services asks: Can records show the professional’s review, responsibility and consent arrangements for the permitted support function? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Illinois: AI support in psychological services, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: AI support in psychological services, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://ilga.gov/Legislation/PublicActs/View/104-0054"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-illinois-video",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: For covered recorded interviews, employers must explain AI use and obtain consent before assessment. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://my.ilga.gov/Legislation/ILCS/Articles?ActID=4015&Chapter=EMPLOYMENT&ChapterID=68&MajorTopic=BUSINESS+AND+EMPLOYMENT"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-illinois-biometric",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: BIPA sets requirements for covered private entities collecting or holding biometric identifiers and information. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.ilga.gov/legislation/ilcs/fulltext?DocName=074000140K15"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-illinois-frontier",
      "relation": "context",
      "rationale": "Illinois: frontier-model safety and audits asks: Can an independent auditor inspect the evidence needed to assess whether the developer follows its published framework? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Illinois: frontier-model safety and audits, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: frontier-model safety and audits, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.ilga.gov/documents/legislation/PublicActs/104/104-0538.htm"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-minnesota-profiling",
      "relation": "context",
      "rationale": "Minnesota: profiling and reevaluation asks: Did correcting the data produce a reevaluation, and what evidence establishes the resulting effect? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Minnesota: profiling and reevaluation, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Minnesota: profiling and reevaluation, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.ag.state.mn.us/Data-Privacy/Consumer/"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-new-york-government",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: New York requires a state-agency AI inventory and agency publication of lists describing automated employment decision tools. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/STT/103-E"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-new-york-raise",
      "relation": "context",
      "rationale": "New York: frontier-model transparency asks: What evidence would show that published safeguards informed deployment decisions and that an incident reached the responsible authority? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by New York: frontier-model transparency, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for New York: frontier-model transparency, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/bills/2025/S8828"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-new-york-companions",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: New York requires covered AI companion operators to provide clear, conspicuous notices that users are not communicating with a human and reasonable-efforts protocols for detecting self-harm or suicidal ideation and directing users to crisis services. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/GBS/1700"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-texas",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: TRAIGA sets disclosure requirements for specified government and healthcare uses, prohibits specified AI practices and provides for enforcement by the Attorney General. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://capitol.texas.gov/billlookup/BillSummary.aspx?Bill=HB149&LegSess=89R"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-utah-chatbots",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Suppliers of covered mental-health chatbots must disclose that the service is AI rather than a human. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://le.utah.gov/xcode/Title13/Chapter72A/C13-72a-P2_2025050720250507.pdf"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-virginia-profiling",
      "relation": "context",
      "rationale": "The privacy-request appeal process supplies context for a documentary challenge path; it must not be treated as a universal appeal of the underlying automated decision.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Virginia: profiling and privacy requests, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Virginia: profiling and privacy requests, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://law.lis.virginia.gov/vacode/title59.1/chapter53/section59.1-577/"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-wisconsin-political",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Covered political audio and video communications containing synthetic media substantially produced using generative AI require disclosures. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://content.govdelivery.com/accounts/WIGOV/bulletins/391af46"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-wisconsin-insurance",
      "relation": "context",
      "rationale": "Wisconsin: insurance AI governance guidance asks: Can the insurer produce evidence that its AI program, testing and vendor oversight operate in the decisions under examination? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Wisconsin: insurance AI governance guidance, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Wisconsin: insurance AI governance guidance, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://oci.wi.gov/Pages/Regulation/Bulletin20250318AI.aspx"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-us-new-york-city-aedt",
      "relation": "context",
      "rationale": "New York City: employment-tool bias audits asks: Which tool and use did the audit examine, and can an affected person find the relevant audit information and notice? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by New York City: employment-tool bias audits, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for New York City: employment-tool bias audits, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.nyc.gov/site/dca/about/automated-employment-decision-tools.page"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-eu-prohibited",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The AI Act prohibits specified practices involving manipulation, exploitation, social scoring and certain biometric or other uses. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-5"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-eu-high-risk",
      "relation": "context",
      "rationale": "High-risk systems and requirements asks: What classification applies to this use, and which evidence would support the relevant requirements? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by High-risk systems and requirements, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for High-risk systems and requirements, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-6"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-eu-human-oversight",
      "relation": "direct",
      "rationale": "The oversight topic separates understanding, authority and intervention; TAE explicitly examines documentary support for those practical control conditions.",
      "investigation_question": "What evidence shows that a reviewer could use their authority, and what happened when they tried?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Human oversight criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02024R1689-20260727"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-eu-transparency",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Article 50 addresses information about certain AI interactions and generated or manipulated content. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-50"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-eu-gpai",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The Act sets provider obligations for general-purpose AI models, including documentation, downstream information and copyright-related measures. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-53"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-eu-value-chain",
      "relation": "context",
      "rationale": "Responsibilities across the value chain asks: Who is responsible for this version and use, and who can supply the information needed to examine it? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Responsibilities across the value chain, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Responsibilities across the value chain, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-25"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-eu-gdpr",
      "relation": "context",
      "rationale": "Personal data and automated decisions asks: What data supports the decision, and which information, correction or challenge rights apply to the person affected? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Personal data and automated decisions, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Personal data and automated decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-eu-nis2",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: NIS2 addresses cybersecurity risk management and incident reporting for covered organizations and sectors. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/nis2-directive"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-eu-cra",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The Cyber Resilience Act addresses cybersecurity of covered hardware and software products with digital elements. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-kr-ai-basic",
      "relation": "context",
      "rationale": "Republic of Korea: AI Basic Act asks: What use category applies, and what information and oversight arrangements need examination? The topic supplies a possible institutional setting or expectation for documentary human-control assessment; TAE’s three historical demonstrations did not test this instrument’s legal requirements.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Republic of Korea: AI Basic Act, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Republic of Korea: AI Basic Act, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.msit.go.kr/eng/bbs/view.do?bbsSeqNo=42&mId=4&mPid=2&nttSeqNo=1214&sCode=eng"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-cn-generative",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The measures address generative AI services offered to the public within China, including data practices, service responsibilities and complaint handling. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.cac.gov.cn/2023-07/13/c_1690898327029107.htm"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-jp-ai-promotion",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Japan’s AI law organizes promotion of AI research and use alongside attention to risks. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www8.cao.go.jp/cstp/ai/ai_act/ai_act.html"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-in-dpdp",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: India’s digital-personal-data framework addresses lawful processing, organizational responsibilities and individuals’ rights. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.pib.gov.in/PressReleseDetailm.aspx?PRID=2190655&lang=2&reg=48"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-br-lgpd",
      "relation": "context",
      "rationale": "A covered person’s request for review offers context for examining challenge records; the topic does not promise universal human review, and TAE does not decide LGPD applicability.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Brazil: data protection and review, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Brazil: data protection and review, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.gov.br/anpd/pt-br/assuntos/titular-de-dados/direito-dos-titulares"
    },
    {
      "program_id": "tae",
      "topic_id": "reg-institutional-commitments",
      "relation": "direct",
      "rationale": "Stated purposes and supplier commitments identify whose authority and information a documentary control assessment must examine.",
      "investigation_question": "What did the institution and its suppliers commit to, and what evidence could show whether those commitments were met?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Procurement, contracts and stated purposes criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "tae",
      "topic_id": "iso-42001",
      "relation": "context",
      "rationale": "AI management systems · ISO/IEC 42001:2023 asks: What evidence shows that the organization's AI responsibilities and review processes operate in practice? The reference helps frame control conditions and vocabulary, while TAE’s case scoring remains governed by its own explicit assessment contract.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by AI management systems · ISO/IEC 42001:2023, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI management systems · ISO/IEC 42001:2023, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.iso.org/standard/42001"
    },
    {
      "program_id": "tae",
      "topic_id": "iso-23894",
      "relation": "context",
      "rationale": "AI risk management · ISO/IEC 23894:2023 asks: Which risks arise in this use, who addresses them, and what evidence supports the response? The reference helps frame control conditions and vocabulary, while TAE’s case scoring remains governed by its own explicit assessment contract.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by AI risk management · ISO/IEC 23894:2023, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI risk management · ISO/IEC 23894:2023, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.iso.org/standard/77304.html"
    },
    {
      "program_id": "tae",
      "topic_id": "iso-42005",
      "relation": "context",
      "rationale": "AI impact assessment · ISO/IEC 42005:2025 asks: Whose interests could be affected, and what changes when new evidence of impact emerges? The reference helps frame control conditions and vocabulary, while TAE’s case scoring remains governed by its own explicit assessment contract.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by AI impact assessment · ISO/IEC 42005:2025, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI impact assessment · ISO/IEC 42005:2025, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.iso.org/standard/42005"
    },
    {
      "program_id": "tae",
      "topic_id": "iso-22989",
      "relation": "context",
      "rationale": "Shared AI terminology · ISO/IEC 22989:2022 asks: Are the people examining this decision using the same terms for the system and its activities? The reference helps frame control conditions and vocabulary, while TAE’s case scoring remains governed by its own explicit assessment contract.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Shared AI terminology · ISO/IEC 22989:2022, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Shared AI terminology · ISO/IEC 22989:2022, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.iso.org/standard/74296.html"
    },
    {
      "program_id": "tae",
      "topic_id": "nist-ai-rmf-1-0",
      "relation": "context",
      "rationale": "AI Risk Management Framework · NIST AI RMF 1.0 asks: How do the identified risks, evaluation findings and management decisions connect for this use? The reference helps frame control conditions and vocabulary, while TAE’s case scoring remains governed by its own explicit assessment contract.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by AI Risk Management Framework · NIST AI RMF 1.0, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI Risk Management Framework · NIST AI RMF 1.0, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "tae",
      "topic_id": "oecd-ai-principles",
      "relation": "context",
      "rationale": "Trustworthy AI principles · OECD asks: How can affected people understand, question and seek an accountable response to this AI use? The reference helps frame control conditions and vocabulary, while TAE’s case scoring remains governed by its own explicit assessment contract.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Trustworthy AI principles · OECD, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Trustworthy AI principles · OECD, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://oecd.ai/en/ai-principles"
    },
    {
      "program_id": "tae",
      "topic_id": "unesco-ai-ethics",
      "relation": "context",
      "rationale": "Ethics of AI · UNESCO Recommendation asks: Whose rights and dignity are at stake, and who remains responsible for responding to harm? The reference helps frame control conditions and vocabulary, while TAE’s case scoring remains governed by its own explicit assessment contract.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Ethics of AI · UNESCO Recommendation, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Ethics of AI · UNESCO Recommendation, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.unesco.org/en/artificial-intelligence/recommendation-ethics"
    },
    {
      "program_id": "tae",
      "topic_id": "owasp-llm-top-10-2025",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Community security guidance describing common risks in applications using large language models, including prompt injection, sensitive information disclosure and excessive agency. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "tae",
      "topic_id": "mitre-atlas",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: A living knowledge base of adversary tactics and techniques involving AI, informed by observed attacks and realistic demonstrations. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "tae",
      "topic_id": "nist-digital-identity-4",
      "relation": "context",
      "rationale": "Digital identity · NIST SP 800-63-4 asks: Whose identity was established, by what assurance process, and what separate authority governed the action? The reference helps frame control conditions and vocabulary, while TAE’s case scoring remains governed by its own explicit assessment contract.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Digital identity · NIST SP 800-63-4, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Digital identity · NIST SP 800-63-4, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "tae",
      "topic_id": "nist-generative-ai-profile",
      "relation": "context",
      "rationale": "Generative AI risk profile · NIST AI 600-1 asks: Which generative AI risks matter in this deployment, and what evidence supports the chosen controls? The reference helps frame control conditions and vocabulary, while TAE’s case scoring remains governed by its own explicit assessment contract.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Generative AI risk profile · NIST AI 600-1, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Generative AI risk profile · NIST AI 600-1, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence"
    },
    {
      "program_id": "tae",
      "topic_id": "iso-27001",
      "relation": "context",
      "rationale": "Information security management · ISO/IEC 27001:2022 asks: What protects the decision's data and records from unauthorized access, alteration or loss? The reference helps frame control conditions and vocabulary, while TAE’s case scoring remains governed by its own explicit assessment contract.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Information security management · ISO/IEC 27001:2022, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Information security management · ISO/IEC 27001:2022, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.iso.org/standard/27001"
    },
    {
      "program_id": "tae",
      "topic_id": "roles-leadership",
      "relation": "context",
      "rationale": "Leadership and accountable ownership asks: Who must act when a concern exceeds the system owner’s authority? This role can shape who owns or reviews an assessment, without itself establishing a person’s practical control over the case decision.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Leadership and accountable ownership, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Leadership and accountable ownership, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "tae",
      "topic_id": "roles-delivery",
      "relation": "direct",
      "rationale": "Locating the party able to change a component helps identify whether the intervention opportunity reached the actual action boundary.",
      "investigation_question": "Which organization can change the component involved, and how does a concern reach it?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Developers, suppliers and deployers criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "tae",
      "topic_id": "roles-domain-users",
      "relation": "direct",
      "rationale": "Available information, expertise and time are conditions in TAE’s question about whether formal authority could be exercised.",
      "investigation_question": "Does the person handling the decision have the information, time and expertise needed to question it?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Domain specialists and frontline users criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "tae",
      "topic_id": "roles-reviewers",
      "relation": "context",
      "rationale": "Reviewers and independent assessors asks: What can the reviewer inspect, and who must respond to an unresolved finding? This role can shape who owns or reviews an assessment, without itself establishing a person’s practical control over the case decision.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Reviewers and independent assessors, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Reviewers and independent assessors, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "tae",
      "topic_id": "roles-affected-people",
      "relation": "direct",
      "rationale": "A route to challenge provides a concrete decision path on which TAE can examine whether concerns could reach someone able to act.",
      "investigation_question": "Can an affected person raise a concern and obtain an intelligible response?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Affected people and routes to challenge criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "tae",
      "topic_id": "roles-intervention",
      "relation": "direct",
      "rationale": "A named power to pause or override is directly relevant to TAE’s distinction between formal authority and the opportunity to affect action.",
      "investigation_question": "If a person challenges the decision, who can change what happens next?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Authority to intervene and repair criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "tae",
      "topic_id": "controls-inventory",
      "relation": "context",
      "rationale": "Inventories and change records asks: Which version and intended use does this decision or test result concern? This arrangement can supply or constrain the records and operating context available to a TAE assessor; it is not itself a validated TAE condition.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Inventories and change records, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Inventories and change records, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "tae",
      "topic_id": "controls-data",
      "relation": "context",
      "rationale": "Data handling and retained records asks: Can the relevant record be retrieved and examined without exposing information beyond the reviewer’s authority? This arrangement can supply or constrain the records and operating context available to a TAE assessor; it is not itself a validated TAE condition.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Data handling and retained records, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Data handling and retained records, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "tae",
      "topic_id": "controls-access",
      "relation": "direct",
      "rationale": "Permission and delegated authority records can help distinguish formal authorization from a practically available intervention route.",
      "investigation_question": "Which identity and permission allowed the action, and who could revoke that permission?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Identity, permissions and delegation criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "tae",
      "topic_id": "controls-intervention",
      "relation": "direct",
      "rationale": "Stopping and containment records can supply documentary evidence of whether a reviewer could intervene before the consequence.",
      "investigation_question": "Can the intervention reach the relevant action before its effects become irreversible?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Stopping, containment and recovery criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "tae",
      "topic_id": "controls-monitoring",
      "relation": "context",
      "rationale": "Logs, incidents and follow-up asks: What happens after a warning is recorded, and how is the response examined? This arrangement can supply or constrain the records and operating context available to a TAE assessor; it is not itself a validated TAE condition.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Logs, incidents and follow-up, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Logs, incidents and follow-up, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "tae",
      "topic_id": "controls-boundaries",
      "relation": "direct",
      "rationale": "The stated action boundary identifies what a human intervention would have had to constrain in the decision under assessment.",
      "investigation_question": "Could the system act beyond the intended scope, and which boundary would prevent or contain it?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Supplier and agent action boundaries criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "tae",
      "topic_id": "evaluation-model",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Examine what a model can do using stated tasks, inputs and assessment methods. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "tae",
      "topic_id": "evaluation-application",
      "relation": "context",
      "rationale": "Application and mission-specific tests asks: How closely do the test conditions match the setting in which people will rely on the result? The topic informs design of a separately scoped future application or reassessment, beyond the closed methods demonstration.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Application and mission-specific tests, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Application and mission-specific tests, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "tae",
      "topic_id": "evaluation-control",
      "relation": "direct",
      "rationale": "The topic’s separation of intervention request, response and result matches TAE’s need to distinguish an opportunity for control from a reassuring checkpoint.",
      "investigation_question": "When the reviewer tried to intervene, what actually changed?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Tests of intervention and authority criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "tae",
      "topic_id": "evaluation-adversarial",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Examine plausible attacks, misuse and component failures in a controlled test setting. The declared Trust, Autonomy, and Evidence work addresses whether the documentary record establishes an opportunity to understand, intervene and affect action; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "tae",
      "topic_id": "evaluation-human-factors",
      "relation": "direct",
      "rationale": "Information, working conditions and the freedom to question a recommendation are documentary conditions relevant to TAE’s control assessment.",
      "investigation_question": "What conditions helped or prevented the person from examining and challenging the output?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Human judgment and working conditions criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "tae",
      "topic_id": "evaluation-reproducibility",
      "relation": "direct",
      "rationale": "Frozen assessment inputs and rule versions are necessary to reproduce TAE’s conditional findings and examine disagreements.",
      "investigation_question": "Can another assessor inspect or repeat the procedure and understand why results differ?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Reproducibility and retained test artifacts criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "tae",
      "topic_id": "evaluation-regression",
      "relation": "context",
      "rationale": "Rechecking after changes asks: What changed, which claims could it affect, and what was retested? The topic informs design of a separately scoped future application or reassessment, beyond the closed methods demonstration.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Rechecking after changes, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Rechecking after changes, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "tae",
      "topic_id": "evidence-claims",
      "relation": "direct",
      "rationale": "TAE’s assessment requires an explicit control claim and scoring contract so a case finding is not generalized beyond its evidence.",
      "investigation_question": "Exactly what conclusion is the reader being asked to accept?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Claims, criteria and scope criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "tae",
      "topic_id": "evidence-provenance",
      "relation": "direct",
      "rationale": "TAE’s documentary judgments depend on identifiable sources and visible gaps; source traceability does not settle evidentiary validity.",
      "investigation_question": "What is the source of this evidence, and what relevant material is unavailable?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Sources, provenance and missing records criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.w3.org/TR/prov-dm/"
    },
    {
      "program_id": "tae",
      "topic_id": "evidence-reconstruction",
      "relation": "direct",
      "rationale": "Reconstructing the decision and intervention is the central documentary operation through which TAE examines practical human control.",
      "investigation_question": "What can the available record establish about the intervention and what followed it?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Reconstructing the decision and intervention criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "tae",
      "topic_id": "evidence-uncertainty",
      "relation": "direct",
      "rationale": "TAE preserves Unresolved findings where retained alternatives or missing evidence do not settle a control condition.",
      "investigation_question": "What would weaken this conclusion, and which questions remain unresolved?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Conflicting evidence and unresolved findings criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "tae",
      "topic_id": "evidence-review",
      "relation": "direct",
      "rationale": "Making the reasoning and source basis inspectable allows another assessor to challenge a TAE judgment without assuming the initial finding is valid.",
      "investigation_question": "Can another reader trace the conclusion to its evidence and challenge the reasoning?",
      "evidence_needed": [
        "Dated source record for the decision, including what the reviewer could see and which alternatives were available.",
        "The applicable TAE scoring contract, retained judgment alternatives and reasons for an unresolved condition.",
        "The specifically selected Review, challenge and communication criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "tae",
      "topic_id": "evidence-correction",
      "relation": "context",
      "rationale": "Correction records and evidence of effects asks: What evidence shows whether the correction reached the people or decisions it was meant to affect? The topic concerns what an institution does with an assessment; a TAE finding does not itself authorize or demonstrate a corrective effect.",
      "investigation_question": "Before using Trust, Autonomy, and Evidence in a setting informed by Correction records and evidence of effects, which source condition, actor and workflow would need to be selected to examine whether the documentary record establishes an opportunity to understand, intervene and affect action?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Correction records and evidence of effects, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. TAE’s closed three-case demonstration does not establish legal compliance, independent validity or transfer to a contemporary system.",
      "program_evidence_url": "https://github.com/node-and-norm/trust-autonomy-evidence/blob/dda52937571ff342810553a435e3569ed6af626b/paper/revisions/2026-10-10/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-consumer",
      "relation": "context",
      "rationale": "U.S. consumer protection asks: What evidence supports the claims made to customers about this system? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by U.S. consumer protection, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for U.S. consumer protection, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.ftc.gov/legal-library/browse/statutes/federal-trade-commission-act"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-equality",
      "relation": "context",
      "rationale": "Employment equality and disability asks: Can a person challenge a technology-assisted employment decision and obtain an accessible review? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Employment equality and disability, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Employment equality and disability, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.eeoc.gov/fact-sheet/federal-laws-prohibiting-job-discrimination-questions-and-answers"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-credit",
      "relation": "context",
      "rationale": "Credit decisions and reasons asks: Can the creditor reconstruct and accurately explain the principal reasons for the adverse decision? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Credit decisions and reasons, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Credit decisions and reasons, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.consumerfinance.gov/compliance/compliance-resources/other-applicable-requirements/equal-credit-opportunity-act/"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-medical",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: FDA guidance distinguishes software functions subject to device oversight from other functions. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.fda.gov/regulatory-information/search-fda-guidance-documents/policy-device-software-functions-and-mobile-medical-applications"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-california",
      "relation": "context",
      "rationale": "California privacy and automated decisions asks: Which personal data and automated decisions are covered, and how would the business respond to a valid request? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by California privacy and automated decisions, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for California privacy and automated decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.cppa.ca.gov/regulations/"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-california-employment",
      "relation": "context",
      "rationale": "California: employment decision systems asks: Can retained records show how the system affected the employment decision and support examination of discrimination concerns? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by California: employment decision systems, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for California: employment decision systems, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://calcivilrights.ca.gov/2025/06/30/civil-rights-council-secures-approval-for-regulations-to-protect-against-employment-discrimination-related-to-artificial-intelligence/"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-california-frontier",
      "relation": "context",
      "rationale": "California: frontier-model transparency asks: What evidence connects the published framework to risk assessments, mitigations and the handling of reported concerns? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by California: frontier-model transparency, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for California: frontier-model transparency, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://oag.ca.gov/sb53"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-california-companions",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: California requires covered companion-chatbot operators to identify AI when users could reasonably mistake it for a human and maintain published protocols addressing suicide and self-harm. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260SB243"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-colorado",
      "relation": "context",
      "rationale": "Colorado: consequential decisions asks: What information would let a person understand the technology’s role and request a meaningful reconsideration? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Colorado: consequential decisions, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Colorado: consequential decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/sb26-189"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-colorado-health-review",
      "relation": "direct",
      "rationale": "The topic asks for evidence of qualified review before denial, which supplies a specific documentary setting for HIT’s question about observable human influence.",
      "investigation_question": "What evidence would show that a qualified reviewer examined the patient’s circumstances and could change a proposed denial before it was issued?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Colorado: AI-assisted health-care review criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1139"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-colorado-psychotherapy",
      "relation": "context",
      "rationale": "Colorado: AI use in psychotherapy asks: What evidence distinguishes active professional participation from later review, and shows that refusing or withdrawing recording consent changed system behavior? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Colorado: AI use in psychotherapy, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Colorado: AI use in psychotherapy, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1195"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-colorado-conversational-ai",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Colorado’s law establishes duties for covered conversational AI operators, including AI disclosures, crisis referral and escalation protocols, and restrictions on claims of professional equivalence. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1263"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-connecticut-employment",
      "relation": "context",
      "rationale": "Connecticut: automated employment decisions asks: What connects the notice, the system’s actual role in the decision and the institution’s response to testing findings? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Connecticut: automated employment decisions, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Connecticut: automated employment decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.cga.ct.gov/2026/ACT/PA/PDF/2026PA-00015-R00SB-00005-PA.PDF"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-illinois-employment",
      "relation": "context",
      "rationale": "Illinois: AI in employment decisions asks: Can the employer trace the tool’s role, examine discriminatory effects and show that required notice was provided? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Illinois: AI in employment decisions, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: AI in employment decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://ilga.gov/legislation/PublicActs/View/103-0804"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-illinois-psychological",
      "relation": "context",
      "rationale": "Illinois: AI support in psychological services asks: Can records show the professional’s review, responsibility and consent arrangements for the permitted support function? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Illinois: AI support in psychological services, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: AI support in psychological services, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://ilga.gov/Legislation/PublicActs/View/104-0054"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-illinois-video",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: For covered recorded interviews, employers must explain AI use and obtain consent before assessment. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://my.ilga.gov/Legislation/ILCS/Articles?ActID=4015&Chapter=EMPLOYMENT&ChapterID=68&MajorTopic=BUSINESS+AND+EMPLOYMENT"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-illinois-biometric",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: BIPA sets requirements for covered private entities collecting or holding biometric identifiers and information. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.ilga.gov/legislation/ilcs/fulltext?DocName=074000140K15"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-illinois-frontier",
      "relation": "context",
      "rationale": "Illinois: frontier-model safety and audits asks: Can an independent auditor inspect the evidence needed to assess whether the developer follows its published framework? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Illinois: frontier-model safety and audits, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: frontier-model safety and audits, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.ilga.gov/documents/legislation/PublicActs/104/104-0538.htm"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-minnesota-profiling",
      "relation": "context",
      "rationale": "Minnesota: profiling and reevaluation asks: Did correcting the data produce a reevaluation, and what evidence establishes the resulting effect? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Minnesota: profiling and reevaluation, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Minnesota: profiling and reevaluation, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.ag.state.mn.us/Data-Privacy/Consumer/"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-new-york-government",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: New York requires a state-agency AI inventory and agency publication of lists describing automated employment decision tools. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/STT/103-E"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-new-york-raise",
      "relation": "context",
      "rationale": "New York: frontier-model transparency asks: What evidence would show that published safeguards informed deployment decisions and that an incident reached the responsible authority? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by New York: frontier-model transparency, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for New York: frontier-model transparency, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/bills/2025/S8828"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-new-york-companions",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: New York requires covered AI companion operators to provide clear, conspicuous notices that users are not communicating with a human and reasonable-efforts protocols for detecting self-harm or suicidal ideation and directing users to crisis services. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/GBS/1700"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-texas",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: TRAIGA sets disclosure requirements for specified government and healthcare uses, prohibits specified AI practices and provides for enforcement by the Attorney General. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://capitol.texas.gov/billlookup/BillSummary.aspx?Bill=HB149&LegSess=89R"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-utah-chatbots",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Suppliers of covered mental-health chatbots must disclose that the service is AI rather than a human. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://le.utah.gov/xcode/Title13/Chapter72A/C13-72a-P2_2025050720250507.pdf"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-virginia-profiling",
      "relation": "context",
      "rationale": "A refused privacy request and its appeal may create documentary influence records, but HIT cannot turn this scoped request process into a general right to override an automated decision.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Virginia: profiling and privacy requests, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Virginia: profiling and privacy requests, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://law.lis.virginia.gov/vacode/title59.1/chapter53/section59.1-577/"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-wisconsin-political",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Covered political audio and video communications containing synthetic media substantially produced using generative AI require disclosures. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://content.govdelivery.com/accounts/WIGOV/bulletins/391af46"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-wisconsin-insurance",
      "relation": "context",
      "rationale": "Wisconsin: insurance AI governance guidance asks: Can the insurer produce evidence that its AI program, testing and vendor oversight operate in the decisions under examination? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Wisconsin: insurance AI governance guidance, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Wisconsin: insurance AI governance guidance, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://oci.wi.gov/Pages/Regulation/Bulletin20250318AI.aspx"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-us-new-york-city-aedt",
      "relation": "context",
      "rationale": "New York City: employment-tool bias audits asks: Which tool and use did the audit examine, and can an affected person find the relevant audit information and notice? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by New York City: employment-tool bias audits, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for New York City: employment-tool bias audits, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.nyc.gov/site/dca/about/automated-employment-decision-tools.page"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-eu-prohibited",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The AI Act prohibits specified practices involving manipulation, exploitation, social scoring and certain biometric or other uses. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-5"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-eu-high-risk",
      "relation": "context",
      "rationale": "High-risk systems and requirements asks: What classification applies to this use, and which evidence would support the relevant requirements? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by High-risk systems and requirements, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for High-risk systems and requirements, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-6"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-eu-human-oversight",
      "relation": "direct",
      "rationale": "Oversight arrangements raise the same documentary questions HIT examines about authority, information and influence on a decision.",
      "investigation_question": "What evidence shows that a reviewer could use their authority, and what happened when they tried?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Human oversight criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02024R1689-20260727"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-eu-transparency",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Article 50 addresses information about certain AI interactions and generated or manipulated content. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-50"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-eu-gpai",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The Act sets provider obligations for general-purpose AI models, including documentation, downstream information and copyright-related measures. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-53"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-eu-value-chain",
      "relation": "context",
      "rationale": "Responsibilities across the value chain asks: Who is responsible for this version and use, and who can supply the information needed to examine it? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Responsibilities across the value chain, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Responsibilities across the value chain, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-25"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-eu-gdpr",
      "relation": "context",
      "rationale": "Personal data and automated decisions asks: What data supports the decision, and which information, correction or challenge rights apply to the person affected? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Personal data and automated decisions, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Personal data and automated decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-eu-nis2",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: NIS2 addresses cybersecurity risk management and incident reporting for covered organizations and sectors. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/nis2-directive"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-eu-cra",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The Cyber Resilience Act addresses cybersecurity of covered hardware and software products with digital elements. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-kr-ai-basic",
      "relation": "context",
      "rationale": "Republic of Korea: AI Basic Act asks: What use category applies, and what information and oversight arrangements need examination? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Republic of Korea: AI Basic Act, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Republic of Korea: AI Basic Act, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.msit.go.kr/eng/bbs/view.do?bbsSeqNo=42&mId=4&mPid=2&nttSeqNo=1214&sCode=eng"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-cn-generative",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The measures address generative AI services offered to the public within China, including data practices, service responsibilities and complaint handling. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.cac.gov.cn/2023-07/13/c_1690898327029107.htm"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-jp-ai-promotion",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Japan’s AI law organizes promotion of AI research and use alongside attention to risks. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www8.cao.go.jp/cstp/ai/ai_act/ai_act.html"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-in-dpdp",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: India’s digital-personal-data framework addresses lawful processing, organizational responsibilities and individuals’ rights. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.pib.gov.in/PressReleseDetailm.aspx?PRID=2190655&lang=2&reg=48"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-br-lgpd",
      "relation": "context",
      "rationale": "Review-request records can motivate a scoped documentary influence question, while the legal right must not be relabeled as a universal guarantee of human review.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Brazil: data protection and review, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Brazil: data protection and review, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.gov.br/anpd/pt-br/assuntos/titular-de-dados/direito-dos-titulares"
    },
    {
      "program_id": "hit",
      "topic_id": "reg-institutional-commitments",
      "relation": "context",
      "rationale": "Procurement, contracts and stated purposes asks: What did the institution and its suppliers commit to, and what evidence could show whether those commitments were met? The topic offers a possible setting in which human influence may matter, but HIT’s single preserved comparison did not evaluate this instrument’s statutory requirements.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Procurement, contracts and stated purposes, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Procurement, contracts and stated purposes, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "iso-42001",
      "relation": "context",
      "rationale": "AI management systems · ISO/IEC 42001:2023 asks: What evidence shows that the organization's AI responsibilities and review processes operate in practice? The reference supplies governance vocabulary or expectations; HIT’s documentary ratings and agreement claims remain tied to their stated scoring contract.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by AI management systems · ISO/IEC 42001:2023, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI management systems · ISO/IEC 42001:2023, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.iso.org/standard/42001"
    },
    {
      "program_id": "hit",
      "topic_id": "iso-23894",
      "relation": "context",
      "rationale": "AI risk management · ISO/IEC 23894:2023 asks: Which risks arise in this use, who addresses them, and what evidence supports the response? The reference supplies governance vocabulary or expectations; HIT’s documentary ratings and agreement claims remain tied to their stated scoring contract.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by AI risk management · ISO/IEC 23894:2023, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI risk management · ISO/IEC 23894:2023, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.iso.org/standard/77304.html"
    },
    {
      "program_id": "hit",
      "topic_id": "iso-42005",
      "relation": "context",
      "rationale": "AI impact assessment · ISO/IEC 42005:2025 asks: Whose interests could be affected, and what changes when new evidence of impact emerges? The reference supplies governance vocabulary or expectations; HIT’s documentary ratings and agreement claims remain tied to their stated scoring contract.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by AI impact assessment · ISO/IEC 42005:2025, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI impact assessment · ISO/IEC 42005:2025, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.iso.org/standard/42005"
    },
    {
      "program_id": "hit",
      "topic_id": "iso-22989",
      "relation": "context",
      "rationale": "Shared AI terminology · ISO/IEC 22989:2022 asks: Are the people examining this decision using the same terms for the system and its activities? The reference supplies governance vocabulary or expectations; HIT’s documentary ratings and agreement claims remain tied to their stated scoring contract.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Shared AI terminology · ISO/IEC 22989:2022, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Shared AI terminology · ISO/IEC 22989:2022, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.iso.org/standard/74296.html"
    },
    {
      "program_id": "hit",
      "topic_id": "nist-ai-rmf-1-0",
      "relation": "context",
      "rationale": "AI Risk Management Framework · NIST AI RMF 1.0 asks: How do the identified risks, evaluation findings and management decisions connect for this use? The reference supplies governance vocabulary or expectations; HIT’s documentary ratings and agreement claims remain tied to their stated scoring contract.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by AI Risk Management Framework · NIST AI RMF 1.0, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI Risk Management Framework · NIST AI RMF 1.0, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "hit",
      "topic_id": "oecd-ai-principles",
      "relation": "context",
      "rationale": "Trustworthy AI principles · OECD asks: How can affected people understand, question and seek an accountable response to this AI use? The reference supplies governance vocabulary or expectations; HIT’s documentary ratings and agreement claims remain tied to their stated scoring contract.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Trustworthy AI principles · OECD, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Trustworthy AI principles · OECD, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://oecd.ai/en/ai-principles"
    },
    {
      "program_id": "hit",
      "topic_id": "unesco-ai-ethics",
      "relation": "context",
      "rationale": "Ethics of AI · UNESCO Recommendation asks: Whose rights and dignity are at stake, and who remains responsible for responding to harm? The reference supplies governance vocabulary or expectations; HIT’s documentary ratings and agreement claims remain tied to their stated scoring contract.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Ethics of AI · UNESCO Recommendation, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Ethics of AI · UNESCO Recommendation, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.unesco.org/en/artificial-intelligence/recommendation-ethics"
    },
    {
      "program_id": "hit",
      "topic_id": "owasp-llm-top-10-2025",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Community security guidance describing common risks in applications using large language models, including prompt injection, sensitive information disclosure and excessive agency. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "hit",
      "topic_id": "mitre-atlas",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: A living knowledge base of adversary tactics and techniques involving AI, informed by observed attacks and realistic demonstrations. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "hit",
      "topic_id": "nist-digital-identity-4",
      "relation": "context",
      "rationale": "Digital identity · NIST SP 800-63-4 asks: Whose identity was established, by what assurance process, and what separate authority governed the action? The reference supplies governance vocabulary or expectations; HIT’s documentary ratings and agreement claims remain tied to their stated scoring contract.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Digital identity · NIST SP 800-63-4, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Digital identity · NIST SP 800-63-4, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "hit",
      "topic_id": "nist-generative-ai-profile",
      "relation": "context",
      "rationale": "Generative AI risk profile · NIST AI 600-1 asks: Which generative AI risks matter in this deployment, and what evidence supports the chosen controls? The reference supplies governance vocabulary or expectations; HIT’s documentary ratings and agreement claims remain tied to their stated scoring contract.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Generative AI risk profile · NIST AI 600-1, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Generative AI risk profile · NIST AI 600-1, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence"
    },
    {
      "program_id": "hit",
      "topic_id": "iso-27001",
      "relation": "context",
      "rationale": "Information security management · ISO/IEC 27001:2022 asks: What protects the decision's data and records from unauthorized access, alteration or loss? The reference supplies governance vocabulary or expectations; HIT’s documentary ratings and agreement claims remain tied to their stated scoring contract.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Information security management · ISO/IEC 27001:2022, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Information security management · ISO/IEC 27001:2022, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.iso.org/standard/27001"
    },
    {
      "program_id": "hit",
      "topic_id": "roles-leadership",
      "relation": "context",
      "rationale": "Leadership and accountable ownership asks: Who must act when a concern exceeds the system owner’s authority? This role can affect the surrounding governance arrangement, while HIT still needs a bounded documentary question and defined scorer remit.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Leadership and accountable ownership, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Leadership and accountable ownership, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "roles-delivery",
      "relation": "context",
      "rationale": "Developers, suppliers and deployers asks: Which organization can change the component involved, and how does a concern reach it? This role can affect the surrounding governance arrangement, while HIT still needs a bounded documentary question and defined scorer remit.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Developers, suppliers and deployers, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Developers, suppliers and deployers, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "roles-domain-users",
      "relation": "direct",
      "rationale": "HIT’s documentary account of human influence needs the reviewer’s task expertise, information and working conditions to be specified.",
      "investigation_question": "Does the person handling the decision have the information, time and expertise needed to question it?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Domain specialists and frontline users criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "hit",
      "topic_id": "roles-reviewers",
      "relation": "direct",
      "rationale": "Reviewer remit and source access bear directly on whether independent scorers can assess the same human-influence claim under one contract.",
      "investigation_question": "What can the reviewer inspect, and who must respond to an unresolved finding?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Reviewers and independent assessors criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "roles-affected-people",
      "relation": "direct",
      "rationale": "Where a challenge produces a retained record, HIT can examine its route and recorded effect without assuming effective remedy.",
      "investigation_question": "Can an affected person raise a concern and obtain an intelligible response?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Affected people and routes to challenge criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "roles-intervention",
      "relation": "direct",
      "rationale": "HIT distinguishes a person’s stated authority from evidence that their judgment could influence what followed.",
      "investigation_question": "If a person challenges the decision, who can change what happens next?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Authority to intervene and repair criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "hit",
      "topic_id": "controls-inventory",
      "relation": "context",
      "rationale": "Inventories and change records asks: Which version and intended use does this decision or test result concern? The arrangement affects what scorers can inspect or what actions are possible, without showing that human judgment changed the outcome.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Inventories and change records, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Inventories and change records, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "controls-data",
      "relation": "context",
      "rationale": "Data handling and retained records asks: Can the relevant record be retrieved and examined without exposing information beyond the reviewer’s authority? The arrangement affects what scorers can inspect or what actions are possible, without showing that human judgment changed the outcome.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Data handling and retained records, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Data handling and retained records, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "hit",
      "topic_id": "controls-access",
      "relation": "direct",
      "rationale": "Authority and access records help establish which documented interventions the person was permitted to make.",
      "investigation_question": "Which identity and permission allowed the action, and who could revoke that permission?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Identity, permissions and delegation criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "hit",
      "topic_id": "controls-intervention",
      "relation": "direct",
      "rationale": "The request, system response and subsequent action provide observable records for examining human influence rather than counting a reviewer’s presence.",
      "investigation_question": "Can the intervention reach the relevant action before its effects become irreversible?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Stopping, containment and recovery criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "controls-monitoring",
      "relation": "direct",
      "rationale": "Logs and follow-up records can connect a human concern to a response, while remaining insufficient to establish what the person understood.",
      "investigation_question": "What happens after a warning is recorded, and how is the response examined?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Logs, incidents and follow-up criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "controls-boundaries",
      "relation": "context",
      "rationale": "Supplier and agent action boundaries asks: Could the system act beyond the intended scope, and which boundary would prevent or contain it? The arrangement affects what scorers can inspect or what actions are possible, without showing that human judgment changed the outcome.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Supplier and agent action boundaries, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Supplier and agent action boundaries, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "hit",
      "topic_id": "evaluation-model",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Examine what a model can do using stated tasks, inputs and assessment methods. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "evaluation-application",
      "relation": "context",
      "rationale": "Application and mission-specific tests asks: How closely do the test conditions match the setting in which people will rely on the result? The topic could inform a future HIT application or recheck; current-contract replication and wider reliability remain open.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Application and mission-specific tests, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Application and mission-specific tests, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "evaluation-control",
      "relation": "direct",
      "rationale": "The intervention-and-authority topic gives a concrete outcome question against which a documentary influence assessment can be checked.",
      "investigation_question": "When the reviewer tried to intervene, what actually changed?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Tests of intervention and authority criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "hit",
      "topic_id": "evaluation-adversarial",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Examine plausible attacks, misuse and component failures in a controlled test setting. The declared Human Influence Telemetry work addresses what the documentary record supports about human judgment and how scorers could assess that claim under one contract; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "hit",
      "topic_id": "evaluation-human-factors",
      "relation": "direct",
      "rationale": "HIT can organize records of time, workload and available information; behavioral claims remain beyond documentary evidence alone.",
      "investigation_question": "What conditions helped or prevented the person from examining and challenging the output?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Human judgment and working conditions criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "hit",
      "topic_id": "evaluation-reproducibility",
      "relation": "direct",
      "rationale": "The preserved one-packet comparison demonstrates why identical packets, rule versions and retained judgments are necessary to interpret reviewer agreement.",
      "investigation_question": "Can another assessor inspect or repeat the procedure and understand why results differ?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Reproducibility and retained test artifacts criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "evaluation-regression",
      "relation": "context",
      "rationale": "Rechecking after changes asks: What changed, which claims could it affect, and what was retested? The topic could inform a future HIT application or recheck; current-contract replication and wider reliability remain open.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Rechecking after changes, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Rechecking after changes, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "hit",
      "topic_id": "evidence-claims",
      "relation": "direct",
      "rationale": "A specified scoring contract is needed to know which human-influence conclusion a HIT rating actually supports.",
      "investigation_question": "Exactly what conclusion is the reader being asked to accept?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Claims, criteria and scope criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "hit",
      "topic_id": "evidence-provenance",
      "relation": "direct",
      "rationale": "Source identity and missingness affect what scorers may legitimately infer from the packet used for HIT assessment.",
      "investigation_question": "What is the source of this evidence, and what relevant material is unavailable?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Sources, provenance and missing records criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.w3.org/TR/prov-dm/"
    },
    {
      "program_id": "hit",
      "topic_id": "evidence-reconstruction",
      "relation": "direct",
      "rationale": "The method examines the documentary connection between human judgment, intervention and subsequent decision events.",
      "investigation_question": "What can the available record establish about the intervention and what followed it?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Reconstructing the decision and intervention criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "hit",
      "topic_id": "evidence-uncertainty",
      "relation": "direct",
      "rationale": "Missing or conflicting records must remain unresolved under the scoring contract rather than becoming an assumed absence of human influence.",
      "investigation_question": "What would weaken this conclusion, and which questions remain unresolved?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Conflicting evidence and unresolved findings criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "hit",
      "topic_id": "evidence-review",
      "relation": "direct",
      "rationale": "A second scorer needs the claim, admissible record and reasons in inspectable form to compare judgments meaningfully.",
      "investigation_question": "Can another reader trace the conclusion to its evidence and challenge the reasoning?",
      "evidence_needed": [
        "A frozen decision packet identifying the reviewer, intervention and subsequent recorded action.",
        "The exact HIT contract, independent initial ratings where available and preserved disagreements.",
        "The specifically selected Review, challenge and communication criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "hit",
      "topic_id": "evidence-correction",
      "relation": "context",
      "rationale": "Correction records and evidence of effects asks: What evidence shows whether the correction reached the people or decisions it was meant to affect? The topic concerns the response to an assessment; documentary human-influence ratings alone do not establish remediation or institutional effectiveness.",
      "investigation_question": "Before using Human Influence Telemetry in a setting informed by Correction records and evidence of effects, which source condition, actor and workflow would need to be selected to examine what the documentary record supports about human judgment and how scorers could assess that claim under one contract?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Correction records and evidence of effects, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Methodological relevance only. Agreement on one historical packet under an earlier HIT contract does not establish general reliability, current-contract replication or legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/human-influence-telemetry/blob/6e2aabcd07912c7c5df4b9a20c069745db87923d/validation/results/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-consumer",
      "relation": "context",
      "rationale": "U.S. consumer protection asks: What evidence supports the claims made to customers about this system? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by U.S. consumer protection, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for U.S. consumer protection, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.ftc.gov/legal-library/browse/statutes/federal-trade-commission-act"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-equality",
      "relation": "context",
      "rationale": "Employment equality and disability asks: Can a person challenge a technology-assisted employment decision and obtain an accessible review? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Employment equality and disability, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Employment equality and disability, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.eeoc.gov/fact-sheet/federal-laws-prohibiting-job-discrimination-questions-and-answers"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-credit",
      "relation": "context",
      "rationale": "Credit decisions and reasons asks: Can the creditor reconstruct and accurately explain the principal reasons for the adverse decision? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Credit decisions and reasons, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Credit decisions and reasons, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.consumerfinance.gov/compliance/compliance-resources/other-applicable-requirements/equal-credit-opportunity-act/"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-medical",
      "relation": "context",
      "rationale": "Medical-device software asks: What intended use, operating conditions and evidence support the device function being examined? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Medical-device software, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Medical-device software, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.fda.gov/regulatory-information/search-fda-guidance-documents/policy-device-software-functions-and-mobile-medical-applications"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-california",
      "relation": "context",
      "rationale": "California privacy and automated decisions asks: Which personal data and automated decisions are covered, and how would the business respond to a valid request? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by California privacy and automated decisions, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for California privacy and automated decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.cppa.ca.gov/regulations/"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-california-employment",
      "relation": "context",
      "rationale": "California: employment decision systems asks: Can retained records show how the system affected the employment decision and support examination of discrimination concerns? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by California: employment decision systems, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for California: employment decision systems, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://calcivilrights.ca.gov/2025/06/30/civil-rights-council-secures-approval-for-regulations-to-protect-against-employment-discrimination-related-to-artificial-intelligence/"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-california-frontier",
      "relation": "context",
      "rationale": "California: frontier-model transparency asks: What evidence connects the published framework to risk assessments, mitigations and the handling of reported concerns? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by California: frontier-model transparency, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for California: frontier-model transparency, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://oag.ca.gov/sb53"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-california-companions",
      "relation": "context",
      "rationale": "California: companion-chatbot safeguards asks: Can users recognize a simulated relationship, step away and reach human crisis support, and what evidence documents those safeguards? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by California: companion-chatbot safeguards, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for California: companion-chatbot safeguards, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260SB243"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-colorado",
      "relation": "context",
      "rationale": "Colorado: consequential decisions asks: What information would let a person understand the technology’s role and request a meaningful reconsideration? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Colorado: consequential decisions, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Colorado: consequential decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/sb26-189"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-colorado-health-review",
      "relation": "direct",
      "rationale": "The topic explicitly asks for retained audit evidence of human review and changed denials, supplying a bounded control-evidence question for corpus development.",
      "investigation_question": "What evidence would show that a qualified reviewer examined the patient’s circumstances and could change a proposed denial before it was issued?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Colorado: AI-assisted health-care review criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1139"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-colorado-psychotherapy",
      "relation": "context",
      "rationale": "Colorado: AI use in psychotherapy asks: What evidence distinguishes active professional participation from later review, and shows that refusing or withdrawing recording consent changed system behavior? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Colorado: AI use in psychotherapy, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Colorado: AI use in psychotherapy, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1195"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-colorado-conversational-ai",
      "relation": "context",
      "rationale": "Colorado: conversational AI safeguards asks: What records would show that disclosures, crisis escalation and protections for minors operated during actual interactions? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Colorado: conversational AI safeguards, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Colorado: conversational AI safeguards, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1263"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-connecticut-employment",
      "relation": "context",
      "rationale": "Connecticut: automated employment decisions asks: What connects the notice, the system’s actual role in the decision and the institution’s response to testing findings? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Connecticut: automated employment decisions, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Connecticut: automated employment decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.cga.ct.gov/2026/ACT/PA/PDF/2026PA-00015-R00SB-00005-PA.PDF"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-illinois-employment",
      "relation": "context",
      "rationale": "Illinois: AI in employment decisions asks: Can the employer trace the tool’s role, examine discriminatory effects and show that required notice was provided? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Illinois: AI in employment decisions, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: AI in employment decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://ilga.gov/legislation/PublicActs/View/103-0804"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-illinois-psychological",
      "relation": "context",
      "rationale": "Illinois: AI support in psychological services asks: Can records show the professional’s review, responsibility and consent arrangements for the permitted support function? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Illinois: AI support in psychological services, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: AI support in psychological services, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://ilga.gov/Legislation/PublicActs/View/104-0054"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-illinois-video",
      "relation": "context",
      "rationale": "Illinois: AI video interviews asks: Can an applicant understand the use, withhold consent and obtain deletion across every recipient of the interview? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Illinois: AI video interviews, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: AI video interviews, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://my.ilga.gov/Legislation/ILCS/Articles?ActID=4015&Chapter=EMPLOYMENT&ChapterID=68&MajorTopic=BUSINESS+AND+EMPLOYMENT"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-illinois-biometric",
      "relation": "context",
      "rationale": "Illinois: biometric information privacy asks: What evidence connects consent and stated purpose to collection, access, onward disclosure and actual deletion? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Illinois: biometric information privacy, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: biometric information privacy, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.ilga.gov/legislation/ilcs/fulltext?DocName=074000140K15"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-illinois-frontier",
      "relation": "context",
      "rationale": "Illinois: frontier-model safety and audits asks: Can an independent auditor inspect the evidence needed to assess whether the developer follows its published framework? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Illinois: frontier-model safety and audits, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: frontier-model safety and audits, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.ilga.gov/documents/legislation/PublicActs/104/104-0538.htm"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-minnesota-profiling",
      "relation": "context",
      "rationale": "Minnesota: profiling and reevaluation asks: Did correcting the data produce a reevaluation, and what evidence establishes the resulting effect? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Minnesota: profiling and reevaluation, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Minnesota: profiling and reevaluation, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.ag.state.mn.us/Data-Privacy/Consumer/"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-new-york-government",
      "relation": "context",
      "rationale": "An AI inventory could identify systems for a prospective corpus sample; it does not itself supply an event showing whether a control operated, and the topic explicitly excludes superseded human-review duties.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by New York: agency AI inventory and disclosure, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for New York: agency AI inventory and disclosure, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/STT/103-E"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-new-york-raise",
      "relation": "context",
      "rationale": "New York: frontier-model transparency asks: What evidence would show that published safeguards informed deployment decisions and that an incident reached the responsible authority? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by New York: frontier-model transparency, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for New York: frontier-model transparency, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/bills/2025/S8828"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-new-york-companions",
      "relation": "context",
      "rationale": "Retained disclosure and crisis-referral records could motivate a bounded packet, but CEC cannot infer user understanding or a staffed handoff from a notice or referral event.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by New York: AI companion safeguards, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for New York: AI companion safeguards, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/GBS/1700"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-texas",
      "relation": "context",
      "rationale": "Texas: AI uses and disclosures asks: What records show that the relevant disclosure reached the person and that the system stayed within its permitted use? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Texas: AI uses and disclosures, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Texas: AI uses and disclosures, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://capitol.texas.gov/billlookup/BillSummary.aspx?Bill=HB149&LegSess=89R"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-utah-chatbots",
      "relation": "context",
      "rationale": "Utah: mental-health chatbots asks: Can the retained record establish that the required disclosure appeared at the relevant point in the interaction? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Utah: mental-health chatbots, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Utah: mental-health chatbots, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://le.utah.gov/xcode/Title13/Chapter72A/C13-72a-P2_2025050720250507.pdf"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-virginia-profiling",
      "relation": "context",
      "rationale": "Virginia: profiling and privacy requests asks: Can the institution show that an eligible opt-out request was implemented and a refused request could be appealed? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Virginia: profiling and privacy requests, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Virginia: profiling and privacy requests, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://law.lis.virginia.gov/vacode/title59.1/chapter53/section59.1-577/"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-wisconsin-political",
      "relation": "context",
      "rationale": "Wisconsin: AI disclosure in political communications asks: Does the published communication retain the required disclosure, and can its production and distribution be reconstructed? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Wisconsin: AI disclosure in political communications, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Wisconsin: AI disclosure in political communications, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://content.govdelivery.com/accounts/WIGOV/bulletins/391af46"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-wisconsin-insurance",
      "relation": "context",
      "rationale": "Wisconsin: insurance AI governance guidance asks: Can the insurer produce evidence that its AI program, testing and vendor oversight operate in the decisions under examination? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Wisconsin: insurance AI governance guidance, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Wisconsin: insurance AI governance guidance, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://oci.wi.gov/Pages/Regulation/Bulletin20250318AI.aspx"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-us-new-york-city-aedt",
      "relation": "context",
      "rationale": "New York City: employment-tool bias audits asks: Which tool and use did the audit examine, and can an affected person find the relevant audit information and notice? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by New York City: employment-tool bias audits, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for New York City: employment-tool bias audits, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.nyc.gov/site/dca/about/automated-employment-decision-tools.page"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-eu-prohibited",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The AI Act prohibits specified practices involving manipulation, exploitation, social scoring and certain biometric or other uses. The declared Control Evidence Corpus work addresses what a bounded packet could establish about control operation and when missing support must remain unresolved; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-5"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-eu-high-risk",
      "relation": "context",
      "rationale": "High-risk systems and requirements asks: What classification applies to this use, and which evidence would support the relevant requirements? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by High-risk systems and requirements, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for High-risk systems and requirements, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-6"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-eu-human-oversight",
      "relation": "direct",
      "rationale": "An oversight assertion can become a corpus question about which records would establish a usable intervention and its observed effect.",
      "investigation_question": "What evidence shows that a reviewer could use their authority, and what happened when they tried?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Human oversight criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02024R1689-20260727"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-eu-transparency",
      "relation": "context",
      "rationale": "Transparency and generated content asks: Would an affected person receive the relevant information in a form they can notice and understand? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Transparency and generated content, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Transparency and generated content, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-50"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-eu-gpai",
      "relation": "context",
      "rationale": "Provider information could supply model-version and capability context for a packet. General-purpose AI is a legal category distinct from AGI, and CEC does not evaluate provider compliance or AGI readiness.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by General-purpose AI models, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for General-purpose AI models, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-53"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-eu-value-chain",
      "relation": "context",
      "rationale": "Responsibilities across the value chain asks: Who is responsible for this version and use, and who can supply the information needed to examine it? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Responsibilities across the value chain, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Responsibilities across the value chain, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-25"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-eu-gdpr",
      "relation": "context",
      "rationale": "Personal data and automated decisions asks: What data supports the decision, and which information, correction or challenge rights apply to the person affected? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Personal data and automated decisions, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Personal data and automated decisions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-eu-nis2",
      "relation": "context",
      "rationale": "Cybersecurity of covered organizations asks: Can the institution identify a relevant cyber incident, contain its effects and preserve an accountable response? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Cybersecurity of covered organizations, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Cybersecurity of covered organizations, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/nis2-directive"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-eu-cra",
      "relation": "context",
      "rationale": "Cybersecurity of digital products asks: What evidence supports the product’s security claims and the handling of vulnerabilities over its support period? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Cybersecurity of digital products, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Cybersecurity of digital products, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-kr-ai-basic",
      "relation": "context",
      "rationale": "Republic of Korea: AI Basic Act asks: What use category applies, and what information and oversight arrangements need examination? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Republic of Korea: AI Basic Act, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Republic of Korea: AI Basic Act, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.msit.go.kr/eng/bbs/view.do?bbsSeqNo=42&mId=4&mPid=2&nttSeqNo=1214&sCode=eng"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-cn-generative",
      "relation": "context",
      "rationale": "China: generative AI services asks: Who provides the service, to which public, and what evidence supports its data and service practices? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by China: generative AI services, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for China: generative AI services, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.cac.gov.cn/2023-07/13/c_1690898327029107.htm"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-jp-ai-promotion",
      "relation": "context",
      "rationale": "Japan: AI development and use asks: How do responsibilities and relevant guidance translate into the way this institution develops or uses AI? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Japan: AI development and use, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Japan: AI development and use, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www8.cao.go.jp/cstp/ai/ai_act/ai_act.html"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-in-dpdp",
      "relation": "context",
      "rationale": "India: digital personal data asks: What personal data is needed, who is responsible for it, and how can a person exercise an applicable right? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by India: digital personal data, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for India: digital personal data, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.pib.gov.in/PressReleseDetailm.aspx?PRID=2190655&lang=2&reg=48"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-br-lgpd",
      "relation": "context",
      "rationale": "Brazil: data protection and review asks: What record would let a person understand and contest a covered automated decision? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Brazil: data protection and review, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Brazil: data protection and review, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.gov.br/anpd/pt-br/assuntos/titular-de-dados/direito-dos-titulares"
    },
    {
      "program_id": "cec",
      "topic_id": "reg-institutional-commitments",
      "relation": "context",
      "rationale": "Procurement, contracts and stated purposes asks: What did the institution and its suppliers commit to, and what evidence could show whether those commitments were met? The topic can motivate a candidate evidence packet, provided its actor, use and selected requirement are scoped first; CEC has no independently coded empirical events or approved corpus release.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Procurement, contracts and stated purposes, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Procurement, contracts and stated purposes, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "iso-42001",
      "relation": "context",
      "rationale": "AI management systems · ISO/IEC 42001:2023 asks: What evidence shows that the organization's AI responsibilities and review processes operate in practice? The reference can inform a candidate control question or evidence field, but imported guidance does not automatically become an admissible corpus item or a scoring rule.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by AI management systems · ISO/IEC 42001:2023, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI management systems · ISO/IEC 42001:2023, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.iso.org/standard/42001"
    },
    {
      "program_id": "cec",
      "topic_id": "iso-23894",
      "relation": "context",
      "rationale": "AI risk management · ISO/IEC 23894:2023 asks: Which risks arise in this use, who addresses them, and what evidence supports the response? The reference can inform a candidate control question or evidence field, but imported guidance does not automatically become an admissible corpus item or a scoring rule.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by AI risk management · ISO/IEC 23894:2023, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI risk management · ISO/IEC 23894:2023, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.iso.org/standard/77304.html"
    },
    {
      "program_id": "cec",
      "topic_id": "iso-42005",
      "relation": "context",
      "rationale": "AI impact assessment · ISO/IEC 42005:2025 asks: Whose interests could be affected, and what changes when new evidence of impact emerges? The reference can inform a candidate control question or evidence field, but imported guidance does not automatically become an admissible corpus item or a scoring rule.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by AI impact assessment · ISO/IEC 42005:2025, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI impact assessment · ISO/IEC 42005:2025, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.iso.org/standard/42005"
    },
    {
      "program_id": "cec",
      "topic_id": "iso-22989",
      "relation": "context",
      "rationale": "Shared AI terminology · ISO/IEC 22989:2022 asks: Are the people examining this decision using the same terms for the system and its activities? The reference can inform a candidate control question or evidence field, but imported guidance does not automatically become an admissible corpus item or a scoring rule.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Shared AI terminology · ISO/IEC 22989:2022, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Shared AI terminology · ISO/IEC 22989:2022, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.iso.org/standard/74296.html"
    },
    {
      "program_id": "cec",
      "topic_id": "nist-ai-rmf-1-0",
      "relation": "context",
      "rationale": "AI Risk Management Framework · NIST AI RMF 1.0 asks: How do the identified risks, evaluation findings and management decisions connect for this use? The reference can inform a candidate control question or evidence field, but imported guidance does not automatically become an admissible corpus item or a scoring rule.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by AI Risk Management Framework · NIST AI RMF 1.0, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI Risk Management Framework · NIST AI RMF 1.0, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "cec",
      "topic_id": "oecd-ai-principles",
      "relation": "context",
      "rationale": "Trustworthy AI principles · OECD asks: How can affected people understand, question and seek an accountable response to this AI use? The reference can inform a candidate control question or evidence field, but imported guidance does not automatically become an admissible corpus item or a scoring rule.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Trustworthy AI principles · OECD, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Trustworthy AI principles · OECD, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://oecd.ai/en/ai-principles"
    },
    {
      "program_id": "cec",
      "topic_id": "unesco-ai-ethics",
      "relation": "context",
      "rationale": "Ethics of AI · UNESCO Recommendation asks: Whose rights and dignity are at stake, and who remains responsible for responding to harm? The reference can inform a candidate control question or evidence field, but imported guidance does not automatically become an admissible corpus item or a scoring rule.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Ethics of AI · UNESCO Recommendation, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Ethics of AI · UNESCO Recommendation, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.unesco.org/en/artificial-intelligence/recommendation-ethics"
    },
    {
      "program_id": "cec",
      "topic_id": "owasp-llm-top-10-2025",
      "relation": "context",
      "rationale": "LLM application security risks · OWASP Top 10 (2025) asks: Can untrusted input cause the application to disclose information or act beyond its intended authority? The reference can inform a candidate control question or evidence field, but imported guidance does not automatically become an admissible corpus item or a scoring rule.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by LLM application security risks · OWASP Top 10 (2025), which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for LLM application security risks · OWASP Top 10 (2025), including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "cec",
      "topic_id": "mitre-atlas",
      "relation": "context",
      "rationale": "Adversarial threat knowledge · MITRE ATLAS asks: Which documented attack paths are plausible here, and what evidence tests the relevant defenses? The reference can inform a candidate control question or evidence field, but imported guidance does not automatically become an admissible corpus item or a scoring rule.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Adversarial threat knowledge · MITRE ATLAS, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Adversarial threat knowledge · MITRE ATLAS, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "cec",
      "topic_id": "nist-digital-identity-4",
      "relation": "context",
      "rationale": "Digital identity · NIST SP 800-63-4 asks: Whose identity was established, by what assurance process, and what separate authority governed the action? The reference can inform a candidate control question or evidence field, but imported guidance does not automatically become an admissible corpus item or a scoring rule.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Digital identity · NIST SP 800-63-4, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Digital identity · NIST SP 800-63-4, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "cec",
      "topic_id": "nist-generative-ai-profile",
      "relation": "context",
      "rationale": "Generative AI risk profile · NIST AI 600-1 asks: Which generative AI risks matter in this deployment, and what evidence supports the chosen controls? The reference can inform a candidate control question or evidence field, but imported guidance does not automatically become an admissible corpus item or a scoring rule.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Generative AI risk profile · NIST AI 600-1, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Generative AI risk profile · NIST AI 600-1, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence"
    },
    {
      "program_id": "cec",
      "topic_id": "iso-27001",
      "relation": "context",
      "rationale": "Information security management · ISO/IEC 27001:2022 asks: What protects the decision's data and records from unauthorized access, alteration or loss? The reference can inform a candidate control question or evidence field, but imported guidance does not automatically become an admissible corpus item or a scoring rule.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Information security management · ISO/IEC 27001:2022, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Information security management · ISO/IEC 27001:2022, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.iso.org/standard/27001"
    },
    {
      "program_id": "cec",
      "topic_id": "roles-leadership",
      "relation": "context",
      "rationale": "Leadership and accountable ownership asks: Who must act when a concern exceeds the system owner’s authority? The role can identify an evidence producer, affected party or responsible actor in a prospective packet; those roles and rights must be agreed for the specific pilot.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Leadership and accountable ownership, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Leadership and accountable ownership, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "roles-delivery",
      "relation": "context",
      "rationale": "Developers, suppliers and deployers asks: Which organization can change the component involved, and how does a concern reach it? The role can identify an evidence producer, affected party or responsible actor in a prospective packet; those roles and rights must be agreed for the specific pilot.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Developers, suppliers and deployers, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Developers, suppliers and deployers, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "roles-domain-users",
      "relation": "context",
      "rationale": "Domain specialists and frontline users asks: Does the person handling the decision have the information, time and expertise needed to question it? The role can identify an evidence producer, affected party or responsible actor in a prospective packet; those roles and rights must be agreed for the specific pilot.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Domain specialists and frontline users, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Domain specialists and frontline users, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "cec",
      "topic_id": "roles-reviewers",
      "relation": "direct",
      "rationale": "CEC’s prospective independent coding and adjudication require defined reviewer roles, access and independence; those pilot roles remain unfilled.",
      "investigation_question": "What can the reviewer inspect, and who must respond to an unresolved finding?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Reviewers and independent assessors criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "roles-affected-people",
      "relation": "context",
      "rationale": "Affected people and routes to challenge asks: Can an affected person raise a concern and obtain an intelligible response? The role can identify an evidence producer, affected party or responsible actor in a prospective packet; those roles and rights must be agreed for the specific pilot.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Affected people and routes to challenge, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Affected people and routes to challenge, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "roles-intervention",
      "relation": "direct",
      "rationale": "Evidence about who could act is needed to distinguish an authorized intervention from a command or acknowledgment without authority.",
      "investigation_question": "If a person challenges the decision, who can change what happens next?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Authority to intervene and repair criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "cec",
      "topic_id": "controls-inventory",
      "relation": "direct",
      "rationale": "Identifying system and version prevents a control-evidence packet from silently mixing observations from different configurations.",
      "investigation_question": "Which version and intended use does this decision or test result concern?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Inventories and change records criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "controls-data",
      "relation": "direct",
      "rationale": "Record access, retention and sensitive-data handling are prerequisites for building a corpus whose surviving evidence can actually be inspected.",
      "investigation_question": "Can the relevant record be retrieved and examined without exposing information beyond the reviewer’s authority?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Data handling and retained records criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "cec",
      "topic_id": "controls-access",
      "relation": "context",
      "rationale": "Identity, permissions and delegation asks: Which identity and permission allowed the action, and who could revoke that permission? The topic can supply background control configuration for a prospective packet; a synthetic representation does not establish operational enforcement.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Identity, permissions and delegation, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Identity, permissions and delegation, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "cec",
      "topic_id": "controls-intervention",
      "relation": "direct",
      "rationale": "CEC’s synthetic demonstrations distinguish an issued stop, propagation and mitigation, matching the separate control stages in this topic.",
      "investigation_question": "Can the intervention reach the relevant action before its effects become irreversible?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Stopping, containment and recovery criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "controls-monitoring",
      "relation": "direct",
      "rationale": "Logs, incidents and follow-up are candidate source records for a bounded event packet; their existence alone does not establish an effective response.",
      "investigation_question": "What happens after a warning is recorded, and how is the response examined?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Logs, incidents and follow-up criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "controls-boundaries",
      "relation": "direct",
      "rationale": "Action scope and external dependencies define which effects a packet can observe and where its evidence boundary ends.",
      "investigation_question": "Could the system act beyond the intended scope, and which boundary would prevent or contain it?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Supplier and agent action boundaries criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "cec",
      "topic_id": "evaluation-model",
      "relation": "context",
      "rationale": "Model capabilities and limitations asks: What does this result establish about the model, and what was not tested? The topic can inform scenario or sampling design, but CEC’s present synthetic comparisons do not establish model capability or human behavior.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Model capabilities and limitations, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Model capabilities and limitations, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "evaluation-application",
      "relation": "direct",
      "rationale": "The intended task and observable environment define what a future empirical control-evidence pilot could legitimately include.",
      "investigation_question": "How closely do the test conditions match the setting in which people will rely on the result?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Application and mission-specific tests criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "evaluation-control",
      "relation": "direct",
      "rationale": "Paired effective, ineffective and insufficient-evidence cases directly serve CEC’s development question about reconstructing control operation.",
      "investigation_question": "When the reviewer tried to intervene, what actually changed?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Tests of intervention and authority criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "cec",
      "topic_id": "evaluation-adversarial",
      "relation": "direct",
      "rationale": "Seeded failures can test whether a development packet and assessor distinguish a control failure from an absent or misleading record.",
      "investigation_question": "Which failure or attack paths were examined, and what happened at the relevant boundary?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Adversarial tests and failure injection criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "cec",
      "topic_id": "evaluation-human-factors",
      "relation": "context",
      "rationale": "Human judgment and working conditions asks: What conditions helped or prevented the person from examining and challenging the output? The topic can inform scenario or sampling design, but CEC’s present synthetic comparisons do not establish model capability or human behavior.",
      "investigation_question": "Before using Control Evidence Corpus in a setting informed by Human judgment and working conditions, which source condition, actor and workflow would need to be selected to examine what a bounded packet could establish about control operation and when missing support must remain unresolved?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Human judgment and working conditions, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "cec",
      "topic_id": "evaluation-reproducibility",
      "relation": "direct",
      "rationale": "Versioned packets, instructions, references and retained disagreements support inspection of CEC’s synthetic instruction comparison.",
      "investigation_question": "Can another assessor inspect or repeat the procedure and understand why results differ?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Reproducibility and retained test artifacts criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "evaluation-regression",
      "relation": "direct",
      "rationale": "Rechecking after packet, instruction or evaluator changes prevents earlier synthetic results from silently transferring to a new setup.",
      "investigation_question": "What changed, which claims could it affect, and what was retested?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Rechecking after changes criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cec",
      "topic_id": "evidence-claims",
      "relation": "direct",
      "rationale": "A corpus item needs a bounded control question and claim so assessors know which conclusion the packet is meant to support.",
      "investigation_question": "Exactly what conclusion is the reader being asked to accept?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Claims, criteria and scope criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "cec",
      "topic_id": "evidence-provenance",
      "relation": "direct",
      "rationale": "Traceability and missingness are central to CEC’s distinction between surviving evidence and an affirmative control finding.",
      "investigation_question": "What is the source of this evidence, and what relevant material is unavailable?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Sources, provenance and missing records criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.w3.org/TR/prov-dm/"
    },
    {
      "program_id": "cec",
      "topic_id": "evidence-reconstruction",
      "relation": "direct",
      "rationale": "Reconstructing action, propagation and mitigation from a bounded packet is CEC’s stated development purpose.",
      "investigation_question": "What can the available record establish about the intervention and what followed it?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Reconstructing the decision and intervention criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "cec",
      "topic_id": "evidence-uncertainty",
      "relation": "direct",
      "rationale": "CEC explicitly preserves missing-evidence outcomes as unresolved rather than automatically labelling a control ineffective.",
      "investigation_question": "What would weaken this conclusion, and which questions remain unresolved?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Conflicting evidence and unresolved findings criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "cec",
      "topic_id": "evidence-review",
      "relation": "direct",
      "rationale": "Prospective independent initial ratings and adjudication require a record that exposes the evidence and disagreement behind each corpus judgment. The empirical pilot roles remain unfilled.",
      "investigation_question": "Can another reader trace the conclusion to its evidence and challenge the reasoning?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Review, challenge and communication criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "cec",
      "topic_id": "evidence-correction",
      "relation": "direct",
      "rationale": "Mitigation and correction records help distinguish completion of a command from evidence that its intended effect reached the affected workflow.",
      "investigation_question": "What evidence shows whether the correction reached the people or decisions it was meant to affect?",
      "evidence_needed": [
        "A rights-cleared bounded event packet separating the control request, propagation and independently retained effect evidence.",
        "A frozen coding contract, missingness record and retained initial ratings/adjudication; current demonstrations remain synthetic.",
        "The specifically selected Correction records and evidence of effects criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Development relevance only. Synthetic examples and authored references do not establish independent human validity, operational effectiveness or legal compliance; an empirical pilot and approved corpus release remain forthcoming.",
      "program_evidence_url": "https://github.com/node-and-norm/node-norm-control-evidence/blob/a3a0d9c67997eb958100413ab54d213053d25c1a/research/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-consumer",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Consumer-protection rules can apply to claims and conduct involving AI products and services. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.ftc.gov/legal-library/browse/statutes/federal-trade-commission-act",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-equality",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Employment decisions involving software or AI remain subject to applicable discrimination laws. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.eeoc.gov/fact-sheet/federal-laws-prohibiting-job-discrimination-questions-and-answers",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-credit",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Credit rules address discrimination and notification of adverse action. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.consumerfinance.gov/compliance/compliance-resources/other-applicable-requirements/equal-credit-opportunity-act/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-medical",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: FDA guidance distinguishes software functions subject to device oversight from other functions. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.fda.gov/regulatory-information/search-fda-guidance-documents/policy-device-software-functions-and-mobile-medical-applications",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-california",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: California’s privacy framework includes adopted rules on specified uses of automated decisionmaking technology, risk assessments and cybersecurity audits. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.cppa.ca.gov/regulations/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-california-employment",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: These regulations clarify how employment discrimination protections apply to automated decision systems. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://calcivilrights.ca.gov/2025/06/30/civil-rights-council-secures-approval-for-regulations-to-protect-against-employment-discrimination-related-to-artificial-intelligence/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-california-frontier",
      "relation": "context",
      "rationale": "California: frontier-model transparency asks: What evidence connects the published framework to risk assessments, mitigations and the handling of reported concerns? The reference supplies an external motivation for checking continued authority, but the current database qualification has no statutory implementation or legal-compliance endpoint.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by California: frontier-model transparency, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for California: frontier-model transparency, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://oag.ca.gov/sb53",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-california-companions",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: California requires covered companion-chatbot operators to identify AI when users could reasonably mistake it for a human and maintain published protocols addressing suicide and self-harm. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260SB243",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-colorado",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Colorado’s 2026 law addresses automated technology that materially influences specified consequential decisions. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://leg.colorado.gov/bills/sb26-189",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-colorado-health-review",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Colorado’s enacted law sets conditions for AI-assisted utilization review. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1139",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-colorado-psychotherapy",
      "relation": "context",
      "rationale": "Withdrawal of recording consent motivates a possible future permission-withdrawal scenario, but the present qualification neither processes psychotherapy data nor establishes that stopping recording satisfies the law.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Colorado: AI use in psychotherapy, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Colorado: AI use in psychotherapy, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1195",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-colorado-conversational-ai",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Colorado’s law establishes duties for covered conversational AI operators, including AI disclosures, crisis referral and escalation protocols, and restrictions on claims of professional equivalence. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1263",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-connecticut-employment",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The selected provisions address automated technology that materially influences employment decisions. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.cga.ct.gov/2026/ACT/PA/PDF/2026PA-00015-R00SB-00005-PA.PDF",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-illinois-employment",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The amendment addresses employer AI use that subjects employees to discrimination on protected grounds, and the use of ZIP codes as a protected-class proxy. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://ilga.gov/legislation/PublicActs/View/103-0804",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-illinois-psychological",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The act restricts AI use in therapy and psychotherapy. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://ilga.gov/Legislation/PublicActs/View/104-0054",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-illinois-video",
      "relation": "context",
      "rationale": "Consent and deletion across video recipients motivate separate lifecycle questions. The current no-new-commit endpoint does not erase copies or undo collection that occurred before withdrawal.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Illinois: AI video interviews, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: AI video interviews, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://my.ilga.gov/Legislation/ILCS/Articles?ActID=4015&Chapter=EMPLOYMENT&ChapterID=68&MajorTopic=BUSINESS+AND+EMPLOYMENT",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-illinois-biometric",
      "relation": "context",
      "rationale": "Biometric consent, onward disclosure and destruction provide context for authority boundaries, but revoking permission to create a new effect is not a test of biometric deletion or BIPA compliance.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Illinois: biometric information privacy, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: biometric information privacy, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.ilga.gov/legislation/ilcs/fulltext?DocName=074000140K15",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-illinois-frontier",
      "relation": "context",
      "rationale": "Illinois: frontier-model safety and audits asks: Can an independent auditor inspect the evidence needed to assess whether the developer follows its published framework? The reference supplies an external motivation for checking continued authority, but the current database qualification has no statutory implementation or legal-compliance endpoint.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Illinois: frontier-model safety and audits, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Illinois: frontier-model safety and audits, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.ilga.gov/documents/legislation/PublicActs/104/104-0538.htm",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-minnesota-profiling",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Consumers have specified rights concerning profiling used for decisions with legal or similarly significant effects. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.ag.state.mn.us/Data-Privacy/Consumer/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-new-york-government",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: New York requires a state-agency AI inventory and agency publication of lists describing automated employment decision tools. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/STT/103-E",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-new-york-raise",
      "relation": "context",
      "rationale": "New York: frontier-model transparency asks: What evidence would show that published safeguards informed deployment decisions and that an incident reached the responsible authority? The reference supplies an external motivation for checking continued authority, but the current database qualification has no statutory implementation or legal-compliance endpoint.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by New York: frontier-model transparency, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for New York: frontier-model transparency, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.nysenate.gov/legislation/bills/2025/S8828",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-new-york-companions",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: New York requires covered AI companion operators to provide clear, conspicuous notices that users are not communicating with a human and reasonable-efforts protocols for detecting self-harm or suicidal ideation and directing users to crisis services. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/GBS/1700",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-texas",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: TRAIGA sets disclosure requirements for specified government and healthcare uses, prohibits specified AI practices and provides for enforcement by the Attorney General. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://capitol.texas.gov/billlookup/BillSummary.aspx?Bill=HB149&LegSess=89R",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-utah-chatbots",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Suppliers of covered mental-health chatbots must disclose that the service is AI rather than a human. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://le.utah.gov/xcode/Title13/Chapter72A/C13-72a-P2_2025050720250507.pdf",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-virginia-profiling",
      "relation": "context",
      "rationale": "Implementing an eligible profiling opt-out can motivate a future withdrawal workflow. The current database endpoint does not establish eligibility, implement privacy-request appeals or evaluate a deployed profiling service.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Virginia: profiling and privacy requests, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Virginia: profiling and privacy requests, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://law.lis.virginia.gov/vacode/title59.1/chapter53/section59.1-577/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-wisconsin-political",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Covered political audio and video communications containing synthetic media substantially produced using generative AI require disclosures. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://content.govdelivery.com/accounts/WIGOV/bulletins/391af46",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-wisconsin-insurance",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The bulletin sets expectations for insurers’ written AI-system programs, accountability, risk controls, validation, monitoring and third-party oversight. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://oci.wi.gov/Pages/Regulation/Bulletin20250318AI.aspx",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-us-new-york-city-aedt",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Covered employers and employment agencies must obtain an independent bias audit before using an automated employment decision tool, keep the audit within the required annual period, publish audit information and give required notices to affected candidates or employees. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.nyc.gov/site/dca/about/automated-employment-decision-tools.page",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-eu-prohibited",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The AI Act prohibits specified practices involving manipulation, exploitation, social scoring and certain biometric or other uses. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-5",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-eu-high-risk",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: High-risk classification depends on specified product and use-case criteria. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-6",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-eu-human-oversight",
      "relation": "context",
      "rationale": "Human oversight asks: What evidence shows that a reviewer could use their authority, and what happened when they tried? The reference supplies an external motivation for checking continued authority, but the current database qualification has no statutory implementation or legal-compliance endpoint.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Human oversight, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Human oversight, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02024R1689-20260727",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-eu-transparency",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Article 50 addresses information about certain AI interactions and generated or manipulated content. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-50",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-eu-gpai",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The Act sets provider obligations for general-purpose AI models, including documentation, downstream information and copyright-related measures. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-53",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-eu-value-chain",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The Act assigns different responsibilities to providers, deployers and other actors. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-25",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-eu-gdpr",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Data-protection duties can apply to the personal data used in an AI workflow. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-eu-nis2",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: NIS2 addresses cybersecurity risk management and incident reporting for covered organizations and sectors. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/nis2-directive",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-eu-cra",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The Cyber Resilience Act addresses cybersecurity of covered hardware and software products with digital elements. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-kr-ai-basic",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Korea’s AI Basic Act combines support for AI development with rules concerning transparency, safety and high-impact AI. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.msit.go.kr/eng/bbs/view.do?bbsSeqNo=42&mId=4&mPid=2&nttSeqNo=1214&sCode=eng",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-cn-generative",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: The measures address generative AI services offered to the public within China, including data practices, service responsibilities and complaint handling. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.cac.gov.cn/2023-07/13/c_1690898327029107.htm",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-jp-ai-promotion",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Japan’s AI law organizes promotion of AI research and use alongside attention to risks. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www8.cao.go.jp/cstp/ai/ai_act/ai_act.html",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-in-dpdp",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: India’s digital-personal-data framework addresses lawful processing, organizational responsibilities and individuals’ rights. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.pib.gov.in/PressReleseDetailm.aspx?PRID=2190655&lang=2&reg=48",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-br-lgpd",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Brazil’s LGPD governs covered processing of personal data and provides rights for affected people. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.gov.br/anpd/pt-br/assuntos/titular-de-dados/direito-dos-titulares",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "reg-institutional-commitments",
      "relation": "context",
      "rationale": "Procurement, contracts and stated purposes asks: What did the institution and its suppliers commit to, and what evidence could show whether those commitments were met? The reference supplies an external motivation for checking continued authority, but the current database qualification has no statutory implementation or legal-compliance endpoint.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Procurement, contracts and stated purposes, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Procurement, contracts and stated purposes, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "iso-42001",
      "relation": "context",
      "rationale": "AI management systems · ISO/IEC 42001:2023 asks: What evidence shows that the organization's AI responsibilities and review processes operate in practice? The reference provides terminology or threat/control context; the qualified instrument tests a narrower ordering contract and does not implement the entire reference.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by AI management systems · ISO/IEC 42001:2023, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI management systems · ISO/IEC 42001:2023, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.iso.org/standard/42001",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "iso-23894",
      "relation": "context",
      "rationale": "AI risk management · ISO/IEC 23894:2023 asks: Which risks arise in this use, who addresses them, and what evidence supports the response? The reference provides terminology or threat/control context; the qualified instrument tests a narrower ordering contract and does not implement the entire reference.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by AI risk management · ISO/IEC 23894:2023, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI risk management · ISO/IEC 23894:2023, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.iso.org/standard/77304.html",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "iso-42005",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: An international standard providing guidance on assessing AI systems' potential effects on individuals, groups and society. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.iso.org/standard/42005",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "iso-22989",
      "relation": "context",
      "rationale": "Shared AI terminology · ISO/IEC 22989:2022 asks: Are the people examining this decision using the same terms for the system and its activities? The reference provides terminology or threat/control context; the qualified instrument tests a narrower ordering contract and does not implement the entire reference.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Shared AI terminology · ISO/IEC 22989:2022, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Shared AI terminology · ISO/IEC 22989:2022, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.iso.org/standard/74296.html",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "nist-ai-rmf-1-0",
      "relation": "context",
      "rationale": "AI Risk Management Framework · NIST AI RMF 1.0 asks: How do the identified risks, evaluation findings and management decisions connect for this use? The reference provides terminology or threat/control context; the qualified instrument tests a narrower ordering contract and does not implement the entire reference.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by AI Risk Management Framework · NIST AI RMF 1.0, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for AI Risk Management Framework · NIST AI RMF 1.0, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "oecd-ai-principles",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Intergovernmental principles, adopted in 2019 and updated in May 2024, address human rights, fairness, transparency, safety and accountability alongside inclusive growth. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://oecd.ai/en/ai-principles",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "unesco-ai-ethics",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Adopted in 2021, this ethical and policy recommendation places human rights and dignity at the center of AI governance. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.unesco.org/en/artificial-intelligence/recommendation-ethics",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "owasp-llm-top-10-2025",
      "relation": "context",
      "rationale": "LLM application security risks · OWASP Top 10 (2025) asks: Can untrusted input cause the application to disclose information or act beyond its intended authority? The reference provides terminology or threat/control context; the qualified instrument tests a narrower ordering contract and does not implement the entire reference.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by LLM application security risks · OWASP Top 10 (2025), which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for LLM application security risks · OWASP Top 10 (2025), including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "mitre-atlas",
      "relation": "context",
      "rationale": "Adversarial threat knowledge · MITRE ATLAS asks: Which documented attack paths are plausible here, and what evidence tests the relevant defenses? The reference provides terminology or threat/control context; the qualified instrument tests a narrower ordering contract and does not implement the entire reference.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Adversarial threat knowledge · MITRE ATLAS, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Adversarial threat knowledge · MITRE ATLAS, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://atlas.mitre.org/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "nist-digital-identity-4",
      "relation": "context",
      "rationale": "The qualification binds an asserted actor to authority within its test setup. NIST user identity proofing and federation provide background but do not specify a complete agent-delegation or revocation protocol.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Digital identity · NIST SP 800-63-4, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Digital identity · NIST SP 800-63-4, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "nist-generative-ai-profile",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: A July 2024 companion to AI RMF 1.0 addressing generative AI risks and suggested management actions. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "iso-27001",
      "relation": "context",
      "rationale": "Information security management · ISO/IEC 27001:2022 asks: What protects the decision's data and records from unauthorized access, alteration or loss? The reference provides terminology or threat/control context; the qualified instrument tests a narrower ordering contract and does not implement the entire reference.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Information security management · ISO/IEC 27001:2022, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Information security management · ISO/IEC 27001:2022, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.iso.org/standard/27001",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "roles-leadership",
      "relation": "context",
      "rationale": "Leadership and accountable ownership asks: Who must act when a concern exceeds the system owner’s authority? The role may matter in a future externally grounded workflow; it is not a measured human or organizational variable in the scripted qualification.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Leadership and accountable ownership, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Leadership and accountable ownership, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "roles-delivery",
      "relation": "context",
      "rationale": "Developers, suppliers and deployers asks: Which organization can change the component involved, and how does a concern reach it? The role may matter in a future externally grounded workflow; it is not a measured human or organizational variable in the scripted qualification.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Developers, suppliers and deployers, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Developers, suppliers and deployers, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "roles-domain-users",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Examine the expertise, information and working conditions of the people using AI in a particular task. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "roles-reviewers",
      "relation": "context",
      "rationale": "Reviewers and independent assessors asks: What can the reviewer inspect, and who must respond to an unresolved finding? The role may matter in a future externally grounded workflow; it is not a measured human or organizational variable in the scripted qualification.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Reviewers and independent assessors, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Reviewers and independent assessors, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "roles-affected-people",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Consider people who experience the decision, including those who never directly use the AI system. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "roles-intervention",
      "relation": "direct",
      "rationale": "The test must identify the actor authorized to withdraw permission and the authority root whose later use should be rejected.",
      "investigation_question": "If a person challenges the decision, who can change what happens next?",
      "evidence_needed": [
        "The frozen timing contract and ordered durable events for withdrawal, authority checks and protected commits.",
        "The matched admission-only and transaction-bound runs, including expected rejection causes, planned steps and retained checker corrections.",
        "The specifically selected Authority to intervene and repair criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "controls-inventory",
      "relation": "context",
      "rationale": "Inventories and change records asks: Which version and intended use does this decision or test result concern? This supporting arrangement affects the test environment, while the active endpoint remains whether an old permission produces a new protected commit after durable withdrawal.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Inventories and change records, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Inventories and change records, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "controls-data",
      "relation": "context",
      "rationale": "Data handling and retained records asks: Can the relevant record be retrieved and examined without exposing information beyond the reviewer’s authority? This supporting arrangement affects the test environment, while the active endpoint remains whether an old permission produces a new protected commit after durable withdrawal.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Data handling and retained records, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Data handling and retained records, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "controls-access",
      "relation": "direct",
      "rationale": "Delegated permission and withdrawal are the active study’s exact control object; checking identity alone does not determine whether authority remains active.",
      "investigation_question": "Which identity and permission allowed the action, and who could revoke that permission?",
      "evidence_needed": [
        "The frozen timing contract and ordered durable events for withdrawal, authority checks and protected commits.",
        "The matched admission-only and transaction-bound runs, including expected rejection causes, planned steps and retained checker corrections.",
        "The specifically selected Identity, permissions and delegation criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "controls-intervention",
      "relation": "direct",
      "rationale": "The qualification tests a stop at a protected-effect boundary; it separately allows effects committed before withdrawal even if confirmation arrives later.",
      "investigation_question": "Can the intervention reach the relevant action before its effects become irreversible?",
      "evidence_needed": [
        "The frozen timing contract and ordered durable events for withdrawal, authority checks and protected commits.",
        "The matched admission-only and transaction-bound runs, including expected rejection causes, planned steps and retained checker corrections.",
        "The specifically selected Stopping, containment and recovery criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "controls-monitoring",
      "relation": "context",
      "rationale": "Logs, incidents and follow-up asks: What happens after a warning is recorded, and how is the response examined? This supporting arrangement affects the test environment, while the active endpoint remains whether an old permission produces a new protected commit after durable withdrawal.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Logs, incidents and follow-up, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Logs, incidents and follow-up, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "controls-boundaries",
      "relation": "direct",
      "rationale": "The parent-to-child delegation edge and transaction-bound protected action specify where current authority must be checked outside the scripted workers.",
      "investigation_question": "Could the system act beyond the intended scope, and which boundary would prevent or contain it?",
      "evidence_needed": [
        "The frozen timing contract and ordered durable events for withdrawal, authority checks and protected commits.",
        "The matched admission-only and transaction-bound runs, including expected rejection causes, planned steps and retained checker corrections.",
        "The specifically selected Supplier and agent action boundaries criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evaluation-model",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Examine what a model can do using stated tasks, inputs and assessment methods. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evaluation-application",
      "relation": "context",
      "rationale": "Application and mission-specific tests asks: How closely do the test conditions match the setting in which people will rely on the result? A future external implementation needs matched timing and observation conditions; no LangGraph or autonomous-agent evaluation has run.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Application and mission-specific tests, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Application and mission-specific tests, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evaluation-control",
      "relation": "direct",
      "rationale": "The admission-only comparison and transaction-bound comparison directly test whether withdrawn permission can still produce a new protected effect.",
      "investigation_question": "After scripted authorized withdrawal is durably committed, can a valid pending or retried request still create a new protected change under the retired authority?",
      "evidence_needed": [
        "The frozen timing contract and ordered durable events for withdrawal, authority checks and protected commits.",
        "The matched admission-only and transaction-bound runs, including expected rejection causes, planned steps and retained checker corrections.",
        "The specifically selected Tests of intervention and authority criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evaluation-adversarial",
      "relation": "direct",
      "rationale": "The qualification deliberately seeds stale permission, retries and rejection-confound cases to test whether the proposed control and checker detect the intended failure.",
      "investigation_question": "Which failure or attack paths were examined, and what happened at the relevant boundary?",
      "evidence_needed": [
        "The frozen timing contract and ordered durable events for withdrawal, authority checks and protected commits.",
        "The matched admission-only and transaction-bound runs, including expected rejection causes, planned steps and retained checker corrections.",
        "The specifically selected Adversarial tests and failure injection criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://atlas.mitre.org/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evaluation-human-factors",
      "relation": "not_established",
      "rationale": "The topic’s stated focus is: Examine information, workload, expertise, incentives and opportunities to question the system. The declared Revocation in Delegated AI Workflows work addresses whether a protected change committed after authority withdrawal in the shared database ordering; its current public scope identifies no specific implementation, case or assessment criterion linking that subject to this topic.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evaluation-reproducibility",
      "relation": "direct",
      "rationale": "Fixed scenarios, retained source and corrections are necessary to reproduce the deterministic measurement instrument before an external workflow is chosen.",
      "investigation_question": "Can another assessor inspect or repeat the procedure and understand why results differ?",
      "evidence_needed": [
        "The frozen timing contract and ordered durable events for withdrawal, authority checks and protected commits.",
        "The matched admission-only and transaction-bound runs, including expected rejection causes, planned steps and retained checker corrections.",
        "The specifically selected Reproducibility and retained test artifacts criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evaluation-regression",
      "relation": "direct",
      "rationale": "Corrections to checker weaknesses are preserved with regression tests so earlier false acceptances are not silently reintroduced.",
      "investigation_question": "What changed, which claims could it affect, and what was retested?",
      "evidence_needed": [
        "The frozen timing contract and ordered durable events for withdrawal, authority checks and protected commits.",
        "The matched admission-only and transaction-bound runs, including expected rejection causes, planned steps and retained checker corrections.",
        "The specifically selected Rechecking after changes criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evidence-claims",
      "relation": "direct",
      "rationale": "The no-new-post-withdrawal-commit endpoint, common ordering and matched comparisons define the exact claim the current instrument can test.",
      "investigation_question": "Exactly what conclusion is the reader being asked to accept?",
      "evidence_needed": [
        "The frozen timing contract and ordered durable events for withdrawal, authority checks and protected commits.",
        "The matched admission-only and transaction-bound runs, including expected rejection causes, planned steps and retained checker corrections.",
        "The specifically selected Claims, criteria and scope criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evidence-provenance",
      "relation": "context",
      "rationale": "The current observer assumes a trusted local database and needs retained source and event identity; evaluating trustworthiness of evidence across adversarial systems is the deferred second program question.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Sources, provenance and missing records, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Sources, provenance and missing records, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.w3.org/TR/prov-dm/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evidence-reconstruction",
      "relation": "direct",
      "rationale": "The separate read-only observer and offline checker reconstruct committed event order, distinguishing actual effects from later acknowledgments.",
      "investigation_question": "What can the available record establish about the intervention and what followed it?",
      "evidence_needed": [
        "The frozen timing contract and ordered durable events for withdrawal, authority checks and protected commits.",
        "The matched admission-only and transaction-bound runs, including expected rejection causes, planned steps and retained checker corrections.",
        "The specifically selected Reconstructing the decision and intervention criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evidence-uncertainty",
      "relation": "direct",
      "rationale": "Incomplete observation, wrong rejection causes or skipped planned steps prevent a clean qualification result even when no protected effect appears.",
      "investigation_question": "What would weaken this conclusion, and which questions remain unresolved?",
      "evidence_needed": [
        "The frozen timing contract and ordered durable events for withdrawal, authority checks and protected commits.",
        "The matched admission-only and transaction-bound runs, including expected rejection causes, planned steps and retained checker corrections.",
        "The specifically selected Conflicting evidence and unresolved findings criterion and source passage, kept separate from the research scoring or timing contract."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evidence-review",
      "relation": "context",
      "rationale": "Publicly inspectable contracts and correction records can support future replication, but an independent external assessment or evidence-trust study has not been completed.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Review, challenge and communication, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Review, challenge and communication, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "revocation",
      "topic_id": "evidence-correction",
      "relation": "context",
      "rationale": "Reversing effects already committed, or repairing prior harm, remains a separate control requirement. The current revocation endpoint concerns new protected changes after durable authority withdrawal.",
      "investigation_question": "Before using Revocation in Delegated AI Workflows in a setting informed by Correction records and evidence of effects, which source condition, actor and workflow would need to be selected to examine whether a protected change committed after authority withdrawal in the shared database ordering?",
      "evidence_needed": [
        "A scoped excerpt and applicability/context note for Correction records and evidence of effects, including its actor and use restrictions.",
        "An explicit study-extension decision stating the proposed workflow, comparison, required records and what the existing research cannot establish."
      ],
      "limit": "Instrument relevance only. The trusted local database test is model-free; it does not demonstrate autonomous-agent control, novel revocation research, statutory compliance or AGI readiness. Questions 2 and 3 remain deferred.",
      "program_evidence_url": "",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/",
      "program_evidence_access": "Private planning record; public evidence link removed."
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-consumer",
      "relation": "context",
      "rationale": "The explorer topic concerns claims made to customers about system behavior. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining claims made to customers about system behavior, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for U.S. consumer protection, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Coverage depends on the conduct, entity and statutory jurisdiction; an AI label does not decide the legal analysis.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.ftc.gov/legal-library/browse/statutes/federal-trade-commission-act"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-equality",
      "relation": "context",
      "rationale": "The explorer topic concerns accessible challenge to technology-assisted employment decisions. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining accessible challenge to technology-assisted employment decisions, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Employment equality and disability, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Different statutes cover different employers, people and decisions. The listed resources do not determine whether a particular decision was discriminatory.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.eeoc.gov/fact-sheet/federal-laws-prohibiting-job-discrimination-questions-and-answers"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-credit",
      "relation": "context",
      "rationale": "The explorer topic concerns principal reasons for an adverse credit decision. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining principal reasons for an adverse credit decision, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Credit decisions and reasons, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Notice requirements vary with the transaction and applicant. This topic describes selected credit rules, not all financial-services obligations.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.consumerfinance.gov/compliance/compliance-resources/other-applicable-requirements/equal-credit-opportunity-act/"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-medical",
      "relation": "not_established",
      "rationale": "The explorer topic concerns device-function classification, intended use and device evidence. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Whether software is a medical device depends on its function and intended use. The AI lifecycle draft is not a binding rule or a completed approval of any product.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.fda.gov/regulatory-information/search-fda-guidance-documents/policy-device-software-functions-and-mobile-medical-applications"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-california",
      "relation": "context",
      "rationale": "The explorer topic concerns covered personal data, automated decisions and consumer requests. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining covered personal data, automated decisions and consumer requests, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for California privacy and automated decisions, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Coverage, exceptions and compliance schedules differ across provisions. These rules do not apply identically to every business or every use of AI.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.cppa.ca.gov/regulations/"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-california-employment",
      "relation": "context",
      "rationale": "The explorer topic concerns retained employment-decision records and discriminatory effects. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining retained employment-decision records and discriminatory effects, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for California: employment decision systems, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. This entry concerns the 2025 employment regulations, not the separate CCPA automated-decision rules or all subsequently enacted employment AI laws. Covered entities and particular records require a scoped assessment.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://calcivilrights.ca.gov/2025/06/30/civil-rights-council-secures-approval-for-regulations-to-protect-against-employment-discrimination-related-to-artificial-intelligence/"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-california-frontier",
      "relation": "not_established",
      "rationale": "The explorer topic concerns catastrophic-risk frameworks, mitigations and reported concerns. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Frontier models, large frontier developers, catastrophic risks and covered employees are defined categories. Publishing a framework does not establish that a model is safe for every application.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://oag.ca.gov/sb53"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-california-companions",
      "relation": "context",
      "rationale": "The explorer topic concerns companion disclosure, crisis protocols and protections for minors. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining companion disclosure, crisis protocols and protections for minors, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for California: companion-chatbot safeguards, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. The definition and qualified business-use, game and voice-assistant exclusions determine coverage. Current three-hour reminders concern known minors during continuing interactions. These provisions do not create a universal human-review or override right. SB1119 changes the known-minor provisions and adds requirements with separate operative dates; the current and forthcoming regimes must be read separately.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260SB243"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-colorado",
      "relation": "context",
      "rationale": "The explorer topic concerns data correction and reconsideration of consequential decisions. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining data correction and reconsideration of consequential decisions, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Colorado: consequential decisions, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Definitions, exemptions, implementing rules and the timing of individual duties matter. The 2024 law alone is not a current account of this framework.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://leg.colorado.gov/bills/sb26-189"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-colorado-health-review",
      "relation": "context",
      "rationale": "The explorer topic concerns qualified review before a medical-necessity denial is issued. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining qualified review before a medical-necessity denial is issued, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Colorado: AI-assisted health-care review, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. This entry covers selected utilization-review provisions in the enacted text, not the broader introduced bill. Relevant entity definitions and coverage terms matter. The research question is an editorial connection to practical human control, not a claim that TAE, HIT or CEC establishes compliance.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1139"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-colorado-psychotherapy",
      "relation": "context",
      "rationale": "The explorer topic concerns real-time professional participation and withdrawal of recording consent. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining real-time professional participation and withdrawal of recording consent, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Colorado: AI use in psychotherapy, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. The recording and transcription consent rule is specific to those uses. Educational, research, wellness and certain FDA-authorized uses have defined conditions or exceptions. The enacted text also restricts misleading claims about professional equivalence and therapist-like confidentiality.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1195"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-colorado-conversational-ai",
      "relation": "context",
      "rationale": "The explorer topic concerns interaction-level disclosures, crisis escalation and protections for minors. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining interaction-level disclosures, crisis escalation and protections for minors, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Colorado: conversational AI safeguards, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Coverage depends on statutory definitions and exclusions, including specified enterprise, research, transactional, health-care and educational uses. The age-estimation wording precedes the January 2027 clause; the later date should not be applied to every duty. Proposed implementing rules require a separate status check.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1263"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-connecticut-employment",
      "relation": "context",
      "rationale": "The explorer topic concerns employment notices, the system’s role and responses to bias-test findings. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining employment notices, the system’s role and responses to bias-test findings, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Connecticut: automated employment decisions, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Employment decisions, developers, deployers and substantial influence are defined terms with exclusions. These sections do not create a general right to override every automated decision. The act’s effective date must be distinguished from the later start of specified duties.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.cga.ct.gov/2026/ACT/PA/PDF/2026PA-00015-R00SB-00005-PA.PDF"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-illinois-employment",
      "relation": "context",
      "rationale": "The explorer topic concerns AI-related discrimination, protected-class proxies and employment notice. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining AI-related discrimination, protected-class proxies and employment notice, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Illinois: AI in employment decisions, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Coverage follows the Human Rights Act and specified employment activities. Notice implementation is subject to agency rulemaking. This statute does not create a universal human-review or override requirement.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://ilga.gov/legislation/PublicActs/View/103-0804"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-illinois-psychological",
      "relation": "context",
      "rationale": "The explorer topic concerns professional responsibility and approval for permitted AI support. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining professional responsibility and approval for permitted AI support, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Illinois: AI support in psychological services, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. The act defines covered services and professionals. Additional restrictions concern emotion or mental-state detection and consent for recording or transcription used in supplementary support; this is not a blanket rule for all health software.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://ilga.gov/Legislation/PublicActs/View/104-0054"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-illinois-video",
      "relation": "context",
      "rationale": "The explorer topic concerns video-interview consent, sharing, deletion and demographic reporting. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining video-interview consent, sharing, deletion and demographic reporting, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Illinois: AI video interviews, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. The act concerns AI analysis of applicant-submitted videos for Illinois-based positions. Sole reliance on AI for in-person interview selection triggers reporting; the act does not categorically prohibit that reliance.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://my.ilga.gov/Legislation/ILCS/Articles?ActID=4015&Chapter=EMPLOYMENT&ChapterID=68&MajorTopic=BUSINESS+AND+EMPLOYMENT"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-illinois-biometric",
      "relation": "not_established",
      "rationale": "The explorer topic concerns biometric collection, consent, disclosure and destruction. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Statutory definitions and exclusions determine coverage; not all images, identity data or AI uses are covered biometrics. This is a biometric-privacy law, not a general AI-governance act.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.ilga.gov/legislation/ilcs/fulltext?DocName=074000140K15"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-illinois-frontier",
      "relation": "not_established",
      "rationale": "The explorer topic concerns independent audit access to a frontier developer’s framework evidence. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Model and developer thresholds limit coverage. The act’s general effective date differs from the start of framework and audit duties; it should not be presented as an audit obligation already in force.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.ilga.gov/documents/legislation/PublicActs/104/104-0538.htm"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-minnesota-profiling",
      "relation": "context",
      "rationale": "The explorer topic concerns data correction, reevaluation and the effect on a profiling outcome. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining data correction, reevaluation and the effect on a profiling outcome, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Minnesota: profiling and reevaluation, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. The act’s coverage thresholds, exclusions and consumer definition apply. These rights do not apply identically to every employment or service decision merely because profiling is involved.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.ag.state.mn.us/Data-Privacy/Consumer/"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-new-york-government",
      "relation": "not_established",
      "rationale": "The explorer topic concerns accuracy of a state-agency AI inventory and its disclosures. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. This entry concerns state agencies, not a general private-sector mandate. The 2025 amendment replaced the earlier impact-assessment and meaningful-human-review provisions; those removed provisions should not be treated as current duties.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/STT/103-E"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-new-york-raise",
      "relation": "context",
      "rationale": "The explorer topic concerns frontier safeguards, deployment decisions and critical-incident reporting. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining frontier safeguards, deployment decisions and critical-incident reporting, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for New York: frontier-model transparency, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Coverage depends on the statutory model and developer definitions and the New York connection. Academic-research and other specified exceptions apply. Publication alone does not establish effective control.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.nysenate.gov/legislation/bills/2025/S8828"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-new-york-companions",
      "relation": "context",
      "rationale": "The explorer topic concerns nonhuman disclosure, crisis referrals and separately scoped minor safeguards. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining nonhuman disclosure, crisis referrals and separately scoped minor safeguards, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for New York: AI companion safeguards, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Coverage concerns defined companions for personal use in New York, with exclusions for specified customer-service, research, technical-assistance and internal-business systems. Article 47 does not require a staffed human handoff or guarantee detection. Separate Safe by Design provisions (§1540(7)) require age assurance before covered users can access integrated companions on covered platforms, and disable access by default for covered minors, subject to parental override, from 1 January 2027. S9051B was signed on 28 October 2026 as chapter 368, adding separate safeguards for minors. Its published text preserves Article 47. The start date of the new safeguards remains under review because the legislative text and official signing announcement differ.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/GBS/1700"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-texas",
      "relation": "context",
      "rationale": "The explorer topic concerns actor-specific disclosures, prohibited uses and statutory sandbox conditions. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining actor-specific disclosures, prohibited uses and statutory sandbox conditions, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Texas: AI uses and disclosures, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Requirements depend on the actor and use. The discrimination prohibition has an intent requirement; disparate impact alone does not establish that intent. A research sandbox is not automatically a participant in the statutory program.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://capitol.texas.gov/billlookup/BillSummary.aspx?Bill=HB149&LegSess=89R"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-utah-chatbots",
      "relation": "context",
      "rationale": "The explorer topic concerns mental-health-chatbot disclosure points and information practices. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining mental-health-chatbot disclosure points and information practices, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Utah: mental-health chatbots, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. This entry covers the mental-health-chatbot provisions, not every Utah AI law. The defined chatbot, supplier and Utah-user scope matters. A disclosure does not establish clinical effectiveness or confer professional licensure.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://le.utah.gov/xcode/Title13/Chapter72A/C13-72a-P2_2025050720250507.pdf"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-virginia-profiling",
      "relation": "context",
      "rationale": "The explorer topic concerns profiling opt-outs and appeals of refused privacy requests. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining profiling opt-outs and appeals of refused privacy requests, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Virginia: profiling and privacy requests, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. An appeal of a refused privacy request is not a universal appeal of the underlying automated decision. Coverage thresholds, entity and data exclusions, and the consumer definition must be examined.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://law.lis.virginia.gov/vacode/title59.1/chapter53/section59.1-577/"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-wisconsin-political",
      "relation": "not_established",
      "rationale": "The explorer topic concerns synthetic-media disclosures in specified political communications. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. This is a targeted political-communications law, not a comprehensive enterprise AI framework. The medium, content and statutory definitions determine the disclosure required.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://content.govdelivery.com/accounts/WIGOV/bulletins/391af46"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-wisconsin-insurance",
      "relation": "context",
      "rationale": "The explorer topic concerns insurer AI-program evidence, testing and vendor oversight. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining insurer AI-program evidence, testing and vendor oversight, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Wisconsin: insurance AI governance guidance, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. The bulletin explains regulatory expectations under existing insurance laws and permits alternative ways to demonstrate compliance. It is guidance, not a new AI statute or a requirement for one prescribed documentation format.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://oci.wi.gov/Pages/Regulation/Bulletin20250318AI.aspx"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-us-new-york-city-aedt",
      "relation": "not_established",
      "rationale": "The explorer topic concerns employment-tool bias-audit scope, independence and notice. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. This is a New York City requirement for defined hiring and promotion tools, not a statewide rule or a general certification that an AI system is fair. The city rules and definitions determine coverage.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.nyc.gov/site/dca/about/automated-employment-decision-tools.page"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-eu-prohibited",
      "relation": "context",
      "rationale": "The explorer topic concerns classification of a proposed use against specified prohibited practices. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining classification of a proposed use against specified prohibited practices, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Prohibited AI practices, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Consult the current article and relevant exceptions. A general risk score or a successful test cannot authorize a prohibited use.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-5"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-eu-high-risk",
      "relation": "context",
      "rationale": "The explorer topic concerns use classification and high-risk documentation and control requirements. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining use classification and high-risk documentation and control requirements, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for High-risk systems and requirements, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Not every consequential use of AI is automatically classified as high-risk. Article 6, the annexes, exceptions and applicable transition provisions require review.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-6"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-eu-human-oversight",
      "relation": "context",
      "rationale": "The explorer topic concerns usable reviewer authority and evidence of what intervention changed. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining usable reviewer authority and evidence of what intervention changed, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Human oversight, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. This is a scoped legal provision, not a universal requirement to put a person behind every AI output. Node & Norm’s research questions do not establish legal conformity.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02024R1689-20260727"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-eu-transparency",
      "relation": "context",
      "rationale": "The explorer topic concerns whether information about AI interaction or generated content reaches its audience. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining whether information about AI interaction or generated content reaches its audience, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Transparency and generated content, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Not every AI use or piece of assisted content has the same disclosure duty. The type of interaction, content, actor and exception matters.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-50"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-eu-gpai",
      "relation": "not_established",
      "rationale": "The explorer topic concerns provider documentation and downstream model-capability and risk information. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. General-purpose AI is a defined regulatory category; it does not mean artificial general intelligence. Provider roles, exemptions and systemic-risk classification require separate examination.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-53"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-eu-value-chain",
      "relation": "context",
      "rationale": "The explorer topic concerns responsibility for a version, intended use and changed supplier role. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining responsibility for a version, intended use and changed supplier role, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Responsibilities across the value chain, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. A supplier contract or an internal job title does not by itself settle the statutory role. Article 25 addresses specified value-chain circumstances.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-25"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-eu-gdpr",
      "relation": "context",
      "rationale": "The explorer topic concerns personal-data correction, information and conditional automated-decision rights. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining personal-data correction, information and conditional automated-decision rights, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Personal data and automated decisions, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Article 22 has defined conditions, exceptions and safeguards; it is not a general prohibition on all automated decisions. Other data-protection duties can apply even when Article 22 does not.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-eu-nis2",
      "relation": "not_established",
      "rationale": "The explorer topic concerns covered organizations’ cybersecurity incident response and supply-chain security. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Coverage depends on sector, entity characteristics and national implementation. NIS2 is not an AI-specific assurance standard.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/nis2-directive"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-eu-cra",
      "relation": "not_established",
      "rationale": "The explorer topic concerns digital-product security, vulnerability handling and support-period evidence. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Product scope, exclusions, actor responsibilities and transition provisions matter. Inclusion here does not mean every AI service falls within the Act.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-kr-ai-basic",
      "relation": "context",
      "rationale": "The explorer topic concerns Korean use categories, transparency, safety and oversight arrangements. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining Korean use categories, transparency, safety and oversight arrangements, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Republic of Korea: AI Basic Act, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the current Korean instruments and implementing guidance for an applicability decision. Terms such as high-impact should not be assumed equivalent to EU high-risk classifications.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.msit.go.kr/eng/bbs/view.do?bbsSeqNo=42&mId=4&mPid=2&nttSeqNo=1214&sCode=eng"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-cn-generative",
      "relation": "context",
      "rationale": "The explorer topic concerns public-facing Chinese generative services, data practices and complaint handling. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining public-facing Chinese generative services, data practices and complaint handling, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for China: generative AI services, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. The measures distinguish public-facing services from research and uses not offered to the domestic public. Other applicable Chinese laws and later measures require separate review.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.cac.gov.cn/2023-07/13/c_1690898327029107.htm"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-jp-ai-promotion",
      "relation": "not_established",
      "rationale": "The explorer topic concerns Japan’s governmental and stakeholder promotion-and-governance responsibilities. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. The law’s promotion-and-governance approach should not be presented as the same risk-classification regime used elsewhere. Existing laws and sector guidance remain relevant.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www8.cao.go.jp/cstp/ai/ai_act/ai_act.html"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-in-dpdp",
      "relation": "not_established",
      "rationale": "The explorer topic concerns covered digital-personal-data processing, organizational duties and individual rights. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. The law and rules have scope conditions, exemptions and phased provisions. Their existence does not establish that every duty applies to every AI activity.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.pib.gov.in/PressReleseDetailm.aspx?PRID=2190655&lang=2&reg=48"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-br-lgpd",
      "relation": "context",
      "rationale": "The explorer topic concerns information and contestability for covered automated personal-data decisions. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining information and contestability for covered automated personal-data decisions, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Brazil: data protection and review, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. The right to request review should not be relabeled as a universal guarantee of human review. Scope, exceptions and regulator guidance require examination.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.gov.br/anpd/pt-br/assuntos/titular-de-dados/direito-dos-titulares"
    },
    {
      "program_id": "repair",
      "topic_id": "reg-institutional-commitments",
      "relation": "direct",
      "rationale": "Stated institutional purposes and supplier commitments can supply the particular obligation against which an accountable explanation or repair is examined.",
      "investigation_question": "In an institution examining purchasing commitments, supplier responsibilities and evidence of fulfillment, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Procurement, contracts and stated purposes, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. This topic concerns commitments to examine, rather than a single law. The terms of a particular agreement, applicable law and responsible parties determine its effect. A supplier assurance does not by itself establish that a control worked.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "iso-42001",
      "relation": "context",
      "rationale": "The explorer topic concerns organizational AI responsibilities, operation and management-system improvement. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining organizational AI responsibilities, operation and management-system improvement, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI management systems · ISO/IEC 42001:2023, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.iso.org/standard/42001"
    },
    {
      "program_id": "repair",
      "topic_id": "iso-23894",
      "relation": "context",
      "rationale": "The explorer topic concerns identification, ownership and treatment of context-specific AI risks. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining identification, ownership and treatment of context-specific AI risks, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI risk management · ISO/IEC 23894:2023, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.iso.org/standard/77304.html"
    },
    {
      "program_id": "repair",
      "topic_id": "iso-42005",
      "relation": "context",
      "rationale": "The explorer topic concerns documented impacts on affected people across a system lifecycle. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining documented impacts on affected people across a system lifecycle, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI impact assessment · ISO/IEC 42005:2025, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.iso.org/standard/42005"
    },
    {
      "program_id": "repair",
      "topic_id": "iso-22989",
      "relation": "context",
      "rationale": "The explorer topic concerns shared terminology for the system, actors and activities. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining shared terminology for the system, actors and activities, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Shared AI terminology · ISO/IEC 22989:2022, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.iso.org/standard/74296.html"
    },
    {
      "program_id": "repair",
      "topic_id": "nist-ai-rmf-1-0",
      "relation": "context",
      "rationale": "The explorer topic concerns connections between identified risks, evaluation findings and management decisions. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining connections between identified risks, evaluation findings and management decisions, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI Risk Management Framework · NIST AI RMF 1.0, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "repair",
      "topic_id": "oecd-ai-principles",
      "relation": "context",
      "rationale": "The explorer topic concerns human rights, transparency and an accountable response to AI use. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining human rights, transparency and an accountable response to AI use, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Trustworthy AI principles · OECD, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://oecd.ai/en/ai-principles"
    },
    {
      "program_id": "repair",
      "topic_id": "unesco-ai-ethics",
      "relation": "context",
      "rationale": "The explorer topic concerns dignity, inclusion, human oversight and responsibility for harm. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining dignity, inclusion, human oversight and responsibility for harm, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Ethics of AI · UNESCO Recommendation, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.unesco.org/en/artificial-intelligence/recommendation-ethics"
    },
    {
      "program_id": "repair",
      "topic_id": "owasp-llm-top-10-2025",
      "relation": "not_established",
      "rationale": "The explorer topic concerns prompt injection, information disclosure and excessive agency in LLM applications. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "repair",
      "topic_id": "mitre-atlas",
      "relation": "not_established",
      "rationale": "The explorer topic concerns documented adversary techniques and evidence for defenses. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "repair",
      "topic_id": "nist-digital-identity-4",
      "relation": "not_established",
      "rationale": "The explorer topic concerns user identity proofing, authentication and federation in the guideline’s scope. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "repair",
      "topic_id": "nist-generative-ai-profile",
      "relation": "context",
      "rationale": "The explorer topic concerns deployment-specific generative-AI risks and management actions. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining deployment-specific generative-AI risks and management actions, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Generative AI risk profile · NIST AI 600-1, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence"
    },
    {
      "program_id": "repair",
      "topic_id": "iso-27001",
      "relation": "not_established",
      "rationale": "The explorer topic concerns confidentiality, integrity and availability of information and retained records. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.iso.org/standard/27001"
    },
    {
      "program_id": "repair",
      "topic_id": "roles-leadership",
      "relation": "direct",
      "rationale": "The public companion makes responsibility follow knowledge, choices and authority, including leaders able to change the process behind a harmful decision.",
      "investigation_question": "In an institution examining leadership ownership, risk acceptance and escalation beyond a system owner, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Leadership and accountable ownership, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Organizational responsibility must be examined in context; naming an owner is not evidence of effective oversight.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "roles-delivery",
      "relation": "direct",
      "rationale": "The public companion asks where copies, instructions and responsibilities travel; divided supplier and institutional powers can leave repair incomplete.",
      "investigation_question": "In an institution examining responsibilities and change authority across developers, suppliers and deployers, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Developers, suppliers and deployers, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. These are descriptive delivery roles. Any legal meaning or duty must be checked against the applicable instrument.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "roles-domain-users",
      "relation": "direct",
      "rationale": "The companion’s prudential-deficit question concerns whether a reviewer could see relevant information, deliberate and act within the workflow.",
      "investigation_question": "In an institution examining the information, expertise, time and discretion available to frontline specialists, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Domain specialists and frontline users, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. A credential or job title alone does not establish task competence, available time or freedom to disagree.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "repair",
      "topic_id": "roles-reviewers",
      "relation": "direct",
      "rationale": "An inquiry must be open to evidence that challenges the institution’s account and reach a reviewer with a remit to investigate it.",
      "investigation_question": "In an institution examining reviewer remit, access, competence and independence, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Reviewers and independent assessors, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Independence, access and competence are separate matters; none follows automatically from an assessment label.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "roles-affected-people",
      "relation": "direct",
      "rationale": "The companion follows the person affected through challenge and response, including burdens that remain after an appeal succeeds.",
      "investigation_question": "In an institution examining routes by which affected people can challenge an account and obtain a response, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Affected people and routes to challenge, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. A feedback channel is not necessarily an appeal process or an effective remedy. Rights and duties vary by context.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "roles-intervention",
      "relation": "direct",
      "rationale": "Authority to reverse an original decision can differ from authority to reimburse a loss or correct copies; the companion examines that division directly.",
      "investigation_question": "In an institution examining powers to pause, override, investigate, hear an appeal and authorize repair, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Authority to intervene and repair, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Formal authority, usable access and an effect on the action are separate questions. A research link does not establish legal compliance.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "controls-inventory",
      "relation": "context",
      "rationale": "The explorer topic concerns identification of the version, intended use, owner and changes under examination. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining identification of the version, intended use, owner and changes under examination, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Inventories and change records, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. An inventory describes the stated estate; its completeness and accuracy still need examination.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "controls-data",
      "relation": "direct",
      "rationale": "The companion’s repair examples require tracing and correcting records held by several systems, while keeping evidentiary gaps visible.",
      "investigation_question": "In an institution examining authorized access, retention and examination of decision records, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Data handling and retained records, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Retention and access depend on context and applicable duties. More data is not automatically better evidence.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "repair",
      "topic_id": "controls-access",
      "relation": "context",
      "rationale": "The explorer topic concerns the identity and delegated permission behind an action and its withdrawal. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining the identity and delegated permission behind an action and its withdrawal, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Identity, permissions and delegation, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. NIST digital identity guidance has a stated user and government-system scope; it is not a complete specification for agent identity or delegation. The related revocation study’s initial qualification uses scripted workers and a local database; autonomous-agent effectiveness remains unestablished.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "repair",
      "topic_id": "controls-intervention",
      "relation": "direct",
      "rationale": "Its cancellation example distinguishes acknowledging an instruction from preventing a queued notice, and separates recoverable action from irreversible harm.",
      "investigation_question": "In an institution examining stopping, containment, recovery and irreversible effects, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Stopping, containment and recovery, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Some actions cannot be reversed. A stop control, a recovery process and correction of harm require different evidence.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "controls-monitoring",
      "relation": "direct",
      "rationale": "The inquiry asks whether earlier complaints reached someone able to change the disputed practice and whether the response was followed through.",
      "investigation_question": "In an institution examining the chain from a warning or complaint to assigned action and follow-up, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Logs, incidents and follow-up, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. A recorded warning is not evidence that anyone understood it or that a corrective action worked.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "controls-boundaries",
      "relation": "context",
      "rationale": "The explorer topic concerns permitted tool actions and dependencies outside the application. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining permitted tool actions and dependencies outside the application, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Supplier and agent action boundaries, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. A documented boundary does not establish enforcement. Test the relevant configuration and retain limits on external visibility.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "repair",
      "topic_id": "evaluation-model",
      "relation": "not_established",
      "rationale": "The explorer topic concerns model tasks, scores, failures and limits of a capability result. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. A model benchmark does not by itself establish the performance or safety of an application using that model.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "evaluation-application",
      "relation": "context",
      "rationale": "The explorer topic concerns testing in the application’s intended task and operating conditions. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining testing in the application’s intended task and operating conditions, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Application and mission-specific tests, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Performance under a stated test condition does not establish performance in every population, environment or later version.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "evaluation-control",
      "relation": "context",
      "rationale": "The explorer topic concerns whether a requested intervention changed the governed action. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining whether a requested intervention changed the governed action, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Tests of intervention and authority, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. A scripted control demonstration, a documentary reconstruction and an observed human intervention support different conclusions. The related revocation study’s initial qualification uses scripted workers and a local database; autonomous-agent effectiveness remains unestablished.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "evaluation-adversarial",
      "relation": "not_established",
      "rationale": "The explorer topic concerns controlled attack or failure paths and responses at a tested boundary. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Passing selected scenarios does not establish complete security. Testing authority and limits must be agreed for the setting.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "repair",
      "topic_id": "evaluation-human-factors",
      "relation": "direct",
      "rationale": "The companion examines conditions for deliberation, such as concealed evidence or withheld authority, while declining to infer understanding from an outcome.",
      "investigation_question": "In an institution examining workload, information, incentives and opportunities for human challenge, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Human judgment and working conditions, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Records can describe conditions; measuring behavior requires an appropriate study. Subjective workload does not establish effective oversight.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "repair",
      "topic_id": "evaluation-reproducibility",
      "relation": "not_established",
      "rationale": "The explorer topic concerns retained inputs, versions, scoring rules, procedures and results. The public companion examines judgment, accountable explanation and repair after institutional harm. Its current public argument supplies no specific study of this technical or jurisdictional subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Repeatability does not establish that the chosen measure answers the intended question or generalizes to field use.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "evaluation-regression",
      "relation": "context",
      "rationale": "The explorer topic concerns which findings require rechecking after a configuration or operating change. This can frame a case about who can question a harmful decision and who owes a response. The companion supplies an ethical inquiry into accountability and repair; it has not tested this instrument or established the institution’s legal duties.",
      "investigation_question": "In an institution examining which findings require rechecking after a configuration or operating change, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Rechecking after changes, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. A previous result belongs to its tested configuration and conditions; it should not silently transfer to an updated system.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "repair",
      "topic_id": "evidence-claims",
      "relation": "direct",
      "rationale": "The companion asks what an institution may honestly claim to have acknowledged, repaired and reformed before closing a case.",
      "investigation_question": "In an institution examining the conclusion, assessment criteria and scope offered to a reader, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Claims, criteria and scope, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. A criterion may come from law, a standard, a contract or a research method. Identify its source rather than treating them as interchangeable.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "repair",
      "topic_id": "evidence-provenance",
      "relation": "direct",
      "rationale": "A retained notice may contradict an internal account; the companion needs source origin and missing records to remain inspectable.",
      "investigation_question": "In an institution examining record origin, transformation, gaps and uncertain attribution, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Sources, provenance and missing records, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. A traceable record can still be incomplete or wrong. Provenance supports examination without establishing truth on its own.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.w3.org/TR/prov-dm/"
    },
    {
      "program_id": "repair",
      "topic_id": "evidence-reconstruction",
      "relation": "direct",
      "rationale": "Its central account reconstructs the initial decision, authority, appeal and subsequent consequences before attributing responsibility.",
      "investigation_question": "In an institution examining the chronology of a decision, intervention and subsequent events, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Reconstructing the decision and intervention, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. A missing record is not automatically evidence of failure; an event occurring later does not by itself establish causation.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "repair",
      "topic_id": "evidence-uncertainty",
      "relation": "direct",
      "rationale": "The companion retains disputed losses, causal uncertainty and irreversible consequences rather than treating a corrected balance as complete repair.",
      "investigation_question": "In an institution examining conflicting evidence, alternative explanations and unresolved findings, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Conflicting evidence and unresolved findings, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Unresolved means the available evidence does not settle the question. It should not silently become either approval or a finding of failure.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "repair",
      "topic_id": "evidence-review",
      "relation": "direct",
      "rationale": "Its account must be specific enough for the affected person to challenge and for new evidence to change the explanation or remedy.",
      "investigation_question": "In an institution examining a reader’s ability to trace and challenge the reasoning and sources, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Review, challenge and communication, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. Public availability does not establish independent validation. Access restrictions and the assessor’s remit should remain clear.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "repair",
      "topic_id": "evidence-correction",
      "relation": "direct",
      "rationale": "The public companion explicitly distinguishes approval of a payment or cancellation from delivery of the remedy and correction of downstream copies.",
      "investigation_question": "In an institution examining the authorized correction and evidence of whether it reached its intended recipient, what can the record establish about the person’s opportunity to challenge the decision, the owner of the response and the repair still owed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Correction records and evidence of effects, with its actor, intended use and stated limits.",
        "The original decision, affected person’s challenge and an account of the resulting consequences.",
        "The responsible parties’ authority, response and evidence distinguishing an approved remedy from delivery and downstream correction."
      ],
      "limit": "Editorial relevance to the public companion only. It does not establish legal applicability, sincere repentance, causal responsibility in a real case or effective institutional repair; the chapter remains private and forthcoming. An assurance finding does not itself authorize a correction. Responsibility stays with the people or institutions empowered to act.",
      "program_evidence_url": "https://nodeandnorm.org/research/institutional-responsibility-repair/#repair-and-reform",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-consumer",
      "relation": "not_established",
      "rationale": "The explorer topic concerns claims made to customers about system behavior. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Coverage depends on the conduct, entity and statutory jurisdiction; an AI label does not decide the legal analysis.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.ftc.gov/legal-library/browse/statutes/federal-trade-commission-act"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-equality",
      "relation": "not_established",
      "rationale": "The explorer topic concerns accessible challenge to technology-assisted employment decisions. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Different statutes cover different employers, people and decisions. The listed resources do not determine whether a particular decision was discriminatory.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.eeoc.gov/fact-sheet/federal-laws-prohibiting-job-discrimination-questions-and-answers"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-credit",
      "relation": "not_established",
      "rationale": "The explorer topic concerns principal reasons for an adverse credit decision. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Notice requirements vary with the transaction and applicant. This topic describes selected credit rules, not all financial-services obligations.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.consumerfinance.gov/compliance/compliance-resources/other-applicable-requirements/equal-credit-opportunity-act/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-medical",
      "relation": "not_established",
      "rationale": "The explorer topic concerns device-function classification, intended use and device evidence. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Whether software is a medical device depends on its function and intended use. The AI lifecycle draft is not a binding rule or a completed approval of any product.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.fda.gov/regulatory-information/search-fda-guidance-documents/policy-device-software-functions-and-mobile-medical-applications"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-california",
      "relation": "not_established",
      "rationale": "The explorer topic concerns covered personal data, automated decisions and consumer requests. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Coverage, exceptions and compliance schedules differ across provisions. These rules do not apply identically to every business or every use of AI.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.cppa.ca.gov/regulations/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-california-employment",
      "relation": "not_established",
      "rationale": "The explorer topic concerns retained employment-decision records and discriminatory effects. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. This entry concerns the 2025 employment regulations, not the separate CCPA automated-decision rules or all subsequently enacted employment AI laws. Covered entities and particular records require a scoped assessment.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://calcivilrights.ca.gov/2025/06/30/civil-rights-council-secures-approval-for-regulations-to-protect-against-employment-discrimination-related-to-artificial-intelligence/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-california-frontier",
      "relation": "not_established",
      "rationale": "The explorer topic concerns catastrophic-risk frameworks, mitigations and reported concerns. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Frontier models, large frontier developers, catastrophic risks and covered employees are defined categories. Publishing a framework does not establish that a model is safe for every application.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://oag.ca.gov/sb53"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-california-companions",
      "relation": "not_established",
      "rationale": "The explorer topic concerns companion disclosure, crisis protocols and protections for minors. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. The definition and qualified business-use, game and voice-assistant exclusions determine coverage. Current three-hour reminders concern known minors during continuing interactions. These provisions do not create a universal human-review or override right. SB1119 changes the known-minor provisions and adds requirements with separate operative dates; the current and forthcoming regimes must be read separately.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260SB243"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-colorado",
      "relation": "not_established",
      "rationale": "The explorer topic concerns data correction and reconsideration of consequential decisions. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Definitions, exemptions, implementing rules and the timing of individual duties matter. The 2024 law alone is not a current account of this framework.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://leg.colorado.gov/bills/sb26-189"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-colorado-health-review",
      "relation": "not_established",
      "rationale": "The explorer topic concerns qualified review before a medical-necessity denial is issued. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. This entry covers selected utilization-review provisions in the enacted text, not the broader introduced bill. Relevant entity definitions and coverage terms matter. The research question is an editorial connection to practical human control, not a claim that TAE, HIT or CEC establishes compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1139"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-colorado-psychotherapy",
      "relation": "not_established",
      "rationale": "The explorer topic concerns real-time professional participation and withdrawal of recording consent. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. The recording and transcription consent rule is specific to those uses. Educational, research, wellness and certain FDA-authorized uses have defined conditions or exceptions. The enacted text also restricts misleading claims about professional equivalence and therapist-like confidentiality.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1195"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-colorado-conversational-ai",
      "relation": "not_established",
      "rationale": "The explorer topic concerns interaction-level disclosures, crisis escalation and protections for minors. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Coverage depends on statutory definitions and exclusions, including specified enterprise, research, transactional, health-care and educational uses. The age-estimation wording precedes the January 2027 clause; the later date should not be applied to every duty. Proposed implementing rules require a separate status check.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1263"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-connecticut-employment",
      "relation": "not_established",
      "rationale": "The explorer topic concerns employment notices, the system’s role and responses to bias-test findings. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Employment decisions, developers, deployers and substantial influence are defined terms with exclusions. These sections do not create a general right to override every automated decision. The act’s effective date must be distinguished from the later start of specified duties.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.cga.ct.gov/2026/ACT/PA/PDF/2026PA-00015-R00SB-00005-PA.PDF"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-illinois-employment",
      "relation": "not_established",
      "rationale": "The explorer topic concerns AI-related discrimination, protected-class proxies and employment notice. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Coverage follows the Human Rights Act and specified employment activities. Notice implementation is subject to agency rulemaking. This statute does not create a universal human-review or override requirement.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://ilga.gov/legislation/PublicActs/View/103-0804"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-illinois-psychological",
      "relation": "not_established",
      "rationale": "The explorer topic concerns professional responsibility and approval for permitted AI support. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. The act defines covered services and professionals. Additional restrictions concern emotion or mental-state detection and consent for recording or transcription used in supplementary support; this is not a blanket rule for all health software.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://ilga.gov/Legislation/PublicActs/View/104-0054"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-illinois-video",
      "relation": "not_established",
      "rationale": "The explorer topic concerns video-interview consent, sharing, deletion and demographic reporting. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. The act concerns AI analysis of applicant-submitted videos for Illinois-based positions. Sole reliance on AI for in-person interview selection triggers reporting; the act does not categorically prohibit that reliance.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://my.ilga.gov/Legislation/ILCS/Articles?ActID=4015&Chapter=EMPLOYMENT&ChapterID=68&MajorTopic=BUSINESS+AND+EMPLOYMENT"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-illinois-biometric",
      "relation": "not_established",
      "rationale": "The explorer topic concerns biometric collection, consent, disclosure and destruction. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Statutory definitions and exclusions determine coverage; not all images, identity data or AI uses are covered biometrics. This is a biometric-privacy law, not a general AI-governance act.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.ilga.gov/legislation/ilcs/fulltext?DocName=074000140K15"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-illinois-frontier",
      "relation": "not_established",
      "rationale": "The explorer topic concerns independent audit access to a frontier developer’s framework evidence. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Model and developer thresholds limit coverage. The act’s general effective date differs from the start of framework and audit duties; it should not be presented as an audit obligation already in force.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.ilga.gov/documents/legislation/PublicActs/104/104-0538.htm"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-minnesota-profiling",
      "relation": "not_established",
      "rationale": "The explorer topic concerns data correction, reevaluation and the effect on a profiling outcome. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. The act’s coverage thresholds, exclusions and consumer definition apply. These rights do not apply identically to every employment or service decision merely because profiling is involved.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.ag.state.mn.us/Data-Privacy/Consumer/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-new-york-government",
      "relation": "not_established",
      "rationale": "The explorer topic concerns accuracy of a state-agency AI inventory and its disclosures. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. This entry concerns state agencies, not a general private-sector mandate. The 2025 amendment replaced the earlier impact-assessment and meaningful-human-review provisions; those removed provisions should not be treated as current duties.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/STT/103-E"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-new-york-raise",
      "relation": "not_established",
      "rationale": "The explorer topic concerns frontier safeguards, deployment decisions and critical-incident reporting. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Coverage depends on the statutory model and developer definitions and the New York connection. Academic-research and other specified exceptions apply. Publication alone does not establish effective control.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/bills/2025/S8828"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-new-york-companions",
      "relation": "not_established",
      "rationale": "The explorer topic concerns nonhuman disclosure, crisis referrals and separately scoped minor safeguards. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Coverage concerns defined companions for personal use in New York, with exclusions for specified customer-service, research, technical-assistance and internal-business systems. Article 47 does not require a staffed human handoff or guarantee detection. Separate Safe by Design provisions (§1540(7)) require age assurance before covered users can access integrated companions on covered platforms, and disable access by default for covered minors, subject to parental override, from 1 January 2027. S9051B was signed on 28 October 2026 as chapter 368, adding separate safeguards for minors. Its published text preserves Article 47. The start date of the new safeguards remains under review because the legislative text and official signing announcement differ.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/GBS/1700"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-texas",
      "relation": "not_established",
      "rationale": "The explorer topic concerns actor-specific disclosures, prohibited uses and statutory sandbox conditions. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Requirements depend on the actor and use. The discrimination prohibition has an intent requirement; disparate impact alone does not establish that intent. A research sandbox is not automatically a participant in the statutory program.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://capitol.texas.gov/billlookup/BillSummary.aspx?Bill=HB149&LegSess=89R"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-utah-chatbots",
      "relation": "not_established",
      "rationale": "The explorer topic concerns mental-health-chatbot disclosure points and information practices. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. This entry covers the mental-health-chatbot provisions, not every Utah AI law. The defined chatbot, supplier and Utah-user scope matters. A disclosure does not establish clinical effectiveness or confer professional licensure.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://le.utah.gov/xcode/Title13/Chapter72A/C13-72a-P2_2025050720250507.pdf"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-virginia-profiling",
      "relation": "not_established",
      "rationale": "The explorer topic concerns profiling opt-outs and appeals of refused privacy requests. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. An appeal of a refused privacy request is not a universal appeal of the underlying automated decision. Coverage thresholds, entity and data exclusions, and the consumer definition must be examined.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://law.lis.virginia.gov/vacode/title59.1/chapter53/section59.1-577/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-wisconsin-political",
      "relation": "not_established",
      "rationale": "The explorer topic concerns synthetic-media disclosures in specified political communications. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. This is a targeted political-communications law, not a comprehensive enterprise AI framework. The medium, content and statutory definitions determine the disclosure required.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://content.govdelivery.com/accounts/WIGOV/bulletins/391af46"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-wisconsin-insurance",
      "relation": "not_established",
      "rationale": "The explorer topic concerns insurer AI-program evidence, testing and vendor oversight. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. The bulletin explains regulatory expectations under existing insurance laws and permits alternative ways to demonstrate compliance. It is guidance, not a new AI statute or a requirement for one prescribed documentation format.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://oci.wi.gov/Pages/Regulation/Bulletin20250318AI.aspx"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-us-new-york-city-aedt",
      "relation": "not_established",
      "rationale": "The explorer topic concerns employment-tool bias-audit scope, independence and notice. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. This is a New York City requirement for defined hiring and promotion tools, not a statewide rule or a general certification that an AI system is fair. The city rules and definitions determine coverage.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.nyc.gov/site/dca/about/automated-employment-decision-tools.page"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-eu-prohibited",
      "relation": "not_established",
      "rationale": "The explorer topic concerns classification of a proposed use against specified prohibited practices. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Consult the current article and relevant exceptions. A general risk score or a successful test cannot authorize a prohibited use.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-5"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-eu-high-risk",
      "relation": "not_established",
      "rationale": "The explorer topic concerns use classification and high-risk documentation and control requirements. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Not every consequential use of AI is automatically classified as high-risk. Article 6, the annexes, exceptions and applicable transition provisions require review.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-6"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-eu-human-oversight",
      "relation": "not_established",
      "rationale": "The explorer topic concerns usable reviewer authority and evidence of what intervention changed. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. This is a scoped legal provision, not a universal requirement to put a person behind every AI output. Node & Norm’s research questions do not establish legal conformity.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02024R1689-20260727"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-eu-transparency",
      "relation": "not_established",
      "rationale": "The explorer topic concerns whether information about AI interaction or generated content reaches its audience. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Not every AI use or piece of assisted content has the same disclosure duty. The type of interaction, content, actor and exception matters.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-50"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-eu-gpai",
      "relation": "not_established",
      "rationale": "The explorer topic concerns provider documentation and downstream model-capability and risk information. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. General-purpose AI is a defined regulatory category; it does not mean artificial general intelligence. Provider roles, exemptions and systemic-risk classification require separate examination.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-53"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-eu-value-chain",
      "relation": "not_established",
      "rationale": "The explorer topic concerns responsibility for a version, intended use and changed supplier role. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. A supplier contract or an internal job title does not by itself settle the statutory role. Article 25 addresses specified value-chain circumstances.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-25"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-eu-gdpr",
      "relation": "not_established",
      "rationale": "The explorer topic concerns personal-data correction, information and conditional automated-decision rights. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Article 22 has defined conditions, exceptions and safeguards; it is not a general prohibition on all automated decisions. Other data-protection duties can apply even when Article 22 does not.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-eu-nis2",
      "relation": "not_established",
      "rationale": "The explorer topic concerns covered organizations’ cybersecurity incident response and supply-chain security. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Coverage depends on sector, entity characteristics and national implementation. NIS2 is not an AI-specific assurance standard.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/nis2-directive"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-eu-cra",
      "relation": "not_established",
      "rationale": "The explorer topic concerns digital-product security, vulnerability handling and support-period evidence. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Product scope, exclusions, actor responsibilities and transition provisions matter. Inclusion here does not mean every AI service falls within the Act.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-kr-ai-basic",
      "relation": "not_established",
      "rationale": "The explorer topic concerns Korean use categories, transparency, safety and oversight arrangements. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the current Korean instruments and implementing guidance for an applicability decision. Terms such as high-impact should not be assumed equivalent to EU high-risk classifications.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.msit.go.kr/eng/bbs/view.do?bbsSeqNo=42&mId=4&mPid=2&nttSeqNo=1214&sCode=eng"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-cn-generative",
      "relation": "not_established",
      "rationale": "The explorer topic concerns public-facing Chinese generative services, data practices and complaint handling. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. The measures distinguish public-facing services from research and uses not offered to the domestic public. Other applicable Chinese laws and later measures require separate review.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.cac.gov.cn/2023-07/13/c_1690898327029107.htm"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-jp-ai-promotion",
      "relation": "not_established",
      "rationale": "The explorer topic concerns Japan’s governmental and stakeholder promotion-and-governance responsibilities. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. The law’s promotion-and-governance approach should not be presented as the same risk-classification regime used elsewhere. Existing laws and sector guidance remain relevant.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www8.cao.go.jp/cstp/ai/ai_act/ai_act.html"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-in-dpdp",
      "relation": "not_established",
      "rationale": "The explorer topic concerns covered digital-personal-data processing, organizational duties and individual rights. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. The law and rules have scope conditions, exemptions and phased provisions. Their existence does not establish that every duty applies to every AI activity.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.pib.gov.in/PressReleseDetailm.aspx?PRID=2190655&lang=2&reg=48"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-br-lgpd",
      "relation": "not_established",
      "rationale": "The explorer topic concerns information and contestability for covered automated personal-data decisions. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. The right to request review should not be relabeled as a universal guarantee of human review. Scope, exceptions and regulator guidance require examination.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.gov.br/anpd/pt-br/assuntos/titular-de-dados/direito-dos-titulares"
    },
    {
      "program_id": "cdfi",
      "topic_id": "reg-institutional-commitments",
      "relation": "context",
      "rationale": "The explorer topic concerns purchasing commitments, supplier responsibilities and evidence of fulfillment. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside purchasing commitments, supplier responsibilities and evidence of fulfillment, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Procurement, contracts and stated purposes, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. This topic concerns commitments to examine, rather than a single law. The terms of a particular agreement, applicable law and responsible parties determine its effect. A supplier assurance does not by itself establish that a control worked.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "iso-42001",
      "relation": "context",
      "rationale": "The explorer topic concerns organizational AI responsibilities, operation and management-system improvement. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside organizational AI responsibilities, operation and management-system improvement, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI management systems · ISO/IEC 42001:2023, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.iso.org/standard/42001"
    },
    {
      "program_id": "cdfi",
      "topic_id": "iso-23894",
      "relation": "context",
      "rationale": "The explorer topic concerns identification, ownership and treatment of context-specific AI risks. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside identification, ownership and treatment of context-specific AI risks, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI risk management · ISO/IEC 23894:2023, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.iso.org/standard/77304.html"
    },
    {
      "program_id": "cdfi",
      "topic_id": "iso-42005",
      "relation": "context",
      "rationale": "The explorer topic concerns documented impacts on affected people across a system lifecycle. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside documented impacts on affected people across a system lifecycle, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI impact assessment · ISO/IEC 42005:2025, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.iso.org/standard/42005"
    },
    {
      "program_id": "cdfi",
      "topic_id": "iso-22989",
      "relation": "context",
      "rationale": "The explorer topic concerns shared terminology for the system, actors and activities. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside shared terminology for the system, actors and activities, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Shared AI terminology · ISO/IEC 22989:2022, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.iso.org/standard/74296.html"
    },
    {
      "program_id": "cdfi",
      "topic_id": "nist-ai-rmf-1-0",
      "relation": "context",
      "rationale": "The explorer topic concerns connections between identified risks, evaluation findings and management decisions. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside connections between identified risks, evaluation findings and management decisions, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI Risk Management Framework · NIST AI RMF 1.0, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "cdfi",
      "topic_id": "oecd-ai-principles",
      "relation": "context",
      "rationale": "The explorer topic concerns human rights, transparency and an accountable response to AI use. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside human rights, transparency and an accountable response to AI use, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Trustworthy AI principles · OECD, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://oecd.ai/en/ai-principles"
    },
    {
      "program_id": "cdfi",
      "topic_id": "unesco-ai-ethics",
      "relation": "context",
      "rationale": "The explorer topic concerns dignity, inclusion, human oversight and responsibility for harm. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside dignity, inclusion, human oversight and responsibility for harm, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Ethics of AI · UNESCO Recommendation, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.unesco.org/en/artificial-intelligence/recommendation-ethics"
    },
    {
      "program_id": "cdfi",
      "topic_id": "owasp-llm-top-10-2025",
      "relation": "context",
      "rationale": "The explorer topic concerns prompt injection, information disclosure and excessive agency in LLM applications. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside prompt injection, information disclosure and excessive agency in LLM applications, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for LLM application security risks · OWASP Top 10 (2025), with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "mitre-atlas",
      "relation": "context",
      "rationale": "The explorer topic concerns documented adversary techniques and evidence for defenses. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside documented adversary techniques and evidence for defenses, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Adversarial threat knowledge · MITRE ATLAS, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "nist-digital-identity-4",
      "relation": "not_established",
      "rationale": "The explorer topic concerns user identity proofing, authentication and federation in the guideline’s scope. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "cdfi",
      "topic_id": "nist-generative-ai-profile",
      "relation": "context",
      "rationale": "The explorer topic concerns deployment-specific generative-AI risks and management actions. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside deployment-specific generative-AI risks and management actions, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Generative AI risk profile · NIST AI 600-1, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence"
    },
    {
      "program_id": "cdfi",
      "topic_id": "iso-27001",
      "relation": "context",
      "rationale": "The explorer topic concerns confidentiality, integrity and availability of information and retained records. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside confidentiality, integrity and availability of information and retained records, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Information security management · ISO/IEC 27001:2022, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.iso.org/standard/27001"
    },
    {
      "program_id": "cdfi",
      "topic_id": "roles-leadership",
      "relation": "context",
      "rationale": "The explorer topic concerns leadership ownership, risk acceptance and escalation beyond a system owner. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside leadership ownership, risk acceptance and escalation beyond a system owner, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Leadership and accountable ownership, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Organizational responsibility must be examined in context; naming an owner is not evidence of effective oversight.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "roles-delivery",
      "relation": "context",
      "rationale": "The explorer topic concerns responsibilities and change authority across developers, suppliers and deployers. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside responsibilities and change authority across developers, suppliers and deployers, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Developers, suppliers and deployers, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. These are descriptive delivery roles. Any legal meaning or duty must be checked against the applicable instrument.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "roles-domain-users",
      "relation": "direct",
      "rationale": "CDFI requires qualified domain oversight; a fluent answer or automated score cannot supply the human theological judgment that remains required.",
      "investigation_question": "When CDFI is examined alongside the information, expertise, time and discretion available to frontline specialists, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Domain specialists and frontline users, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. A credential or job title alone does not establish task competence, available time or freedom to disagree.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "cdfi",
      "topic_id": "roles-reviewers",
      "relation": "direct",
      "rationale": "Proposed judge-reliability checks and qualified theological review raise specific questions about assessor remit, access and competence.",
      "investigation_question": "When CDFI is examined alongside reviewer remit, access, competence and independence, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Reviewers and independent assessors, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Independence, access and competence are separate matters; none follows automatically from an assessment label.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "roles-affected-people",
      "relation": "context",
      "rationale": "The explorer topic concerns routes by which affected people can challenge an account and obtain a response. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside routes by which affected people can challenge an account and obtain a response, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Affected people and routes to challenge, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. A feedback channel is not necessarily an appeal process or an effective remedy. Rights and duties vary by context.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "roles-intervention",
      "relation": "context",
      "rationale": "The explorer topic concerns powers to pause, override, investigate, hear an appeal and authorize repair. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside powers to pause, override, investigate, hear an appeal and authorize repair, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Authority to intervene and repair, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Formal authority, usable access and an effect on the action are separate questions. A research link does not establish legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "controls-inventory",
      "relation": "context",
      "rationale": "The explorer topic concerns identification of the version, intended use, owner and changes under examination. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside identification of the version, intended use, owner and changes under examination, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Inventories and change records, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. An inventory describes the stated estate; its completeness and accuracy still need examination.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "controls-data",
      "relation": "context",
      "rationale": "The explorer topic concerns authorized access, retention and examination of decision records. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside authorized access, retention and examination of decision records, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Data handling and retained records, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Retention and access depend on context and applicable duties. More data is not automatically better evidence.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "cdfi",
      "topic_id": "controls-access",
      "relation": "not_established",
      "rationale": "The explorer topic concerns the identity and delegated permission behind an action and its withdrawal. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. NIST digital identity guidance has a stated user and government-system scope; it is not a complete specification for agent identity or delegation. The related revocation study’s initial qualification uses scripted workers and a local database; autonomous-agent effectiveness remains unestablished.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "cdfi",
      "topic_id": "controls-intervention",
      "relation": "not_established",
      "rationale": "The explorer topic concerns stopping, containment, recovery and irreversible effects. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Some actions cannot be reversed. A stop control, a recovery process and correction of harm require different evidence.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "controls-monitoring",
      "relation": "context",
      "rationale": "The explorer topic concerns the chain from a warning or complaint to assigned action and follow-up. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside the chain from a warning or complaint to assigned action and follow-up, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Logs, incidents and follow-up, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. A recorded warning is not evidence that anyone understood it or that a corrective action worked.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "controls-boundaries",
      "relation": "not_established",
      "rationale": "The explorer topic concerns permitted tool actions and dependencies outside the application. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. A documented boundary does not establish enforcement. Test the relevant configuration and retain limits on external visibility.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evaluation-model",
      "relation": "direct",
      "rationale": "CDFI’s scoring architecture translates literature-derived failure definitions and cap gates into model-response evaluation; the chosen weights remain provisional.",
      "investigation_question": "When CDFI is examined alongside model tasks, scores, failures and limits of a capability result, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Model capabilities and limitations, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. A model benchmark does not by itself establish the performance or safety of an application using that model.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evaluation-application",
      "relation": "direct",
      "rationale": "The method is domain-specific to SAICRED, so the relation between a prompt, intended Catholic use and evaluation criterion must be made explicit.",
      "investigation_question": "When CDFI is examined alongside testing in the application’s intended task and operating conditions, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Application and mission-specific tests, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Performance under a stated test condition does not establish performance in every population, environment or later version.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evaluation-control",
      "relation": "not_established",
      "rationale": "The explorer topic concerns whether a requested intervention changed the governed action. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. A scripted control demonstration, a documentary reconstruction and an observed human intervention support different conclusions. The related revocation study’s initial qualification uses scripted workers and a local database; autonomous-agent effectiveness remains unestablished.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evaluation-adversarial",
      "relation": "direct",
      "rationale": "Its observable failure definitions and disqualifying gates can inform bounded challenge cases, without establishing coverage of security attacks or all doctrinal errors.",
      "investigation_question": "When CDFI is examined alongside controlled attack or failure paths and responses at a tested boundary, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Adversarial tests and failure injection, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Passing selected scenarios does not establish complete security. Testing authority and limits must be agreed for the setting.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evaluation-human-factors",
      "relation": "context",
      "rationale": "The explorer topic concerns workload, information, incentives and opportunities for human challenge. This can frame an organizational or research condition for inspecting CDFI’s source-to-criterion translation. The doctrinal scoring architecture has not evaluated this governance regime, certified an organization or validated an operating control.",
      "investigation_question": "When CDFI is examined alongside workload, information, incentives and opportunities for human challenge, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Human judgment and working conditions, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Records can describe conditions; measuring behavior requires an appropriate study. Subjective workload does not establish effective oversight.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evaluation-reproducibility",
      "relation": "direct",
      "rationale": "The preserved differences among formula, configuration and calculator make exact inputs, scales, weights and versions necessary to inspect a score.",
      "investigation_question": "When CDFI is examined alongside retained inputs, versions, scoring rules, procedures and results, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Reproducibility and retained test artifacts, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Repeatability does not establish that the chosen measure answers the intended question or generalizes to field use.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evaluation-regression",
      "relation": "direct",
      "rationale": "A scoring-rule or configuration change can change gates and rankings, so an earlier result cannot silently transfer to the revised contract.",
      "investigation_question": "When CDFI is examined alongside which findings require rechecking after a configuration or operating change, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Rechecking after changes, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. A previous result belongs to its tested configuration and conditions; it should not silently transfer to an updated system.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evidence-claims",
      "relation": "direct",
      "rationale": "CDFI’s open scoring-contract reconciliation directly concerns which criterion governs a conclusion and what the reported score supports.",
      "investigation_question": "When CDFI is examined alongside the conclusion, assessment criteria and scope offered to a reader, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Claims, criteria and scope, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. A criterion may come from law, a standard, a contract or a research method. Identify its source rather than treating them as interchangeable.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evidence-provenance",
      "relation": "direct",
      "rationale": "The seven-publication source-to-method map preserves the progression from a source claim to a failure definition, score and review requirement.",
      "investigation_question": "When CDFI is examined alongside record origin, transformation, gaps and uncertain attribution, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Sources, provenance and missing records, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. A traceable record can still be incomplete or wrong. Provenance supports examination without establishing truth on its own.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.w3.org/TR/prov-dm/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evidence-reconstruction",
      "relation": "not_established",
      "rationale": "The explorer topic concerns the chronology of a decision, intervention and subsequent events. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. A missing record is not automatically evidence of failure; an event occurring later does not by itself establish causation.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evidence-uncertainty",
      "relation": "direct",
      "rationale": "Unreconciled scales or weights and pending human theological validation require an unresolved or qualified account rather than a definitive ranking.",
      "investigation_question": "When CDFI is examined alongside conflicting evidence, alternative explanations and unresolved findings, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Conflicting evidence and unresolved findings, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Unresolved means the available evidence does not settle the question. It should not silently become either approval or a finding of failure.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evidence-review",
      "relation": "direct",
      "rationale": "A reviewer needs to inspect the source-to-method translation and challenge the scoring choices; public availability alone does not validate them.",
      "investigation_question": "When CDFI is examined alongside a reader’s ability to trace and challenge the reasoning and sources, which source-derived evaluation criterion and qualified review would justify the proposed judgment, and which part remains outside the scoring contract?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Review, challenge and communication, with its actor, intended use and stated limits.",
        "The exact source-to-method translation, prompt or response, criterion, scale, weight, gate and governing configuration.",
        "The retained scoring result, counterexamples and qualified human review addressing disagreements and unvalidated choices."
      ],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. Public availability does not establish independent validation. Access restrictions and the assessor’s remit should remain clear.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "cdfi",
      "topic_id": "evidence-correction",
      "relation": "not_established",
      "rationale": "The explorer topic concerns the authorized correction and evidence of whether it reached its intended recipient. CDFI currently concerns domain-specific response scoring and evaluation governance for SAICRED. No specific study, control implementation or jurisdictional application covering this subject is established in its public scope.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. The scoring contract still needs reconciliation and qualified human theological validation; this is not doctrinal certification, legal compliance or demonstrated deployment effectiveness. An assurance finding does not itself authorize a correction. Responsibility stays with the people or institutions empowered to act.",
      "program_evidence_url": "https://github.com/node-and-norm/cdfi-framework/blob/54d58532ada2cef692d088c3881a1a92f40f68cc/TRANSLATION-METHOD.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-consumer",
      "relation": "context",
      "rationale": "The explorer topic concerns claims made to customers about system behavior. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning claims made to customers about system behavior, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for U.S. consumer protection, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Coverage depends on the conduct, entity and statutory jurisdiction; an AI label does not decide the legal analysis.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.ftc.gov/legal-library/browse/statutes/federal-trade-commission-act"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-equality",
      "relation": "context",
      "rationale": "The explorer topic concerns accessible challenge to technology-assisted employment decisions. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning accessible challenge to technology-assisted employment decisions, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Employment equality and disability, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Different statutes cover different employers, people and decisions. The listed resources do not determine whether a particular decision was discriminatory.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.eeoc.gov/fact-sheet/federal-laws-prohibiting-job-discrimination-questions-and-answers"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-credit",
      "relation": "direct",
      "rationale": "GDI’s reconstruction of evidence and decision factors can frame an inspection question about recorded principal reasons; the format itself does not meet a creditor’s notice duties.",
      "investigation_question": "For a proposed GDI account concerning principal reasons for an adverse credit decision, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Credit decisions and reasons, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Notice requirements vary with the transaction and applicant. This topic describes selected credit rules, not all financial-services obligations.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.consumerfinance.gov/compliance/compliance-resources/other-applicable-requirements/equal-credit-opportunity-act/"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-medical",
      "relation": "not_established",
      "rationale": "The explorer topic concerns device-function classification, intended use and device evidence. GDI currently specifies decision evidence and checks selected structural, routing and receipt-integrity properties. No specific subject-matched implementation or study is established for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Whether software is a medical device depends on its function and intended use. The AI lifecycle draft is not a binding rule or a completed approval of any product.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.fda.gov/regulatory-information/search-fda-guidance-documents/policy-device-software-functions-and-mobile-medical-applications"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-california",
      "relation": "context",
      "rationale": "The explorer topic concerns covered personal data, automated decisions and consumer requests. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning covered personal data, automated decisions and consumer requests, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for California privacy and automated decisions, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Coverage, exceptions and compliance schedules differ across provisions. These rules do not apply identically to every business or every use of AI.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.cppa.ca.gov/regulations/"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-california-employment",
      "relation": "context",
      "rationale": "The explorer topic concerns retained employment-decision records and discriminatory effects. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning retained employment-decision records and discriminatory effects, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for California: employment decision systems, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. This entry concerns the 2025 employment regulations, not the separate CCPA automated-decision rules or all subsequently enacted employment AI laws. Covered entities and particular records require a scoped assessment.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://calcivilrights.ca.gov/2025/06/30/civil-rights-council-secures-approval-for-regulations-to-protect-against-employment-discrimination-related-to-artificial-intelligence/"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-california-frontier",
      "relation": "context",
      "rationale": "The explorer topic concerns catastrophic-risk frameworks, mitigations and reported concerns. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning catastrophic-risk frameworks, mitigations and reported concerns, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for California: frontier-model transparency, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Frontier models, large frontier developers, catastrophic risks and covered employees are defined categories. Publishing a framework does not establish that a model is safe for every application.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://oag.ca.gov/sb53"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-california-companions",
      "relation": "context",
      "rationale": "The explorer topic concerns companion disclosure, crisis protocols and protections for minors. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning companion disclosure, crisis protocols and protections for minors, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for California: companion-chatbot safeguards, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. The definition and qualified business-use, game and voice-assistant exclusions determine coverage. Current three-hour reminders concern known minors during continuing interactions. These provisions do not create a universal human-review or override right. SB1119 changes the known-minor provisions and adds requirements with separate operative dates; the current and forthcoming regimes must be read separately.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260SB243"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-colorado",
      "relation": "context",
      "rationale": "The explorer topic concerns data correction and reconsideration of consequential decisions. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning data correction and reconsideration of consequential decisions, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Colorado: consequential decisions, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Definitions, exemptions, implementing rules and the timing of individual duties matter. The 2024 law alone is not a current account of this framework.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://leg.colorado.gov/bills/sb26-189"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-colorado-health-review",
      "relation": "context",
      "rationale": "The explorer topic concerns qualified review before a medical-necessity denial is issued. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning qualified review before a medical-necessity denial is issued, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Colorado: AI-assisted health-care review, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. This entry covers selected utilization-review provisions in the enacted text, not the broader introduced bill. Relevant entity definitions and coverage terms matter. The research question is an editorial connection to practical human control, not a claim that TAE, HIT or CEC establishes compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1139"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-colorado-psychotherapy",
      "relation": "context",
      "rationale": "The explorer topic concerns real-time professional participation and withdrawal of recording consent. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning real-time professional participation and withdrawal of recording consent, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Colorado: AI use in psychotherapy, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. The recording and transcription consent rule is specific to those uses. Educational, research, wellness and certain FDA-authorized uses have defined conditions or exceptions. The enacted text also restricts misleading claims about professional equivalence and therapist-like confidentiality.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1195"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-colorado-conversational-ai",
      "relation": "context",
      "rationale": "The explorer topic concerns interaction-level disclosures, crisis escalation and protections for minors. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning interaction-level disclosures, crisis escalation and protections for minors, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Colorado: conversational AI safeguards, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Coverage depends on statutory definitions and exclusions, including specified enterprise, research, transactional, health-care and educational uses. The age-estimation wording precedes the January 2027 clause; the later date should not be applied to every duty. Proposed implementing rules require a separate status check.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1263"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-connecticut-employment",
      "relation": "context",
      "rationale": "The explorer topic concerns employment notices, the system’s role and responses to bias-test findings. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning employment notices, the system’s role and responses to bias-test findings, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Connecticut: automated employment decisions, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Employment decisions, developers, deployers and substantial influence are defined terms with exclusions. These sections do not create a general right to override every automated decision. The act’s effective date must be distinguished from the later start of specified duties.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.cga.ct.gov/2026/ACT/PA/PDF/2026PA-00015-R00SB-00005-PA.PDF"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-illinois-employment",
      "relation": "context",
      "rationale": "The explorer topic concerns AI-related discrimination, protected-class proxies and employment notice. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning AI-related discrimination, protected-class proxies and employment notice, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Illinois: AI in employment decisions, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Coverage follows the Human Rights Act and specified employment activities. Notice implementation is subject to agency rulemaking. This statute does not create a universal human-review or override requirement.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://ilga.gov/legislation/PublicActs/View/103-0804"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-illinois-psychological",
      "relation": "context",
      "rationale": "The explorer topic concerns professional responsibility and approval for permitted AI support. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning professional responsibility and approval for permitted AI support, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Illinois: AI support in psychological services, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. The act defines covered services and professionals. Additional restrictions concern emotion or mental-state detection and consent for recording or transcription used in supplementary support; this is not a blanket rule for all health software.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://ilga.gov/Legislation/PublicActs/View/104-0054"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-illinois-video",
      "relation": "context",
      "rationale": "The explorer topic concerns video-interview consent, sharing, deletion and demographic reporting. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning video-interview consent, sharing, deletion and demographic reporting, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Illinois: AI video interviews, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. The act concerns AI analysis of applicant-submitted videos for Illinois-based positions. Sole reliance on AI for in-person interview selection triggers reporting; the act does not categorically prohibit that reliance.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://my.ilga.gov/Legislation/ILCS/Articles?ActID=4015&Chapter=EMPLOYMENT&ChapterID=68&MajorTopic=BUSINESS+AND+EMPLOYMENT"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-illinois-biometric",
      "relation": "context",
      "rationale": "The explorer topic concerns biometric collection, consent, disclosure and destruction. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning biometric collection, consent, disclosure and destruction, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Illinois: biometric information privacy, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Statutory definitions and exclusions determine coverage; not all images, identity data or AI uses are covered biometrics. This is a biometric-privacy law, not a general AI-governance act.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.ilga.gov/legislation/ilcs/fulltext?DocName=074000140K15"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-illinois-frontier",
      "relation": "context",
      "rationale": "The explorer topic concerns independent audit access to a frontier developer’s framework evidence. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning independent audit access to a frontier developer’s framework evidence, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Illinois: frontier-model safety and audits, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Model and developer thresholds limit coverage. The act’s general effective date differs from the start of framework and audit duties; it should not be presented as an audit obligation already in force.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.ilga.gov/documents/legislation/PublicActs/104/104-0538.htm"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-minnesota-profiling",
      "relation": "context",
      "rationale": "The explorer topic concerns data correction, reevaluation and the effect on a profiling outcome. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning data correction, reevaluation and the effect on a profiling outcome, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Minnesota: profiling and reevaluation, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. The act’s coverage thresholds, exclusions and consumer definition apply. These rights do not apply identically to every employment or service decision merely because profiling is involved.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.ag.state.mn.us/Data-Privacy/Consumer/"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-new-york-government",
      "relation": "context",
      "rationale": "The explorer topic concerns accuracy of a state-agency AI inventory and its disclosures. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning accuracy of a state-agency AI inventory and its disclosures, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for New York: agency AI inventory and disclosure, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. This entry concerns state agencies, not a general private-sector mandate. The 2025 amendment replaced the earlier impact-assessment and meaningful-human-review provisions; those removed provisions should not be treated as current duties.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/STT/103-E"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-new-york-raise",
      "relation": "context",
      "rationale": "The explorer topic concerns frontier safeguards, deployment decisions and critical-incident reporting. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning frontier safeguards, deployment decisions and critical-incident reporting, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for New York: frontier-model transparency, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Coverage depends on the statutory model and developer definitions and the New York connection. Academic-research and other specified exceptions apply. Publication alone does not establish effective control.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/bills/2025/S8828"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-new-york-companions",
      "relation": "context",
      "rationale": "The explorer topic concerns nonhuman disclosure, crisis referrals and separately scoped minor safeguards. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning nonhuman disclosure, crisis referrals and separately scoped minor safeguards, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for New York: AI companion safeguards, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Coverage concerns defined companions for personal use in New York, with exclusions for specified customer-service, research, technical-assistance and internal-business systems. Article 47 does not require a staffed human handoff or guarantee detection. Separate Safe by Design provisions (§1540(7)) require age assurance before covered users can access integrated companions on covered platforms, and disable access by default for covered minors, subject to parental override, from 1 January 2027. S9051B was signed on 28 October 2026 as chapter 368, adding separate safeguards for minors. Its published text preserves Article 47. The start date of the new safeguards remains under review because the legislative text and official signing announcement differ.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/GBS/1700"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-texas",
      "relation": "context",
      "rationale": "The explorer topic concerns actor-specific disclosures, prohibited uses and statutory sandbox conditions. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning actor-specific disclosures, prohibited uses and statutory sandbox conditions, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Texas: AI uses and disclosures, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Requirements depend on the actor and use. The discrimination prohibition has an intent requirement; disparate impact alone does not establish that intent. A research sandbox is not automatically a participant in the statutory program.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://capitol.texas.gov/billlookup/BillSummary.aspx?Bill=HB149&LegSess=89R"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-utah-chatbots",
      "relation": "context",
      "rationale": "The explorer topic concerns mental-health-chatbot disclosure points and information practices. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning mental-health-chatbot disclosure points and information practices, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Utah: mental-health chatbots, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. This entry covers the mental-health-chatbot provisions, not every Utah AI law. The defined chatbot, supplier and Utah-user scope matters. A disclosure does not establish clinical effectiveness or confer professional licensure.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://le.utah.gov/xcode/Title13/Chapter72A/C13-72a-P2_2025050720250507.pdf"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-virginia-profiling",
      "relation": "context",
      "rationale": "The explorer topic concerns profiling opt-outs and appeals of refused privacy requests. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning profiling opt-outs and appeals of refused privacy requests, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Virginia: profiling and privacy requests, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. An appeal of a refused privacy request is not a universal appeal of the underlying automated decision. Coverage thresholds, entity and data exclusions, and the consumer definition must be examined.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://law.lis.virginia.gov/vacode/title59.1/chapter53/section59.1-577/"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-wisconsin-political",
      "relation": "not_established",
      "rationale": "The explorer topic concerns synthetic-media disclosures in specified political communications. GDI currently specifies decision evidence and checks selected structural, routing and receipt-integrity properties. No specific subject-matched implementation or study is established for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. This is a targeted political-communications law, not a comprehensive enterprise AI framework. The medium, content and statutory definitions determine the disclosure required.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://content.govdelivery.com/accounts/WIGOV/bulletins/391af46"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-wisconsin-insurance",
      "relation": "context",
      "rationale": "The explorer topic concerns insurer AI-program evidence, testing and vendor oversight. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning insurer AI-program evidence, testing and vendor oversight, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Wisconsin: insurance AI governance guidance, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. The bulletin explains regulatory expectations under existing insurance laws and permits alternative ways to demonstrate compliance. It is guidance, not a new AI statute or a requirement for one prescribed documentation format.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://oci.wi.gov/Pages/Regulation/Bulletin20250318AI.aspx"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-us-new-york-city-aedt",
      "relation": "context",
      "rationale": "The explorer topic concerns employment-tool bias-audit scope, independence and notice. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning employment-tool bias-audit scope, independence and notice, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for New York City: employment-tool bias audits, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. This is a New York City requirement for defined hiring and promotion tools, not a statewide rule or a general certification that an AI system is fair. The city rules and definitions determine coverage.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.nyc.gov/site/dca/about/automated-employment-decision-tools.page"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-eu-prohibited",
      "relation": "context",
      "rationale": "The explorer topic concerns classification of a proposed use against specified prohibited practices. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning classification of a proposed use against specified prohibited practices, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Prohibited AI practices, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Consult the current article and relevant exceptions. A general risk score or a successful test cannot authorize a prohibited use.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-5"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-eu-high-risk",
      "relation": "context",
      "rationale": "The explorer topic concerns use classification and high-risk documentation and control requirements. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning use classification and high-risk documentation and control requirements, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for High-risk systems and requirements, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Not every consequential use of AI is automatically classified as high-risk. Article 6, the annexes, exceptions and applicable transition provisions require review.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-6"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-eu-human-oversight",
      "relation": "context",
      "rationale": "The explorer topic concerns usable reviewer authority and evidence of what intervention changed. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning usable reviewer authority and evidence of what intervention changed, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Human oversight, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. This is a scoped legal provision, not a universal requirement to put a person behind every AI output. Node & Norm’s research questions do not establish legal conformity.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02024R1689-20260727"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-eu-transparency",
      "relation": "context",
      "rationale": "The explorer topic concerns whether information about AI interaction or generated content reaches its audience. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning whether information about AI interaction or generated content reaches its audience, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Transparency and generated content, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Not every AI use or piece of assisted content has the same disclosure duty. The type of interaction, content, actor and exception matters.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-50"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-eu-gpai",
      "relation": "context",
      "rationale": "The explorer topic concerns provider documentation and downstream model-capability and risk information. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning provider documentation and downstream model-capability and risk information, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for General-purpose AI models, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. General-purpose AI is a defined regulatory category; it does not mean artificial general intelligence. Provider roles, exemptions and systemic-risk classification require separate examination.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-53"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-eu-value-chain",
      "relation": "direct",
      "rationale": "GDI’s versioned authority and obligation record can identify which actor was understood to control a decision or component; the legal provider/deployer role still needs separate analysis.",
      "investigation_question": "For a proposed GDI account concerning responsibility for a version, intended use and changed supplier role, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Responsibilities across the value chain, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. A supplier contract or an internal job title does not by itself settle the statutory role. Article 25 addresses specified value-chain circumstances.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-25"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-eu-gdpr",
      "relation": "context",
      "rationale": "The explorer topic concerns personal-data correction, information and conditional automated-decision rights. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning personal-data correction, information and conditional automated-decision rights, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Personal data and automated decisions, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Article 22 has defined conditions, exceptions and safeguards; it is not a general prohibition on all automated decisions. Other data-protection duties can apply even when Article 22 does not.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-eu-nis2",
      "relation": "not_established",
      "rationale": "The explorer topic concerns covered organizations’ cybersecurity incident response and supply-chain security. GDI currently specifies decision evidence and checks selected structural, routing and receipt-integrity properties. No specific subject-matched implementation or study is established for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Coverage depends on sector, entity characteristics and national implementation. NIS2 is not an AI-specific assurance standard.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/nis2-directive"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-eu-cra",
      "relation": "not_established",
      "rationale": "The explorer topic concerns digital-product security, vulnerability handling and support-period evidence. GDI currently specifies decision evidence and checks selected structural, routing and receipt-integrity properties. No specific subject-matched implementation or study is established for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Product scope, exclusions, actor responsibilities and transition provisions matter. Inclusion here does not mean every AI service falls within the Act.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-kr-ai-basic",
      "relation": "context",
      "rationale": "The explorer topic concerns Korean use categories, transparency, safety and oversight arrangements. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning Korean use categories, transparency, safety and oversight arrangements, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Republic of Korea: AI Basic Act, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the current Korean instruments and implementing guidance for an applicability decision. Terms such as high-impact should not be assumed equivalent to EU high-risk classifications.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.msit.go.kr/eng/bbs/view.do?bbsSeqNo=42&mId=4&mPid=2&nttSeqNo=1214&sCode=eng"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-cn-generative",
      "relation": "context",
      "rationale": "The explorer topic concerns public-facing Chinese generative services, data practices and complaint handling. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning public-facing Chinese generative services, data practices and complaint handling, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for China: generative AI services, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. The measures distinguish public-facing services from research and uses not offered to the domestic public. Other applicable Chinese laws and later measures require separate review.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.cac.gov.cn/2023-07/13/c_1690898327029107.htm"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-jp-ai-promotion",
      "relation": "not_established",
      "rationale": "The explorer topic concerns Japan’s governmental and stakeholder promotion-and-governance responsibilities. GDI currently specifies decision evidence and checks selected structural, routing and receipt-integrity properties. No specific subject-matched implementation or study is established for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. The law’s promotion-and-governance approach should not be presented as the same risk-classification regime used elsewhere. Existing laws and sector guidance remain relevant.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www8.cao.go.jp/cstp/ai/ai_act/ai_act.html"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-in-dpdp",
      "relation": "context",
      "rationale": "The explorer topic concerns covered digital-personal-data processing, organizational duties and individual rights. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning covered digital-personal-data processing, organizational duties and individual rights, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for India: digital personal data, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. The law and rules have scope conditions, exemptions and phased provisions. Their existence does not establish that every duty applies to every AI activity.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.pib.gov.in/PressReleseDetailm.aspx?PRID=2190655&lang=2&reg=48"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-br-lgpd",
      "relation": "context",
      "rationale": "The explorer topic concerns information and contestability for covered automated personal-data decisions. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning information and contestability for covered automated personal-data decisions, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Brazil: data protection and review, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. The right to request review should not be relabeled as a universal guarantee of human review. Scope, exceptions and regulator guidance require examination.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.gov.br/anpd/pt-br/assuntos/titular-de-dados/direito-dos-titulares"
    },
    {
      "program_id": "gdi",
      "topic_id": "reg-institutional-commitments",
      "relation": "direct",
      "rationale": "GDI records obligations and their sources, making purchasing commitments a specific candidate input rather than relying on a supplier’s assurance as proof.",
      "investigation_question": "For a proposed GDI account concerning purchasing commitments, supplier responsibilities and evidence of fulfillment, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Procurement, contracts and stated purposes, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. This topic concerns commitments to examine, rather than a single law. The terms of a particular agreement, applicable law and responsible parties determine its effect. A supplier assurance does not by itself establish that a control worked.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "iso-42001",
      "relation": "context",
      "rationale": "The explorer topic concerns organizational AI responsibilities, operation and management-system improvement. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning organizational AI responsibilities, operation and management-system improvement, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI management systems · ISO/IEC 42001:2023, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.iso.org/standard/42001"
    },
    {
      "program_id": "gdi",
      "topic_id": "iso-23894",
      "relation": "context",
      "rationale": "The explorer topic concerns identification, ownership and treatment of context-specific AI risks. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning identification, ownership and treatment of context-specific AI risks, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI risk management · ISO/IEC 23894:2023, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.iso.org/standard/77304.html"
    },
    {
      "program_id": "gdi",
      "topic_id": "iso-42005",
      "relation": "context",
      "rationale": "The explorer topic concerns documented impacts on affected people across a system lifecycle. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning documented impacts on affected people across a system lifecycle, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI impact assessment · ISO/IEC 42005:2025, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.iso.org/standard/42005"
    },
    {
      "program_id": "gdi",
      "topic_id": "iso-22989",
      "relation": "context",
      "rationale": "The explorer topic concerns shared terminology for the system, actors and activities. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning shared terminology for the system, actors and activities, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Shared AI terminology · ISO/IEC 22989:2022, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.iso.org/standard/74296.html"
    },
    {
      "program_id": "gdi",
      "topic_id": "nist-ai-rmf-1-0",
      "relation": "context",
      "rationale": "The explorer topic concerns connections between identified risks, evaluation findings and management decisions. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning connections between identified risks, evaluation findings and management decisions, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI Risk Management Framework · NIST AI RMF 1.0, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "gdi",
      "topic_id": "oecd-ai-principles",
      "relation": "context",
      "rationale": "The explorer topic concerns human rights, transparency and an accountable response to AI use. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning human rights, transparency and an accountable response to AI use, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Trustworthy AI principles · OECD, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://oecd.ai/en/ai-principles"
    },
    {
      "program_id": "gdi",
      "topic_id": "unesco-ai-ethics",
      "relation": "context",
      "rationale": "The explorer topic concerns dignity, inclusion, human oversight and responsibility for harm. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning dignity, inclusion, human oversight and responsibility for harm, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Ethics of AI · UNESCO Recommendation, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.unesco.org/en/artificial-intelligence/recommendation-ethics"
    },
    {
      "program_id": "gdi",
      "topic_id": "owasp-llm-top-10-2025",
      "relation": "context",
      "rationale": "The explorer topic concerns prompt injection, information disclosure and excessive agency in LLM applications. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning prompt injection, information disclosure and excessive agency in LLM applications, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for LLM application security risks · OWASP Top 10 (2025), with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "gdi",
      "topic_id": "mitre-atlas",
      "relation": "not_established",
      "rationale": "The explorer topic concerns documented adversary techniques and evidence for defenses. GDI currently specifies decision evidence and checks selected structural, routing and receipt-integrity properties. No specific subject-matched implementation or study is established for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "gdi",
      "topic_id": "nist-digital-identity-4",
      "relation": "context",
      "rationale": "The explorer topic concerns user identity proofing, authentication and federation in the guideline’s scope. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning user identity proofing, authentication and federation in the guideline’s scope, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Digital identity · NIST SP 800-63-4, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "gdi",
      "topic_id": "nist-generative-ai-profile",
      "relation": "context",
      "rationale": "The explorer topic concerns deployment-specific generative-AI risks and management actions. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning deployment-specific generative-AI risks and management actions, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Generative AI risk profile · NIST AI 600-1, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence"
    },
    {
      "program_id": "gdi",
      "topic_id": "iso-27001",
      "relation": "context",
      "rationale": "The explorer topic concerns confidentiality, integrity and availability of information and retained records. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning confidentiality, integrity and availability of information and retained records, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Information security management · ISO/IEC 27001:2022, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.iso.org/standard/27001"
    },
    {
      "program_id": "gdi",
      "topic_id": "roles-leadership",
      "relation": "direct",
      "rationale": "Its decision authority and obligation fields can identify who accepted a decision and who was recorded as responsible for an unresolved issue.",
      "investigation_question": "For a proposed GDI account concerning leadership ownership, risk acceptance and escalation beyond a system owner, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Leadership and accountable ownership, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Organizational responsibility must be examined in context; naming an owner is not evidence of effective oversight.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "roles-delivery",
      "relation": "direct",
      "rationale": "A reconstructable decision account needs to distinguish the evidence provider, system operator and party able to change a component.",
      "investigation_question": "For a proposed GDI account concerning responsibilities and change authority across developers, suppliers and deployers, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Developers, suppliers and deployers, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. These are descriptive delivery roles. Any legal meaning or duty must be checked against the applicable instrument.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "roles-domain-users",
      "relation": "direct",
      "rationale": "Its alternative and authority records can preserve a specialist’s input and remit, while not proving that the specialist understood or freely accepted it.",
      "investigation_question": "For a proposed GDI account concerning the information, expertise, time and discretion available to frontline specialists, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Domain specialists and frontline users, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. A credential or job title alone does not establish task competence, available time or freedom to disagree.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "gdi",
      "topic_id": "roles-reviewers",
      "relation": "direct",
      "rationale": "An inspectable GDR needs to identify the reviewer’s remit and available evidence so another assessor can challenge the account.",
      "investigation_question": "For a proposed GDI account concerning reviewer remit, access, competence and independence, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Reviewers and independent assessors, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Independence, access and competence are separate matters; none follows automatically from an assessment label.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "roles-affected-people",
      "relation": "direct",
      "rationale": "GDI’s inspectable explanation can provide material for a challenge, while a valid record cannot establish that an affected person had access or an effective appeal.",
      "investigation_question": "For a proposed GDI account concerning routes by which affected people can challenge an account and obtain a response, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Affected people and routes to challenge, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. A feedback channel is not necessarily an appeal process or an effective remedy. Rights and duties vary by context.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "roles-intervention",
      "relation": "direct",
      "rationale": "Recording who could change the action and what obligations followed an intervention is part of the authority-and-obligation reconstruction problem.",
      "investigation_question": "For a proposed GDI account concerning powers to pause, override, investigate, hear an appeal and authorize repair, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Authority to intervene and repair, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Formal authority, usable access and an effect on the action are separate questions. A research link does not establish legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "controls-inventory",
      "relation": "direct",
      "rationale": "A decision record’s evidence and authority need to refer to the actual model, application, intended use and version under examination.",
      "investigation_question": "For a proposed GDI account concerning identification of the version, intended use, owner and changes under examination, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Inventories and change records, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. An inventory describes the stated estate; its completeness and accuracy still need examination.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "controls-data",
      "relation": "direct",
      "rationale": "Retaining and protecting required decision evidence is necessary for GDI’s proposed reconstruction task, although no retention or access regime is certified.",
      "investigation_question": "For a proposed GDI account concerning authorized access, retention and examination of decision records, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Data handling and retained records, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Retention and access depend on context and applicable duties. More data is not automatically better evidence.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "gdi",
      "topic_id": "controls-access",
      "relation": "direct",
      "rationale": "GDI can record the identity and permission asserted for an action; its receipt demonstration does not enforce revocation or prove the permission was legitimate.",
      "investigation_question": "For a proposed GDI account concerning the identity and delegated permission behind an action and its withdrawal, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Identity, permissions and delegation, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. NIST digital identity guidance has a stated user and government-system scope; it is not a complete specification for agent identity or delegation. The related revocation study’s initial qualification uses scripted workers and a local database; autonomous-agent effectiveness remains unestablished.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "gdi",
      "topic_id": "controls-intervention",
      "relation": "context",
      "rationale": "The explorer topic concerns stopping, containment, recovery and irreversible effects. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning stopping, containment, recovery and irreversible effects, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Stopping, containment and recovery, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Some actions cannot be reversed. A stop control, a recovery process and correction of harm require different evidence.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "controls-monitoring",
      "relation": "direct",
      "rationale": "Exceptions and follow-up records can be connected to the original decision and recorded obligation, preserving the distinction between a warning and a response.",
      "investigation_question": "For a proposed GDI account concerning the chain from a warning or complaint to assigned action and follow-up, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Logs, incidents and follow-up, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. A recorded warning is not evidence that anyone understood it or that a corrective action worked.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "controls-boundaries",
      "relation": "direct",
      "rationale": "An action record needs to specify what was permitted and which dependencies or side effects it cannot observe; documentation does not establish enforcement.",
      "investigation_question": "For a proposed GDI account concerning permitted tool actions and dependencies outside the application, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Supplier and agent action boundaries, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. A documented boundary does not establish enforcement. Test the relevant configuration and retain limits on external visibility.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "gdi",
      "topic_id": "evaluation-model",
      "relation": "context",
      "rationale": "The explorer topic concerns model tasks, scores, failures and limits of a capability result. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning model tasks, scores, failures and limits of a capability result, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Model capabilities and limitations, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. A model benchmark does not by itself establish the performance or safety of an application using that model.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "evaluation-application",
      "relation": "direct",
      "rationale": "Its supplied fixtures test a defined record contract and routing behavior, so the application setting and intended reconstruction benefit require a separately matched study.",
      "investigation_question": "For a proposed GDI account concerning testing in the application’s intended task and operating conditions, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Application and mission-specific tests, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Performance under a stated test condition does not establish performance in every population, environment or later version.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "evaluation-control",
      "relation": "context",
      "rationale": "The explorer topic concerns whether a requested intervention changed the governed action. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning whether a requested intervention changed the governed action, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Tests of intervention and authority, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. A scripted control demonstration, a documentary reconstruction and an observed human intervention support different conclusions. The related revocation study’s initial qualification uses scripted workers and a local database; autonomous-agent effectiveness remains unestablished.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "evaluation-adversarial",
      "relation": "context",
      "rationale": "The explorer topic concerns controlled attack or failure paths and responses at a tested boundary. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning controlled attack or failure paths and responses at a tested boundary, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Adversarial tests and failure injection, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Passing selected scenarios does not establish complete security. Testing authority and limits must be agreed for the setting.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "gdi",
      "topic_id": "evaluation-human-factors",
      "relation": "context",
      "rationale": "The explorer topic concerns workload, information, incentives and opportunities for human challenge. This can help specify information an assessor might want in a decision account. GDI’s generic record and fixture checks have not implemented or validated this particular governance requirement.",
      "investigation_question": "For a proposed GDI account concerning workload, information, incentives and opportunities for human challenge, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Human judgment and working conditions, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Records can describe conditions; measuring behavior requires an appropriate study. Subjective workload does not establish effective oversight.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "gdi",
      "topic_id": "evaluation-reproducibility",
      "relation": "direct",
      "rationale": "The schema, classifier and receipt checks depend on exact fixtures and versions; the account distinguishes retained local checks from upstream technical results.",
      "investigation_question": "For a proposed GDI account concerning retained inputs, versions, scoring rules, procedures and results, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Reproducibility and retained test artifacts, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Repeatability does not establish that the chosen measure answers the intended question or generalizes to field use.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "evaluation-regression",
      "relation": "direct",
      "rationale": "Changes to required fields, routing rules, canonicalization or signature verification require rechecking the properties actually claimed for those records.",
      "investigation_question": "For a proposed GDI account concerning which findings require rechecking after a configuration or operating change, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Rechecking after changes, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. A previous result belongs to its tested configuration and conditions; it should not silently transfer to an updated system.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "gdi",
      "topic_id": "evidence-claims",
      "relation": "direct",
      "rationale": "The specification and checks make explicit which structural, routing or integrity property is claimed, without treating it as factual or institutional validity.",
      "investigation_question": "For a proposed GDI account concerning the conclusion, assessment criteria and scope offered to a reader, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Claims, criteria and scope, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. A criterion may come from law, a standard, a contract or a research method. Identify its source rather than treating them as interchangeable.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "gdi",
      "topic_id": "evidence-provenance",
      "relation": "direct",
      "rationale": "GDI connects evidence to its source and transformation; a signature or hash can support integrity examination while leaving source truth unresolved.",
      "investigation_question": "For a proposed GDI account concerning record origin, transformation, gaps and uncertain attribution, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Sources, provenance and missing records, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. A traceable record can still be incomplete or wrong. Provenance supports examination without establishing truth on its own.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.w3.org/TR/prov-dm/"
    },
    {
      "program_id": "gdi",
      "topic_id": "evidence-reconstruction",
      "relation": "direct",
      "rationale": "A GDR’s purpose is to connect evidence, alternatives, authority and obligations into an account of a decision that another reader can reconstruct.",
      "investigation_question": "For a proposed GDI account concerning the chronology of a decision, intervention and subsequent events, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Reconstructing the decision and intervention, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. A missing record is not automatically evidence of failure; an event occurring later does not by itself establish causation.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "gdi",
      "topic_id": "evidence-uncertainty",
      "relation": "direct",
      "rationale": "A signed or schema-valid record may still be incomplete, contradictory or wrong; missing support must remain visible to an assessor.",
      "investigation_question": "For a proposed GDI account concerning conflicting evidence, alternative explanations and unresolved findings, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Conflicting evidence and unresolved findings, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Unresolved means the available evidence does not settle the question. It should not silently become either approval or a finding of failure.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "gdi",
      "topic_id": "evidence-review",
      "relation": "direct",
      "rationale": "GDI’s inspectable account provides the sources and reasoning another person would need to challenge, while not implying independent validation.",
      "investigation_question": "For a proposed GDI account concerning a reader’s ability to trace and challenge the reasoning and sources, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Review, challenge and communication, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. Public availability does not establish independent validation. Access restrictions and the assessor’s remit should remain clear.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "gdi",
      "topic_id": "evidence-correction",
      "relation": "direct",
      "rationale": "A correction should retain what changed, who authorized it and which downstream effect remains unverified, rather than replacing the historical account.",
      "investigation_question": "For a proposed GDI account concerning the authorized correction and evidence of whether it reached its intended recipient, which evidence, decision factors, authority and obligations would an independent reader need to reconstruct or challenge the account?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Correction records and evidence of effects, with its actor, intended use and stated limits.",
        "The actual decision factors and source evidence, considered alternatives, recorded authority and obligation owners.",
        "The versioned GDR and relevant integrity or reconstruction checks, with missing or contradictory information retained."
      ],
      "limit": "Methodological relevance only. A schema-valid, signed or interoperable record does not prove factual truth, legitimate authority, lawful action, reviewer understanding or effective human control. An assurance finding does not itself authorize a correction. Responsibility stays with the people or institutions empowered to act.",
      "program_evidence_url": "https://github.com/node-and-norm/governed-decision-intelligence/blob/6915e5ab06d8346dd9ee359236430b273496dff1/RESEARCH.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-consumer",
      "relation": "not_established",
      "rationale": "The explorer topic concerns claims made to customers about system behavior. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Coverage depends on the conduct, entity and statutory jurisdiction; an AI label does not decide the legal analysis.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.ftc.gov/legal-library/browse/statutes/federal-trade-commission-act"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-equality",
      "relation": "not_established",
      "rationale": "The explorer topic concerns accessible challenge to technology-assisted employment decisions. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Different statutes cover different employers, people and decisions. The listed resources do not determine whether a particular decision was discriminatory.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.eeoc.gov/fact-sheet/federal-laws-prohibiting-job-discrimination-questions-and-answers"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-credit",
      "relation": "not_established",
      "rationale": "The explorer topic concerns principal reasons for an adverse credit decision. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Notice requirements vary with the transaction and applicant. This topic describes selected credit rules, not all financial-services obligations.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.consumerfinance.gov/compliance/compliance-resources/other-applicable-requirements/equal-credit-opportunity-act/"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-medical",
      "relation": "context",
      "rationale": "The explorer record concerns FDA device-software guidance, while RGDS’s public design origin concerns IND preparation. This supplies cross-domain gate-design context only; it does not map device guidance to IND submission requirements.",
      "investigation_question": "For a proposed gate concerning device-function classification, intended use and device evidence, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Medical-device software, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Whether software is a medical device depends on its function and intended use. The AI lifecycle draft is not a binding rule or a completed approval of any product.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.fda.gov/regulatory-information/search-fda-guidance-documents/policy-device-software-functions-and-mobile-medical-applications"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-california",
      "relation": "not_established",
      "rationale": "The explorer topic concerns covered personal data, automated decisions and consumer requests. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Coverage, exceptions and compliance schedules differ across provisions. These rules do not apply identically to every business or every use of AI.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.cppa.ca.gov/regulations/"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-california-employment",
      "relation": "not_established",
      "rationale": "The explorer topic concerns retained employment-decision records and discriminatory effects. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. This entry concerns the 2025 employment regulations, not the separate CCPA automated-decision rules or all subsequently enacted employment AI laws. Covered entities and particular records require a scoped assessment.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://calcivilrights.ca.gov/2025/06/30/civil-rights-council-secures-approval-for-regulations-to-protect-against-employment-discrimination-related-to-artificial-intelligence/"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-california-frontier",
      "relation": "not_established",
      "rationale": "The explorer topic concerns catastrophic-risk frameworks, mitigations and reported concerns. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Frontier models, large frontier developers, catastrophic risks and covered employees are defined categories. Publishing a framework does not establish that a model is safe for every application.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://oag.ca.gov/sb53"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-california-companions",
      "relation": "not_established",
      "rationale": "The explorer topic concerns companion disclosure, crisis protocols and protections for minors. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. The definition and qualified business-use, game and voice-assistant exclusions determine coverage. Current three-hour reminders concern known minors during continuing interactions. These provisions do not create a universal human-review or override right. SB1119 changes the known-minor provisions and adds requirements with separate operative dates; the current and forthcoming regimes must be read separately.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=202520260SB243"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-colorado",
      "relation": "not_established",
      "rationale": "The explorer topic concerns data correction and reconsideration of consequential decisions. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Definitions, exemptions, implementing rules and the timing of individual duties matter. The 2024 law alone is not a current account of this framework.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/sb26-189"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-colorado-health-review",
      "relation": "context",
      "rationale": "The explorer topic concerns qualified review before a medical-necessity denial is issued. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning qualified review before a medical-necessity denial is issued, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Colorado: AI-assisted health-care review, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. This entry covers selected utilization-review provisions in the enacted text, not the broader introduced bill. Relevant entity definitions and coverage terms matter. The research question is an editorial connection to practical human control, not a claim that TAE, HIT or CEC establishes compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1139"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-colorado-psychotherapy",
      "relation": "not_established",
      "rationale": "The explorer topic concerns real-time professional participation and withdrawal of recording consent. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. The recording and transcription consent rule is specific to those uses. Educational, research, wellness and certain FDA-authorized uses have defined conditions or exceptions. The enacted text also restricts misleading claims about professional equivalence and therapist-like confidentiality.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1195"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-colorado-conversational-ai",
      "relation": "not_established",
      "rationale": "The explorer topic concerns interaction-level disclosures, crisis escalation and protections for minors. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Coverage depends on statutory definitions and exclusions, including specified enterprise, research, transactional, health-care and educational uses. The age-estimation wording precedes the January 2027 clause; the later date should not be applied to every duty. Proposed implementing rules require a separate status check.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://leg.colorado.gov/bills/HB26-1263"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-connecticut-employment",
      "relation": "not_established",
      "rationale": "The explorer topic concerns employment notices, the system’s role and responses to bias-test findings. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Employment decisions, developers, deployers and substantial influence are defined terms with exclusions. These sections do not create a general right to override every automated decision. The act’s effective date must be distinguished from the later start of specified duties.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.cga.ct.gov/2026/ACT/PA/PDF/2026PA-00015-R00SB-00005-PA.PDF"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-illinois-employment",
      "relation": "not_established",
      "rationale": "The explorer topic concerns AI-related discrimination, protected-class proxies and employment notice. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Coverage follows the Human Rights Act and specified employment activities. Notice implementation is subject to agency rulemaking. This statute does not create a universal human-review or override requirement.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://ilga.gov/legislation/PublicActs/View/103-0804"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-illinois-psychological",
      "relation": "context",
      "rationale": "The explorer topic concerns professional responsibility and approval for permitted AI support. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning professional responsibility and approval for permitted AI support, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Illinois: AI support in psychological services, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. The act defines covered services and professionals. Additional restrictions concern emotion or mental-state detection and consent for recording or transcription used in supplementary support; this is not a blanket rule for all health software.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://ilga.gov/Legislation/PublicActs/View/104-0054"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-illinois-video",
      "relation": "not_established",
      "rationale": "The explorer topic concerns video-interview consent, sharing, deletion and demographic reporting. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. The act concerns AI analysis of applicant-submitted videos for Illinois-based positions. Sole reliance on AI for in-person interview selection triggers reporting; the act does not categorically prohibit that reliance.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://my.ilga.gov/Legislation/ILCS/Articles?ActID=4015&Chapter=EMPLOYMENT&ChapterID=68&MajorTopic=BUSINESS+AND+EMPLOYMENT"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-illinois-biometric",
      "relation": "not_established",
      "rationale": "The explorer topic concerns biometric collection, consent, disclosure and destruction. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Statutory definitions and exclusions determine coverage; not all images, identity data or AI uses are covered biometrics. This is a biometric-privacy law, not a general AI-governance act.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.ilga.gov/legislation/ilcs/fulltext?DocName=074000140K15"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-illinois-frontier",
      "relation": "not_established",
      "rationale": "The explorer topic concerns independent audit access to a frontier developer’s framework evidence. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Model and developer thresholds limit coverage. The act’s general effective date differs from the start of framework and audit duties; it should not be presented as an audit obligation already in force.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.ilga.gov/documents/legislation/PublicActs/104/104-0538.htm"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-minnesota-profiling",
      "relation": "not_established",
      "rationale": "The explorer topic concerns data correction, reevaluation and the effect on a profiling outcome. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. The act’s coverage thresholds, exclusions and consumer definition apply. These rights do not apply identically to every employment or service decision merely because profiling is involved.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.ag.state.mn.us/Data-Privacy/Consumer/"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-new-york-government",
      "relation": "not_established",
      "rationale": "The explorer topic concerns accuracy of a state-agency AI inventory and its disclosures. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. This entry concerns state agencies, not a general private-sector mandate. The 2025 amendment replaced the earlier impact-assessment and meaningful-human-review provisions; those removed provisions should not be treated as current duties.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/STT/103-E"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-new-york-raise",
      "relation": "not_established",
      "rationale": "The explorer topic concerns frontier safeguards, deployment decisions and critical-incident reporting. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Coverage depends on the statutory model and developer definitions and the New York connection. Academic-research and other specified exceptions apply. Publication alone does not establish effective control.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/bills/2025/S8828"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-new-york-companions",
      "relation": "not_established",
      "rationale": "The explorer topic concerns nonhuman disclosure, crisis referrals and separately scoped minor safeguards. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Coverage concerns defined companions for personal use in New York, with exclusions for specified customer-service, research, technical-assistance and internal-business systems. Article 47 does not require a staffed human handoff or guarantee detection. Separate Safe by Design provisions (§1540(7)) require age assurance before covered users can access integrated companions on covered platforms, and disable access by default for covered minors, subject to parental override, from 1 January 2027. S9051B was signed on 28 October 2026 as chapter 368, adding separate safeguards for minors. Its published text preserves Article 47. The start date of the new safeguards remains under review because the legislative text and official signing announcement differ.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.nysenate.gov/legislation/laws/GBS/1700"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-texas",
      "relation": "not_established",
      "rationale": "The explorer topic concerns actor-specific disclosures, prohibited uses and statutory sandbox conditions. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Requirements depend on the actor and use. The discrimination prohibition has an intent requirement; disparate impact alone does not establish that intent. A research sandbox is not automatically a participant in the statutory program.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://capitol.texas.gov/billlookup/BillSummary.aspx?Bill=HB149&LegSess=89R"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-utah-chatbots",
      "relation": "not_established",
      "rationale": "The explorer topic concerns mental-health-chatbot disclosure points and information practices. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. This entry covers the mental-health-chatbot provisions, not every Utah AI law. The defined chatbot, supplier and Utah-user scope matters. A disclosure does not establish clinical effectiveness or confer professional licensure.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://le.utah.gov/xcode/Title13/Chapter72A/C13-72a-P2_2025050720250507.pdf"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-virginia-profiling",
      "relation": "not_established",
      "rationale": "The explorer topic concerns profiling opt-outs and appeals of refused privacy requests. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. An appeal of a refused privacy request is not a universal appeal of the underlying automated decision. Coverage thresholds, entity and data exclusions, and the consumer definition must be examined.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://law.lis.virginia.gov/vacode/title59.1/chapter53/section59.1-577/"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-wisconsin-political",
      "relation": "not_established",
      "rationale": "The explorer topic concerns synthetic-media disclosures in specified political communications. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. This is a targeted political-communications law, not a comprehensive enterprise AI framework. The medium, content and statutory definitions determine the disclosure required.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://content.govdelivery.com/accounts/WIGOV/bulletins/391af46"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-wisconsin-insurance",
      "relation": "context",
      "rationale": "The explorer topic concerns insurer AI-program evidence, testing and vendor oversight. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning insurer AI-program evidence, testing and vendor oversight, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Wisconsin: insurance AI governance guidance, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. The bulletin explains regulatory expectations under existing insurance laws and permits alternative ways to demonstrate compliance. It is guidance, not a new AI statute or a requirement for one prescribed documentation format.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://oci.wi.gov/Pages/Regulation/Bulletin20250318AI.aspx"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-us-new-york-city-aedt",
      "relation": "not_established",
      "rationale": "The explorer topic concerns employment-tool bias-audit scope, independence and notice. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. This is a New York City requirement for defined hiring and promotion tools, not a statewide rule or a general certification that an AI system is fair. The city rules and definitions determine coverage.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.nyc.gov/site/dca/about/automated-employment-decision-tools.page"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-eu-prohibited",
      "relation": "context",
      "rationale": "The explorer topic concerns classification of a proposed use against specified prohibited practices. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning classification of a proposed use against specified prohibited practices, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Prohibited AI practices, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Consult the current article and relevant exceptions. A general risk score or a successful test cannot authorize a prohibited use.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-5"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-eu-high-risk",
      "relation": "context",
      "rationale": "The explorer topic concerns use classification and high-risk documentation and control requirements. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning use classification and high-risk documentation and control requirements, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for High-risk systems and requirements, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Not every consequential use of AI is automatically classified as high-risk. Article 6, the annexes, exceptions and applicable transition provisions require review.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-6"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-eu-human-oversight",
      "relation": "context",
      "rationale": "The explorer topic concerns usable reviewer authority and evidence of what intervention changed. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning usable reviewer authority and evidence of what intervention changed, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Human oversight, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. This is a scoped legal provision, not a universal requirement to put a person behind every AI output. Node & Norm’s research questions do not establish legal conformity.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:02024R1689-20260727"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-eu-transparency",
      "relation": "not_established",
      "rationale": "The explorer topic concerns whether information about AI interaction or generated content reaches its audience. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Not every AI use or piece of assisted content has the same disclosure duty. The type of interaction, content, actor and exception matters.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-50"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-eu-gpai",
      "relation": "context",
      "rationale": "The explorer topic concerns provider documentation and downstream model-capability and risk information. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning provider documentation and downstream model-capability and risk information, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for General-purpose AI models, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. General-purpose AI is a defined regulatory category; it does not mean artificial general intelligence. Provider roles, exemptions and systemic-risk classification require separate examination.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-53"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-eu-value-chain",
      "relation": "context",
      "rationale": "The explorer topic concerns responsibility for a version, intended use and changed supplier role. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning responsibility for a version, intended use and changed supplier role, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Responsibilities across the value chain, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. A supplier contract or an internal job title does not by itself settle the statutory role. Article 25 addresses specified value-chain circumstances.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://ai-act-service-desk.ec.europa.eu/en/ai-act/article-25"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-eu-gdpr",
      "relation": "context",
      "rationale": "The explorer topic concerns personal-data correction, information and conditional automated-decision rights. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning personal-data correction, information and conditional automated-decision rights, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Personal data and automated decisions, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Article 22 has defined conditions, exceptions and safeguards; it is not a general prohibition on all automated decisions. Other data-protection duties can apply even when Article 22 does not.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://commission.europa.eu/law/law-topic/data-protection/information-individuals_en"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-eu-nis2",
      "relation": "not_established",
      "rationale": "The explorer topic concerns covered organizations’ cybersecurity incident response and supply-chain security. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Coverage depends on sector, entity characteristics and national implementation. NIS2 is not an AI-specific assurance standard.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/nis2-directive"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-eu-cra",
      "relation": "not_established",
      "rationale": "The explorer topic concerns digital-product security, vulnerability handling and support-period evidence. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Product scope, exclusions, actor responsibilities and transition provisions matter. Inclusion here does not mean every AI service falls within the Act.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-kr-ai-basic",
      "relation": "not_established",
      "rationale": "The explorer topic concerns Korean use categories, transparency, safety and oversight arrangements. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the current Korean instruments and implementing guidance for an applicability decision. Terms such as high-impact should not be assumed equivalent to EU high-risk classifications.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.msit.go.kr/eng/bbs/view.do?bbsSeqNo=42&mId=4&mPid=2&nttSeqNo=1214&sCode=eng"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-cn-generative",
      "relation": "not_established",
      "rationale": "The explorer topic concerns public-facing Chinese generative services, data practices and complaint handling. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. The measures distinguish public-facing services from research and uses not offered to the domestic public. Other applicable Chinese laws and later measures require separate review.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.cac.gov.cn/2023-07/13/c_1690898327029107.htm"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-jp-ai-promotion",
      "relation": "not_established",
      "rationale": "The explorer topic concerns Japan’s governmental and stakeholder promotion-and-governance responsibilities. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. The law’s promotion-and-governance approach should not be presented as the same risk-classification regime used elsewhere. Existing laws and sector guidance remain relevant.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www8.cao.go.jp/cstp/ai/ai_act/ai_act.html"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-in-dpdp",
      "relation": "not_established",
      "rationale": "The explorer topic concerns covered digital-personal-data processing, organizational duties and individual rights. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. The law and rules have scope conditions, exemptions and phased provisions. Their existence does not establish that every duty applies to every AI activity.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.pib.gov.in/PressReleseDetailm.aspx?PRID=2190655&lang=2&reg=48"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-br-lgpd",
      "relation": "not_established",
      "rationale": "The explorer topic concerns information and contestability for covered automated personal-data decisions. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. The right to request review should not be relabeled as a universal guarantee of human review. Scope, exceptions and regulator guidance require examination.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.gov.br/anpd/pt-br/assuntos/titular-de-dados/direito-dos-titulares"
    },
    {
      "program_id": "rgds",
      "topic_id": "reg-institutional-commitments",
      "relation": "direct",
      "rationale": "RGDS models permission with unresolved conditions, named owners and closure evidence; a particular contract can supply an explicit condition to inspect.",
      "investigation_question": "For a proposed gate concerning purchasing commitments, supplier responsibilities and evidence of fulfillment, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Procurement, contracts and stated purposes, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. This topic concerns commitments to examine, rather than a single law. The terms of a particular agreement, applicable law and responsible parties determine its effect. A supplier assurance does not by itself establish that a control worked.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "iso-42001",
      "relation": "context",
      "rationale": "The explorer topic concerns organizational AI responsibilities, operation and management-system improvement. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning organizational AI responsibilities, operation and management-system improvement, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI management systems · ISO/IEC 42001:2023, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.iso.org/standard/42001"
    },
    {
      "program_id": "rgds",
      "topic_id": "iso-23894",
      "relation": "context",
      "rationale": "The explorer topic concerns identification, ownership and treatment of context-specific AI risks. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning identification, ownership and treatment of context-specific AI risks, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI risk management · ISO/IEC 23894:2023, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.iso.org/standard/77304.html"
    },
    {
      "program_id": "rgds",
      "topic_id": "iso-42005",
      "relation": "context",
      "rationale": "The explorer topic concerns documented impacts on affected people across a system lifecycle. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning documented impacts on affected people across a system lifecycle, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI impact assessment · ISO/IEC 42005:2025, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.iso.org/standard/42005"
    },
    {
      "program_id": "rgds",
      "topic_id": "iso-22989",
      "relation": "context",
      "rationale": "The explorer topic concerns shared terminology for the system, actors and activities. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning shared terminology for the system, actors and activities, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Shared AI terminology · ISO/IEC 22989:2022, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.iso.org/standard/74296.html"
    },
    {
      "program_id": "rgds",
      "topic_id": "nist-ai-rmf-1-0",
      "relation": "context",
      "rationale": "The explorer topic concerns connections between identified risks, evaluation findings and management decisions. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning connections between identified risks, evaluation findings and management decisions, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for AI Risk Management Framework · NIST AI RMF 1.0, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "rgds",
      "topic_id": "oecd-ai-principles",
      "relation": "context",
      "rationale": "The explorer topic concerns human rights, transparency and an accountable response to AI use. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning human rights, transparency and an accountable response to AI use, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Trustworthy AI principles · OECD, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://oecd.ai/en/ai-principles"
    },
    {
      "program_id": "rgds",
      "topic_id": "unesco-ai-ethics",
      "relation": "context",
      "rationale": "The explorer topic concerns dignity, inclusion, human oversight and responsibility for harm. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning dignity, inclusion, human oversight and responsibility for harm, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Ethics of AI · UNESCO Recommendation, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.unesco.org/en/artificial-intelligence/recommendation-ethics"
    },
    {
      "program_id": "rgds",
      "topic_id": "owasp-llm-top-10-2025",
      "relation": "not_established",
      "rationale": "The explorer topic concerns prompt injection, information disclosure and excessive agency in LLM applications. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "rgds",
      "topic_id": "mitre-atlas",
      "relation": "not_established",
      "rationale": "The explorer topic concerns documented adversary techniques and evidence for defenses. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "rgds",
      "topic_id": "nist-digital-identity-4",
      "relation": "not_established",
      "rationale": "The explorer topic concerns user identity proofing, authentication and federation in the guideline’s scope. RGDS currently supplies gate-decision records and validators for six illustrative scenarios. Its public scope does not establish a specific investigation or implementation for this subject.",
      "investigation_question": null,
      "evidence_needed": [],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "rgds",
      "topic_id": "nist-generative-ai-profile",
      "relation": "context",
      "rationale": "The explorer topic concerns deployment-specific generative-AI risks and management actions. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning deployment-specific generative-AI risks and management actions, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Generative AI risk profile · NIST AI 600-1, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.nist.gov/publications/artificial-intelligence-risk-management-framework-generative-artificial-intelligence"
    },
    {
      "program_id": "rgds",
      "topic_id": "iso-27001",
      "relation": "context",
      "rationale": "The explorer topic concerns confidentiality, integrity and availability of information and retained records. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning confidentiality, integrity and availability of information and retained records, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Information security management · ISO/IEC 27001:2022, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Use the published standard’s stated scope; this crosswalk does not claim conformance to its full requirements.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.iso.org/standard/27001"
    },
    {
      "program_id": "rgds",
      "topic_id": "roles-leadership",
      "relation": "direct",
      "rationale": "Its gate decision needs an accountable owner who can accept, defer or refuse a condition and assign follow-up beyond a team’s immediate authority.",
      "investigation_question": "For a proposed gate concerning leadership ownership, risk acceptance and escalation beyond a system owner, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Leadership and accountable ownership, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Organizational responsibility must be examined in context; naming an owner is not evidence of effective oversight.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "roles-delivery",
      "relation": "direct",
      "rationale": "Conditional permission depends on who supplies missing evidence and who can change the blocked dependency, including external parties.",
      "investigation_question": "For a proposed gate concerning responsibilities and change authority across developers, suppliers and deployers, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Developers, suppliers and deployers, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. These are descriptive delivery roles. Any legal meaning or duty must be checked against the applicable instrument.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "roles-domain-users",
      "relation": "direct",
      "rationale": "Source-informed design distinguishes a specialist’s evidence and judgment from the authority to proceed with a regulated preparation decision.",
      "investigation_question": "For a proposed gate concerning the information, expertise, time and discretion available to frontline specialists, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Domain specialists and frontline users, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. A credential or job title alone does not establish task competence, available time or freedom to disagree.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "rgds",
      "topic_id": "roles-reviewers",
      "relation": "direct",
      "rationale": "A reviewer needs the governing gate conditions and source evidence to assess why the record says go, no-go or defer.",
      "investigation_question": "For a proposed gate concerning reviewer remit, access, competence and independence, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Reviewers and independent assessors, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Independence, access and competence are separate matters; none follows automatically from an assessment label.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "roles-affected-people",
      "relation": "context",
      "rationale": "The explorer topic concerns routes by which affected people can challenge an account and obtain a response. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning routes by which affected people can challenge an account and obtain a response, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Affected people and routes to challenge, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. A feedback channel is not necessarily an appeal process or an effective remedy. Rights and duties vary by context.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "roles-intervention",
      "relation": "direct",
      "rationale": "The go/no-go/defer structure makes authority to pause a decision and authority to close its outstanding conditions explicit.",
      "investigation_question": "For a proposed gate concerning powers to pause, override, investigate, hear an appeal and authorize repair, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Authority to intervene and repair, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Formal authority, usable access and an effect on the action are separate questions. A research link does not establish legal compliance.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "controls-inventory",
      "relation": "direct",
      "rationale": "Gate outcomes refer to a particular decision and evidence state; a version change can invalidate a prior conditional approval.",
      "investigation_question": "For a proposed gate concerning identification of the version, intended use, owner and changes under examination, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Inventories and change records, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. An inventory describes the stated estate; its completeness and accuracy still need examination.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "controls-data",
      "relation": "direct",
      "rationale": "The method requires relevant evidence to remain retrievable for checking a condition’s closure, with access and retention scoped separately.",
      "investigation_question": "For a proposed gate concerning authorized access, retention and examination of decision records, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Data handling and retained records, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Retention and access depend on context and applicable duties. More data is not automatically better evidence.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "rgds",
      "topic_id": "controls-access",
      "relation": "context",
      "rationale": "The explorer topic concerns the identity and delegated permission behind an action and its withdrawal. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning the identity and delegated permission behind an action and its withdrawal, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Identity, permissions and delegation, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. NIST digital identity guidance has a stated user and government-system scope; it is not a complete specification for agent identity or delegation. The related revocation study’s initial qualification uses scripted workers and a local database; autonomous-agent effectiveness remains unestablished.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://csrc.nist.gov/pubs/sp/800/63/4/final"
    },
    {
      "program_id": "rgds",
      "topic_id": "controls-intervention",
      "relation": "direct",
      "rationale": "A no-go or defer record can specify a proposed stopping condition; the illustrative reference implementation does not prove execution was stopped.",
      "investigation_question": "For a proposed gate concerning stopping, containment, recovery and irreversible effects, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Stopping, containment and recovery, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Some actions cannot be reversed. A stop control, a recovery process and correction of harm require different evidence.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "controls-monitoring",
      "relation": "direct",
      "rationale": "A condition has to remain assigned and followed through until closure evidence is reviewed; issuing approval alone does not finish that obligation.",
      "investigation_question": "For a proposed gate concerning the chain from a warning or complaint to assigned action and follow-up, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Logs, incidents and follow-up, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. A recorded warning is not evidence that anyone understood it or that a corrective action worked.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "controls-boundaries",
      "relation": "direct",
      "rationale": "A conditional go needs a defined action scope and explicit limits on what unresolved evidence or supplier dependencies still prohibit.",
      "investigation_question": "For a proposed gate concerning permitted tool actions and dependencies outside the application, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Supplier and agent action boundaries, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. A documented boundary does not establish enforcement. Test the relevant configuration and retain limits on external visibility.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://genai.owasp.org/llm-top-10/"
    },
    {
      "program_id": "rgds",
      "topic_id": "evaluation-model",
      "relation": "context",
      "rationale": "The explorer topic concerns model tasks, scores, failures and limits of a capability result. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning model tasks, scores, failures and limits of a capability result, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Model capabilities and limitations, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. A model benchmark does not by itself establish the performance or safety of an application using that model.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "evaluation-application",
      "relation": "direct",
      "rationale": "Its six authored examples concern defined regulated preparation and gate scenarios; inspection should retain that setting rather than infer IND outcomes.",
      "investigation_question": "For a proposed gate concerning testing in the application’s intended task and operating conditions, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Application and mission-specific tests, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Performance under a stated test condition does not establish performance in every population, environment or later version.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "evaluation-control",
      "relation": "context",
      "rationale": "The explorer topic concerns whether a requested intervention changed the governed action. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning whether a requested intervention changed the governed action, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Tests of intervention and authority, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. A scripted control demonstration, a documentary reconstruction and an observed human intervention support different conclusions. The related revocation study’s initial qualification uses scripted workers and a local database; autonomous-agent effectiveness remains unestablished.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "evaluation-adversarial",
      "relation": "context",
      "rationale": "The explorer topic concerns controlled attack or failure paths and responses at a tested boundary. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning controlled attack or failure paths and responses at a tested boundary, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Adversarial tests and failure injection, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Passing selected scenarios does not establish complete security. Testing authority and limits must be agreed for the setting.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://atlas.mitre.org/"
    },
    {
      "program_id": "rgds",
      "topic_id": "evaluation-human-factors",
      "relation": "context",
      "rationale": "The explorer topic concerns workload, information, incentives and opportunities for human challenge. This can supply background for scoping a gate, a responsible owner or evidence required before proceeding. The six illustrative RGDS records do not implement or validate this instrument or control.",
      "investigation_question": "For a proposed gate concerning workload, information, incentives and opportunities for human challenge, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Human judgment and working conditions, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Records can describe conditions; measuring behavior requires an appropriate study. Subjective workload does not establish effective oversight.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf"
    },
    {
      "program_id": "rgds",
      "topic_id": "evaluation-reproducibility",
      "relation": "direct",
      "rationale": "The two validator entry points and v2.0.1 date-format correction make the exact contract, validators and canonical examples necessary for reproduction.",
      "investigation_question": "For a proposed gate concerning retained inputs, versions, scoring rules, procedures and results, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Reproducibility and retained test artifacts, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Repeatability does not establish that the chosen measure answers the intended question or generalizes to field use.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "evaluation-regression",
      "relation": "direct",
      "rationale": "The v2.0.1 validator correction shows why older accepted records require rechecking against the corrected semantic and date rules.",
      "investigation_question": "For a proposed gate concerning which findings require rechecking after a configuration or operating change, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Rechecking after changes, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. A previous result belongs to its tested configuration and conditions; it should not silently transfer to an updated system.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    },
    {
      "program_id": "rgds",
      "topic_id": "evidence-claims",
      "relation": "direct",
      "rationale": "RGDS separates structural acceptance of a conditional record from a substantive claim that the conditions justified proceeding.",
      "investigation_question": "For a proposed gate concerning the conclusion, assessment criteria and scope offered to a reader, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Claims, criteria and scope, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. A criterion may come from law, a standard, a contract or a research method. Identify its source rather than treating them as interchangeable.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "rgds",
      "topic_id": "evidence-provenance",
      "relation": "direct",
      "rationale": "A gate needs traceable sources for conflicting values and late reports so the record can justify which evidence supported the decision.",
      "investigation_question": "For a proposed gate concerning record origin, transformation, gaps and uncertain attribution, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Sources, provenance and missing records, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. A traceable record can still be incomplete or wrong. Provenance supports examination without establishing truth on its own.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.w3.org/TR/prov-dm/"
    },
    {
      "program_id": "rgds",
      "topic_id": "evidence-reconstruction",
      "relation": "direct",
      "rationale": "The decision record should let another reader reconstruct why the team proceeded, stopped or waited and what was still owed.",
      "investigation_question": "For a proposed gate concerning the chronology of a decision, intervention and subsequent events, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Reconstructing the decision and intervention, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. A missing record is not automatically evidence of failure; an event occurring later does not by itself establish causation.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://nodeandnorm.org/research/human-control/tae/"
    },
    {
      "program_id": "rgds",
      "topic_id": "evidence-uncertainty",
      "relation": "direct",
      "rationale": "Missing or conflicting material can support a defer/no-go or unresolved condition; it should not be silently converted into permission.",
      "investigation_question": "For a proposed gate concerning conflicting evidence, alternative explanations and unresolved findings, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Conflicting evidence and unresolved findings, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Unresolved means the available evidence does not settle the question. It should not silently become either approval or a finding of failure.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "rgds",
      "topic_id": "evidence-review",
      "relation": "direct",
      "rationale": "A reviewer must be able to trace the permission and each condition to its evidence and challenge whether closure was justified.",
      "investigation_question": "For a proposed gate concerning a reader’s ability to trace and challenge the reasoning and sources, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Review, challenge and communication, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. Public availability does not establish independent validation. Access restrictions and the assessor’s remit should remain clear.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://www.gov.uk/government/publications/introduction-to-ai-assurance/introduction-to-ai-assurance"
    },
    {
      "program_id": "rgds",
      "topic_id": "evidence-correction",
      "relation": "direct",
      "rationale": "Closure evidence and recorded ownership are central to distinguishing a completed follow-up action from satisfaction of the approval condition.",
      "investigation_question": "For a proposed gate concerning the authorized correction and evidence of whether it reached its intended recipient, what permits proceeding, what remains unresolved and which owner must provide evidence before the condition can be closed?",
      "evidence_needed": [
        "The versioned source and scoped criterion for Correction records and evidence of effects, with its actor, intended use and stated limits.",
        "The particular go/no-go/defer record, evidence state, permission scope and unresolved conditions.",
        "A named condition owner, the evidence offered for closure and the validator and contract version used."
      ],
      "limit": "Methodological relevance only. Authored examples and validator checks do not establish that permission was justified, that an action stopped, regulatory acceptance or deployed workflow effectiveness. An assurance finding does not itself authorize a correction. Responsibility stays with the people or institutions empowered to act.",
      "program_evidence_url": "https://github.com/node-and-norm/rgds/blob/a217a57490f357aa06c509abd821592370556a7d/README.md",
      "governance_source_url": "https://airc.nist.gov/airmf-resources/airmf/5-sec-core/"
    }
  ]
}
