{
  "code": "AI-01",
  "slug": "synthetic-source-disclosure-and-authority",
  "title": "Synthetic Source Disclosure and Authority",
  "category": "Synthetic Sources",
  "status": "Current",
  "version": "2.0.4-wip",
  "summary": "Synthetic characters and generated dialogue are visibly disclosed and cannot create authoritative game facts, inventory, permissions, or settlement.",
  "keywords": [
    "AI",
    "synthetic source",
    "disclosure",
    "server authority",
    "memory",
    "generated dialogue"
  ],
  "mission_phases": [
    "Access",
    "Collect",
    "Validate",
    "Deliver"
  ],
  "canonical": "https://iarpg.com/standard/synthetic-source-disclosure-and-authority",
  "json": "https://iarpg.com/records/synthetic-source-disclosure-and-authority.json",
  "requirements": [
    {
      "level": "MUST",
      "text": "Disclose synthetic characters and generated responses in the interaction surface."
    },
    {
      "level": "MUST",
      "text": "Keep mission facts, inventory, access, rewards, legal status, and world state server-authoritative."
    },
    {
      "level": "MUST",
      "text": "Treat synthetic output as a report or claim unless validated against authoritative state."
    },
    {
      "level": "SHOULD",
      "text": "Store only reviewed, scoped continuity in durable character memory."
    },
    {
      "level": "MAY",
      "text": "Synthetic sources intentionally mislead when the mission clearly supports verification and fail-forward outcomes."
    }
  ],
  "research": [
    {
      "label": "Controlled generative architecture",
      "href": "/docs/report/systemic-implementation-of-delusional-ai-and-hallucinated-mission-vectors-in-virtual-reality-mmorpgs#generative-architectures-for-delusional-npcs",
      "note": "Separate mechanical truth from narrative generation."
    },
    {
      "label": "Mitigation strategies and design guidelines",
      "href": "/docs/report/hallucinated-ai-quest-design-in-vr-mmorpgs#mitigation-strategies-and-design-guidelines",
      "note": "Reliability signaling, player agency, and bounded falsehoods."
    }
  ],
  "related": [
    "mission-claim-verification",
    "provenance-confidence-and-corroboration",
    "safety-and-fiction-boundary"
  ],
  "release": "IARPG-OPS-2",
  "revised_utc": "2026-07-20T12:04:07Z",
  "purpose": "Bound generated dialogue and unreliable synthetic claims so language generation cannot silently control authoritative game truth.",
  "rationale": "Players must be able to distinguish a synthetic claim from a verified location, object, reward, warrant, or mission outcome.",
  "game_interaction": [
    "Inspect source disclosure",
    "Verify claim packet",
    "Compare reliability history",
    "Accept, defer, or reject claim"
  ],
  "inputs": [
    "Synthetic statement",
    "Server claim packet",
    "Source history"
  ],
  "outputs": [
    "Verified claim",
    "Contradiction",
    "Deferred tasking",
    "Reliability update"
  ],
  "state_transitions": [
    {
      "from": "not-applicable",
      "event": "record requirement evaluated",
      "to": "conforming-or-documented-exception"
    }
  ],
  "evidence_and_provenance": [
    "The implementation records the source, UTC event time, mission identifier, responsible role, and reason code for consequential state changes.",
    "Generated dialogue and player interpretation are not stored as authoritative facts without a separate verification event."
  ],
  "ui_requirements": [
    "Show the record code and requirement level at the point of use.",
    "Expose the reason for blocked, failed, escalated, or irreversible actions.",
    "Provide a direct link to the canonical standard and machine-readable record."
  ],
  "accessibility_requirements": [
    "Essential information is available without reliance on color, audio, motion, or a VR-only gesture.",
    "Keyboard, screen-reader, reduced-motion, seated-play, and high-contrast equivalents are documented where the interaction applies."
  ],
  "telemetry_events": [
    {
      "name": "standard.synthetic-source-disclosure-and-authority.evaluated",
      "required_fields": [
        "event_id",
        "timestamp_utc",
        "mission_id",
        "record_code",
        "result",
        "reason_code"
      ]
    }
  ],
  "abuse_and_exploit_cases": [
    "A participant attempts to omit required context so another role accepts a misleading task.",
    "A generated or user-authored statement is presented as server-authoritative without verification.",
    "A consequential state transition occurs without a durable reason code."
  ],
  "failure_behavior": "Fail closed for irreversible or settlement-bearing actions. Preserve the current state, show the missing requirement, and allow correction or documented exception review.",
  "recovery_behavior": "Restore from the last authoritative event, retain the rejected transition in the audit log, and require a new validated event before continuing.",
  "example_implementation": "A mission interface evaluates AI-01 before advancing the relevant state and writes the result to the local event log with a UTC timestamp and reason code.",
  "roles": [
    "Operative",
    "Handler",
    "Intelligence Analyst"
  ],
  "authority_types": [
    "Civil administration",
    "Military command",
    "Commercial intelligence service",
    "International verification body",
    "Scientific consortium",
    "Independent investigative network"
  ],
  "collection_disciplines": [],
  "interaction_types": [
    "Inspect source disclosure",
    "Verify claim packet",
    "Compare reliability history"
  ],
  "evidence_requirement": "Reviewable provenance required",
  "conformance_level": "Level B — Playable",
  "implementation_maturity": "Published WIP",
  "related_examples": [
    "port-access-anomaly-investigation"
  ],
  "revision_history": [
    {
      "version": "1.0.0",
      "date_utc": "2026-07-19",
      "note": "Initial IARPG-OPS-1 publication."
    },
    {
      "version": "2.0.1-wip",
      "date_utc": "2026-07-19",
      "note": "Expanded for IARPG-OPS-2 workbench, simulation, evidence, accessibility, telemetry, and machine-readable publication."
    },
    {
      "version": "2.0.2-wip",
      "date_utc": "2026-07-19T16:42:07Z",
      "change": "Reviewed for operation-package lifecycle compatibility and local tool integration."
    },
    {
      "version": "2.0.3-wip",
      "date_utc": "2026-07-19T18:45:50Z",
      "note": "Reviewed for integrity-aware package verification, merge, multi-role replay, custody comparison, batch review, backup, publication preview, and release-promotion workflows."
    },
    {
      "version": "2.0.4-wip",
      "date_utc": "2026-07-20T12:04:07Z",
      "note": "Reviewed for canonicalization, round-trip portability, recovery, provenance, compatibility, accessibility, hosting evidence, and stable-promotion gates."
    }
  ]
}