ARCHETYPAL

Consult IT Services before using MSU credentials for AI products, including free tools.

AIR-242001C9D0 · version 2 · Governance · candidate interpretation

Users must consult IT Services.

Situation & purpose

An AI system or employee activity involves IT Services. Confirm the actor and source conditions before using this template.

Provide a traceable control for the action: consult IT Services.

Examples

Meets the rule
users performs the required action "consult" for IT Services within these source conditions: Within the source scope; assess applicability before adoption., and retains evidence.
Does not meet the rule
users omits the required action "consult" for IT Services while those source conditions apply.
Outside scope
The actor, activity, jurisdiction, or applicability conditions in this source variant do not match.

Evidence & enforcement

  • Dated record of the action
  • Responsible actor and approval, where required
  • Applicable source edition and scope

Human or authorized system adapter required. Machine-executable: no. Convert to a reviewed organization contract and validate the adapter before deployment.

Limits

A rule card is an interpretation aid, not an applicability determination.

Equivalent intent does not make different source obligations interchangeable.

Owner review

Record your interpretation decision. This does not adopt a policy for an organization.

Owner sign-in

JSON rule card
{
  "id": "AIR-242001C9D0",
  "version": 2,
  "title": "Consult IT Services before using MSU credentials for AI products, including free tools.",
  "text": "Users must consult IT Services.",
  "topic": "Governance",
  "intent": "consult it services",
  "status": "candidate",
  "semanticStatus": "human-validation-required",
  "variants": [
    {
      "sourceId": "msu-genai-guidelines",
      "control": "Procuring or Registering, paragraph 2",
      "sourceVersion": "Approved August 12, 2025; no revisions listed",
      "url": "https://ai.msu.edu/guidelines",
      "actor": "users",
      "modality": "must",
      "action": "consult",
      "object": "IT Services",
      "condition": "Within the source scope; assess applicability before adoption.",
      "exception": null,
      "timing": null,
      "authority": "organization-specific",
      "jurisdiction": "Michigan State University, US",
      "checkedAt": "2026-09-28",
      "status": "interpretation-needs-review",
      "examples": {
        "meetsRule": "users performs the required action \"consult\" for IT Services within these source conditions: Within the source scope; assess applicability before adoption., and retains evidence.",
        "doesNotMeetRule": "users omits the required action \"consult\" for IT Services while those source conditions apply.",
        "outOfScope": "The actor, activity, jurisdiction, or applicability conditions in this source variant do not match."
      }
    }
  ],
  "situation": "An AI system or employee activity involves IT Services. Confirm the actor and source conditions before using this template.",
  "purpose": "Provide a traceable control for the action: consult IT Services.",
  "examples": {
    "meetsRule": "users performs the required action \"consult\" for IT Services within these source conditions: Within the source scope; assess applicability before adoption., and retains evidence.",
    "doesNotMeetRule": "users omits the required action \"consult\" for IT Services while those source conditions apply.",
    "outOfScope": "The actor, activity, jurisdiction, or applicability conditions in this source variant do not match."
  },
  "evidence": [
    "Dated record of the action",
    "Responsible actor and approval, where required",
    "Applicable source edition and scope"
  ],
  "enforcement": {
    "mode": "policy-template",
    "adapter": "Human or authorized system adapter required",
    "machineExecutable": false
  },
  "limitations": [
    "A rule card is an interpretation aid, not an applicability determination.",
    "Equivalent intent does not make different source obligations interchangeable."
  ],
  "createdAt": "2026-10-03",
  "updatedAt": "2026-10-03"
}
Back to registry