{
  "schema_version": "1.2",
  "source_register": [
    {
      "id": "src-intake",
      "title": "Intake and supplied-records list",
      "version": "Intake baseline",
      "calendar_date": null,
      "approval_status": "Sponsor scope acknowledgment is illustrated; no institutional authorization is recorded.",
      "review_state": "Read in this illustration",
      "content": "Two declared uses are in scope: staff drafting from procedure text and an embedded vendor feature under consideration. No customer or account data is supplied.",
      "limitation": "The list is the supplied starting point, not a complete technology census."
    },
    {
      "id": "src-staff",
      "title": "Staff-use disclosure",
      "version": "Initial disclosure",
      "calendar_date": null,
      "approval_status": "No authorization to send confidential material is supplied.",
      "review_state": "Read in this illustration",
      "content": "Staff report using a public assistant to draft procedure explanations. The assistant runs outside the institution. Staff do not declare which procedure version was used or all text entered.",
      "limitation": "Self-report is incomplete and does not establish data exclusion or full usage coverage."
    },
    {
      "id": "src-procedure-earlier",
      "title": "Earlier controlled procedure",
      "version": "Revision 1",
      "calendar_date": null,
      "approval_status": "A supplied approval record marks this version approved through the institution's procedure-control route. The approver name and calendar date are blank.",
      "review_state": "Excerpt compared in this illustration",
      "content": "A second reviewer must approve an exception before staff act. If an instruction conflicts with the controlled procedure, pause and refer the question to the procedure owner.",
      "limitation": "This excerpt alone does not establish that the full procedure is complete, current or acceptable."
    },
    {
      "id": "src-procedure-later",
      "title": "Later working procedure copy",
      "version": "Revision 2 working copy",
      "calendar_date": null,
      "approval_status": "No approval record or supersession notice is supplied.",
      "review_state": "Excerpt compared in this illustration",
      "content": "Staff may act on a routine exception and notify the second reviewer afterward. The working copy does not say when an exception stops being routine.",
      "limitation": "The higher revision number does not make this working copy the controlling version."
    },
    {
      "id": "src-vendor-proposal",
      "title": "Embedded-feature proposal",
      "version": "Proposal baseline",
      "calendar_date": null,
      "approval_status": "No feature activation approval is supplied.",
      "review_state": "Read in this illustration",
      "content": "The existing platform may include an AI-assisted summary feature. The proposal describes summaries but does not state whether the feature is on by default, which fields it reads, what is retained, or how the institution disables it.",
      "limitation": "A proposal reference is evidence of a claim, not evidence of actual configuration or accepted controls."
    },
    {
      "id": "src-vendor-disclosure",
      "title": "Vendor feature disclosure",
      "version": "Initial disclosure",
      "calendar_date": null,
      "approval_status": "No institutional acceptance is supplied.",
      "review_state": "Read in this illustration",
      "content": "The disclosure refers to service-event metadata and an administrator setting. It does not describe free-text fields, downstream processing, retention, or the effect of switching the setting off.",
      "limitation": "The disclosure leaves data reach and effective disablement unanswered."
    },
    {
      "id": "src-change",
      "title": "Changed vendor feature disclosure",
      "version": "Revised disclosure",
      "calendar_date": null,
      "approval_status": "No institutional acceptance or activation approval is supplied.",
      "review_state": "Read and compared in the follow-up illustration",
      "content": "The revised disclosure says the feature is enabled unless the institution disables it and may read free-text service notes in addition to event metadata. No configuration capture or retention answer accompanies the revision.",
      "limitation": "The supplied change reopens the data-reach and default-setting question; it does not prove the live setting."
    },
    {
      "id": "src-procedure-confirmation",
      "title": "Returned controlling-version confirmation",
      "version": "Owner response 1",
      "calendar_date": null,
      "approval_status": "Synthetic role confirmation; actual-institution signer and date remain blank",
      "review_state": "Inspected and judged sufficient in this illustration for the version question only",
      "content": "The procedure owner confirms Revision 1 controls, withdraws Revision 2 working copy for this workflow and retains the second-review requirement. The returned response includes the controlling approval reference and explicitly addresses the conflicting instruction.",
      "limitation": "Resolves only the controlling-version question in the synthetic sequence. It does not authorize assistant use or establish the permitted-input boundary."
    }
  ],
  "coverage_activities": [
    {
      "id": "cov-scope",
      "activity": "Agree the review boundary",
      "what_was_done": "Read the intake baseline and record the two declared uses and supplied materials.",
      "finding": "The engagement is bounded to the supplied records and these two uses.",
      "limit": "No network discovery, system access or institution-wide census was performed."
    },
    {
      "id": "cov-disclosures",
      "activity": "Reconcile use disclosures",
      "what_was_done": "Compare staff-use disclosure with the embedded-feature proposal and vendor disclosure.",
      "finding": "Staff inputs and vendor data reach remain incompletely declared.",
      "limit": "A disclosure does not establish actual behavior."
    },
    {
      "id": "cov-versions",
      "activity": "Reconcile procedure versions",
      "what_was_done": "Compare both supplied excerpts and their approval provenance.",
      "finding": "Secondary-review instructions conflict; only the earlier version has supplied approval evidence.",
      "limit": "No full-procedure acceptance or supersession determination is made."
    },
    {
      "id": "cov-review",
      "activity": "Prepare the reviewer file",
      "what_was_done": "Record observations, open questions, role assignments, recommendation and conditions.",
      "finding": "The board summary explains why feature activation is deferred and staff drafting is limited.",
      "limit": "Preparation does not record a reviewer acceptance or an institutional decision."
    },
    {
      "id": "cov-change",
      "activity": "Review a supplied change",
      "what_was_done": "Retain the baseline and compare a revised vendor disclosure to the initial disclosure.",
      "finding": "Default activation and free-text data reach reopen the affected question.",
      "limit": "The revised disclosure is not a live configuration inspection."
    }
  ],
  "six_column_evidence_rows": [
    {
      "id": "use-staff",
      "use": "Staff drafting of procedure explanations",
      "where_it_runs": "A public assistant outside the institution",
      "data_it_can_touch": "Reported procedure text; full inputs are not disclosed. Customer, member, account and confidential material must be excluded.",
      "owner": "Operations procedure owner",
      "evidence_on_hand": "Staff-use disclosure; earlier controlled procedure; later working copy; supplied approval record for the earlier version; returned controlling-version confirmation",
      "question_still_open": "Can the permitted-input boundary and generated-answer review be demonstrated?",
      "source_ids": [
        "src-staff",
        "src-procedure-earlier",
        "src-procedure-later",
        "src-procedure-confirmation"
      ],
      "reviewer_observation": "Returned evidence resolves the controlling-version question in this illustration. Staff inputs and safe-use treatment remain open.",
      "review_disposition": "Retain the earlier controlled procedure as the review baseline; resolve conflict before using generated instructions operationally."
    },
    {
      "id": "use-vendor",
      "use": "Embedded AI summary feature in an existing platform",
      "where_it_runs": "The vendor's service; downstream processing is not declared",
      "data_it_can_touch": "Initial disclosure mentions event metadata; free-text reach, retention and downstream access are unresolved.",
      "owner": "Vendor-management owner with IT review",
      "evidence_on_hand": "Embedded-feature proposal and incomplete initial vendor disclosure",
      "question_still_open": "Is the feature enabled by default, what can it read, and does the institution's off setting stop the relevant processing?",
      "source_ids": [
        "src-vendor-proposal",
        "src-vendor-disclosure"
      ],
      "reviewer_observation": "The documents describe a feature but do not establish the live setting or effective off control.",
      "review_disposition": "Do not authorize activation on the supplied evidence; request configuration and data-handling evidence."
    }
  ],
  "conflicting_procedure_excerpts": [
    {
      "source_id": "src-procedure-earlier",
      "excerpt": "A second reviewer must approve an exception before staff act. If an instruction conflicts with the controlled procedure, pause and refer the question to the procedure owner.",
      "approval_state": "A supplied approval record marks this version approved through the institution's procedure-control route. The approver name and calendar date are blank."
    },
    {
      "source_id": "src-procedure-later",
      "excerpt": "Staff may act on a routine exception and notify the second reviewer afterward. The working copy does not say when an exception stops being routine.",
      "approval_state": "No approval record or supersession notice is supplied."
    }
  ],
  "open_questions": [
    {
      "id": "q-procedure",
      "question": "Which procedure version controls?",
      "reason": "The supplied excerpts conflict and the later working copy lacks approval and supersession evidence.",
      "needed_evidence": "Procedure owner's controlling-version confirmation, approval record and explicit treatment of the conflicting instruction.",
      "owner_role": "Operations procedure owner",
      "status": "Resolved in illustration for controlling version only",
      "resolution_source_id": "src-procedure-confirmation",
      "resolution_reason": "The returned owner response identifies the controlling version, approval reference and treatment of the conflicting instruction."
    },
    {
      "id": "q-staff-data",
      "question": "What text has staff sent, and what may they send?",
      "reason": "The staff disclosure does not enumerate inputs or demonstrate exclusion of confidential material.",
      "needed_evidence": "A permitted-input rule, a redacted input example and a review of the disclosed usage boundary.",
      "owner_role": "Risk/compliance owner with operations",
      "status": "Open"
    },
    {
      "id": "q-vendor",
      "question": "What can the feature read, and is it effectively off?",
      "reason": "Default behavior, fields, retention, downstream access and effective disablement are not established.",
      "needed_evidence": "Feature-specific handling terms, field list, retention answer and authorized configuration evidence.",
      "owner_role": "Vendor-management owner with IT",
      "status": "Reopened by supplied change"
    },
    {
      "id": "q-return",
      "question": "What evidence would permit a return to the reviewer?",
      "reason": "The recommendation is conditional; no acceptance or institutional authorization is recorded.",
      "needed_evidence": "Completed role actions, reviewed supporting evidence and a separate recorded decision by the authorized institution reviewer.",
      "owner_role": "Risk/compliance owner",
      "status": "Open"
    }
  ],
  "actions": [
    {
      "id": "action-procedure",
      "owner_role": "Operations procedure owner",
      "action": "Confirm the controlling procedure and resolve the secondary-review conflict with an approval or correction record.",
      "due_milestone": "Before any generated procedure instruction is used operationally",
      "calendar_due_date": null,
      "evidence_to_return": "Controlling-version confirmation and approved treatment of the conflicting instruction",
      "status": "Resolved in illustration after sufficient returned evidence",
      "question_ids": [
        "q-procedure"
      ],
      "closure_source_ids": [
        "src-procedure-confirmation"
      ],
      "closure_scope": "Version confirmation only; assistant authorization remains separate",
      "reviewer_role": "Illustrative procedure-control reviewer",
      "actual_institution_acceptance": null
    },
    {
      "id": "action-staff",
      "owner_role": "Risk/compliance owner with operations",
      "action": "Define permitted inputs, collect a redacted example, and review the staff-use disclosure before allowing the limited drafting workflow.",
      "due_milestone": "Before the limited staff drafting workflow begins",
      "calendar_due_date": null,
      "evidence_to_return": "Permitted-input rule, redacted input example and documented review",
      "status": "Assigned role; completion not asserted",
      "question_ids": [
        "q-staff-data"
      ]
    },
    {
      "id": "action-vendor",
      "owner_role": "Vendor-management owner",
      "action": "Obtain feature-specific default, field-access, retention, downstream-processing and disablement answers; reconcile the revised disclosure.",
      "due_milestone": "Before feature activation is reconsidered",
      "calendar_due_date": null,
      "evidence_to_return": "Written feature disclosure and handling terms with unresolved items identified",
      "status": "Assigned role; completion not asserted",
      "question_ids": [
        "q-vendor"
      ]
    },
    {
      "id": "action-it",
      "owner_role": "IT owner",
      "action": "Inspect the authorized feature setting and document what the off control covers; use approved synthetic test material if a control test is authorized.",
      "due_milestone": "Before feature activation is reconsidered",
      "calendar_due_date": null,
      "evidence_to_return": "Authorized setting record and any separately authorized control-test result",
      "status": "Inspection and test are requested; neither is claimed completed",
      "question_ids": [
        "q-vendor"
      ]
    },
    {
      "id": "action-board",
      "owner_role": "Risk/compliance owner",
      "action": "Return the evidence and unresolved items to the authorized reviewer, then record any actual decision separately.",
      "due_milestone": "At the next reviewer decision milestone after the evidence actions",
      "calendar_due_date": null,
      "evidence_to_return": "Reviewer observations and a separately completed institution decision record",
      "status": "Reviewer acceptance and institution decision remain blank",
      "question_ids": [
        "q-return"
      ]
    }
  ],
  "retained_baseline": {
    "id": "baseline-review",
    "label": "Retained review baseline",
    "source_ids": [
      "src-intake",
      "src-staff",
      "src-procedure-earlier",
      "src-procedure-later",
      "src-vendor-proposal",
      "src-vendor-disclosure"
    ],
    "recommendation": "Retain the earlier controlled procedure as the baseline. Limit staff drafting to approved generic or redacted procedure material under human review once the input and version conditions are resolved. Keep the embedded feature disabled pending evidence of data reach, defaults and effective disablement.",
    "decision_conditions": [
      "The procedure owner confirms the controlling version and resolves the secondary-review conflict.",
      "Risk/compliance and operations review the permitted-input rule and redacted example; confidential material remains outside the public assistant.",
      "Vendor management supplies complete feature-specific handling answers, and IT provides authorized evidence of the relevant setting and control behavior.",
      "The authorized institution reviewer makes and records the actual decision separately; a source reference or completed checkbox is insufficient."
    ],
    "actual_institution_decision": {
      "decision": null,
      "reviewer": null,
      "owner": null,
      "calendar_date": null
    },
    "retention_note": "Keep the initial source register, excerpts, observations, open questions and recommendation together. The supplied follow-up does not overwrite them."
  },
  "change_event": {
    "id": "change-vendor-disclosure",
    "trigger": "A revised vendor feature disclosure is supplied after the baseline review.",
    "source_id": "src-change",
    "changed_claim": "The feature is described as enabled unless disabled, with access to free-text service notes as well as event metadata.",
    "affected_question_id": "q-vendor",
    "reopened_question": "What can the feature read, and is it effectively off?",
    "reviewer_observation": "The changed default and broader stated data reach require new configuration and handling evidence. The source change does not prove the live feature is active or that a disable control works.",
    "actions_reopened": [
      "action-vendor",
      "action-it"
    ],
    "baseline_disposition": "Retain the baseline. Add this revision and a follow-up observation; do not silently replace the earlier evidence.",
    "recommendation_after_change": "Continue to defer feature activation and request revised handling answers plus authorized setting evidence. The controlling-version action remains resolved in the illustration; permitted staff inputs and generated-answer review remain open.",
    "actual_institution_decision": {
      "decision": null,
      "reviewer": null,
      "owner": null,
      "calendar_date": null
    }
  },
  "actual_institution_decision": {
    "decision": null,
    "reviewer": null,
    "owner": null,
    "calendar_date": null
  },
  "disclosure": "Supporting records for a synthetic illustration; no institutional acceptance or live inspection is asserted.",
  "illustrative": true,
  "review_scope": {
    "uses": 2,
    "records": "Only the declared uses and listed source versions",
    "exclusions": [
      "Institution-wide discovery",
      "Live systems and configurations",
      "Confidential customer records",
      "Legal opinion and compliance certification"
    ],
    "timing": "Illustrative sequence, not a measured delivery duration"
  },
  "tiering_method": {
    "source": "https://www.csbs.org/node/584231",
    "source_checked": "October 11, 2026",
    "method": "Assess consumer impact, human oversight, harm potential and data sensitivity. The highest-rated known factor generally sets the preliminary tier. Unknown factors keep the assignment provisional.",
    "boundary": "Tiers follow the optional CSBS worksheet. Your institution assigns the final tier.",
    "factor_assessments": [
      {
        "use_id": "use-staff",
        "consumer_impact": "Tier 2: drafts may affect operational instructions",
        "human_oversight": "Unknown: consistent qualified review not evidenced",
        "harm_potential": "Tier 2: a wrong instruction could cause operational harm",
        "data_sensitivity": "Unknown: historical inputs not verified",
        "preliminary_tier": "Tier 2 provisional; unknown factors may raise the tier"
      },
      {
        "use_id": "use-vendor",
        "consumer_impact": "Unknown: output use not accepted",
        "human_oversight": "Unknown: checkpoints not evidenced",
        "harm_potential": "Unknown: operating dependence not established",
        "data_sensitivity": "Potential Tier 3: free-text service notes may contain sensitive information",
        "preliminary_tier": "Tier 3 provisional pending data and control review"
      }
    ],
    "version": "CSBS worksheet preparation: example edition 2026-10-17"
  },
  "proposed_risk_tiers": [
    {
      "use_id": "use-staff",
      "proposed_tier": "Tier 2 provisional; unknown factors may raise the tier",
      "reasons": [
        "Drafts may become operational instructions.",
        "Inputs and controlling versions were initially unclear."
      ],
      "source_ids": [
        "src-staff",
        "src-procedure-earlier",
        "src-procedure-later",
        "src-procedure-confirmation"
      ],
      "uncertainty": "Historical staff inputs and permitted-input enforcement remain unverified.",
      "possible_treatment": "Consider a Tier 1 only after permitted generic inputs, controlled versions and human review are evidenced.",
      "reviewer_role": "Institution risk reviewer",
      "reviewer_status": "Pending institution review",
      "institution_accepted_tier": null
    },
    {
      "use_id": "use-vendor",
      "proposed_tier": "Tier 3 provisional pending data and control review",
      "reasons": [
        "The revised disclosure expands stated reach to free-text service notes.",
        "Default activation, retention and effective shutdown require evidence.",
        "Service notes may contain sensitive information; actual contents and safeguards remain unknown."
      ],
      "source_ids": [
        "src-vendor-disclosure",
        "src-change"
      ],
      "uncertainty": "No authorized setting inspection or shutdown test has been returned.",
      "possible_treatment": "Keep activation deferred; obtain handling answers and authorized control evidence.",
      "reviewer_role": "Institution risk reviewer with IT",
      "reviewer_status": "Pending institution review",
      "institution_accepted_tier": null
    }
  ],
  "safe_use_policy_gaps": [
    {
      "id": "gap-input-version",
      "use_id": "use-staff",
      "source_ids": [
        "src-staff",
        "src-procedure-earlier",
        "src-procedure-later"
      ],
      "finding": "Neither supplied procedure excerpt states which inputs may enter a public assistant or how generated wording is checked against the controlling version.",
      "proposed_treatment": "Permit only approved generic or redacted procedure text. Exclude member, account and confidential material. Record the controlling version and require a second reviewer before operational use.",
      "action_id": "action-staff",
      "owner_role": "Risk/compliance owner with operations",
      "status": "Open; treatment proposed, not an approved policy",
      "board_condition": "Tier 1 staff drafting remains conditional on reviewed input boundaries and generated-answer review."
    }
  ],
  "evidence_assessments": [
    {
      "id": "assessment-version",
      "question_id": "q-procedure",
      "source_ids": [
        "src-procedure-earlier",
        "src-procedure-later",
        "src-procedure-confirmation"
      ],
      "declaration_received": true,
      "reference_supplied": true,
      "source_inspected": "Synthetic reviewer compared the returned response with both excerpts",
      "sufficiency": "Sufficient in this illustration for controlling version only",
      "reviewer_role": "Illustrative procedure-control reviewer",
      "review_date": null,
      "institution_decision_recorded": false,
      "limitation": "No actual-institution approval, use authorization or verified signature"
    },
    {
      "id": "assessment-inputs",
      "question_id": "q-staff-data",
      "source_ids": [
        "src-staff"
      ],
      "declaration_received": true,
      "reference_supplied": true,
      "source_inspected": "Synthetic review of supplied disclosure",
      "sufficiency": "Insufficient: input examples and an accepted safe-use treatment are missing",
      "reviewer_role": "Illustrative risk reviewer",
      "review_date": null,
      "institution_decision_recorded": false
    },
    {
      "id": "assessment-vendor",
      "question_id": "q-vendor",
      "source_ids": [
        "src-vendor-disclosure",
        "src-change"
      ],
      "declaration_received": true,
      "reference_supplied": true,
      "source_inspected": "Synthetic comparison of initial and revised disclosures",
      "sufficiency": "Insufficient: configuration, shutdown, retention and downstream handling remain open",
      "reviewer_role": "Illustrative risk reviewer with IT",
      "review_date": null,
      "institution_decision_recorded": false
    }
  ],
  "board_traceability": [
    {
      "finding": "Version conflict",
      "question_id": "q-procedure",
      "action_ids": [
        "action-procedure"
      ],
      "assessment_id": "assessment-version",
      "board_recommendation": "Retain Revision 1 as the controlling baseline in this example.",
      "condition": "Closing this action alone does not authorize AI use."
    },
    {
      "finding": "Safe-use policy gap and unknown historical inputs",
      "question_id": "q-staff-data",
      "action_ids": [
        "action-staff"
      ],
      "assessment_id": "assessment-inputs",
      "board_recommendation": "Defer operational use of generated instructions pending accepted input and review rules.",
      "condition": "Institution records its own decision after evidence review."
    },
    {
      "finding": "Expanded vendor data reach and unresolved shutdown",
      "question_id": "q-vendor",
      "action_ids": [
        "action-vendor",
        "action-it"
      ],
      "assessment_id": "assessment-vendor",
      "board_recommendation": "Keep embedded-feature activation deferred.",
      "condition": "Revised handling terms and authorized control evidence must return to review."
    }
  ],
  "follow_up_history": [
    {
      "stage": "Initial baseline",
      "records": {
        "schema_version": "1.0",
        "source_register": [
          {
            "id": "src-intake",
            "title": "Intake and supplied-records list",
            "version": "Intake baseline",
            "calendar_date": null,
            "approval_status": "Sponsor scope acknowledgment is illustrated; no institutional authorization is recorded.",
            "review_state": "Read in this illustration",
            "content": "Two declared uses are in scope: staff drafting from procedure text and an embedded vendor feature under consideration. No customer or account data is supplied.",
            "limitation": "The list is the supplied starting point, not a complete technology census."
          },
          {
            "id": "src-staff",
            "title": "Staff-use disclosure",
            "version": "Initial disclosure",
            "calendar_date": null,
            "approval_status": "No authorization to send confidential material is supplied.",
            "review_state": "Read in this illustration",
            "content": "Staff report using a public assistant to draft procedure explanations. The assistant runs outside the institution. Staff do not declare which procedure version was used or all text entered.",
            "limitation": "Self-report is incomplete and does not establish data exclusion or full usage coverage."
          },
          {
            "id": "src-procedure-earlier",
            "title": "Earlier controlled procedure",
            "version": "Revision 1",
            "calendar_date": null,
            "approval_status": "A supplied approval record marks this version approved through the institution's procedure-control route. The approver name and calendar date are blank.",
            "review_state": "Excerpt compared in this illustration",
            "content": "A second reviewer must approve an exception before staff act. If an instruction conflicts with the controlled procedure, pause and refer the question to the procedure owner.",
            "limitation": "This excerpt alone does not establish that the full procedure is complete, current or acceptable."
          },
          {
            "id": "src-procedure-later",
            "title": "Later working procedure copy",
            "version": "Revision 2 working copy",
            "calendar_date": null,
            "approval_status": "No approval record or supersession notice is supplied.",
            "review_state": "Excerpt compared in this illustration",
            "content": "Staff may act on a routine exception and notify the second reviewer afterward. The working copy does not say when an exception stops being routine.",
            "limitation": "The higher revision number does not make this working copy the controlling version."
          },
          {
            "id": "src-vendor-proposal",
            "title": "Embedded-feature proposal",
            "version": "Proposal baseline",
            "calendar_date": null,
            "approval_status": "No feature activation approval is supplied.",
            "review_state": "Read in this illustration",
            "content": "The existing platform may include an AI-assisted summary feature. The proposal describes summaries but does not state whether the feature is on by default, which fields it reads, what is retained, or how the institution disables it.",
            "limitation": "A proposal reference is evidence of a claim, not evidence of actual configuration or accepted controls."
          },
          {
            "id": "src-vendor-disclosure",
            "title": "Vendor feature disclosure",
            "version": "Initial disclosure",
            "calendar_date": null,
            "approval_status": "No institutional acceptance is supplied.",
            "review_state": "Read in this illustration",
            "content": "The disclosure refers to service-event metadata and an administrator setting. It does not describe free-text fields, downstream processing, retention, or the effect of switching the setting off.",
            "limitation": "The disclosure leaves data reach and effective disablement unanswered."
          },
          {
            "id": "src-change",
            "title": "Changed vendor feature disclosure",
            "version": "Revised disclosure",
            "calendar_date": null,
            "approval_status": "No institutional acceptance or activation approval is supplied.",
            "review_state": "Read and compared in the follow-up illustration",
            "content": "The revised disclosure says the feature is enabled unless the institution disables it and may read free-text service notes in addition to event metadata. No configuration capture or retention answer accompanies the revision.",
            "limitation": "The supplied change reopens the data-reach and default-setting question; it does not prove the live setting."
          }
        ],
        "coverage_activities": [
          {
            "id": "cov-scope",
            "activity": "Agree the review boundary",
            "what_was_done": "Read the intake baseline and record the two declared uses and supplied materials.",
            "finding": "The engagement is bounded to the supplied records and these two uses.",
            "limit": "No network discovery, system access or institution-wide census was performed."
          },
          {
            "id": "cov-disclosures",
            "activity": "Reconcile use disclosures",
            "what_was_done": "Compare staff-use disclosure with the embedded-feature proposal and vendor disclosure.",
            "finding": "Staff inputs and vendor data reach remain incompletely declared.",
            "limit": "A disclosure does not establish actual behavior."
          },
          {
            "id": "cov-versions",
            "activity": "Reconcile procedure versions",
            "what_was_done": "Compare both supplied excerpts and their approval provenance.",
            "finding": "Secondary-review instructions conflict; only the earlier version has supplied approval evidence.",
            "limit": "No full-procedure acceptance or supersession determination is made."
          },
          {
            "id": "cov-review",
            "activity": "Prepare the reviewer file",
            "what_was_done": "Record observations, open questions, role assignments, recommendation and conditions.",
            "finding": "The board summary explains why feature activation is deferred and staff drafting is limited.",
            "limit": "Preparation does not record a reviewer acceptance or an institutional decision."
          },
          {
            "id": "cov-change",
            "activity": "Review a supplied change",
            "what_was_done": "Retain the baseline and compare a revised vendor disclosure to the initial disclosure.",
            "finding": "Default activation and free-text data reach reopen the affected question.",
            "limit": "The revised disclosure is not a live configuration inspection."
          }
        ],
        "six_column_evidence_rows": [
          {
            "id": "use-staff",
            "use": "Staff drafting of procedure explanations",
            "where_it_runs": "A public assistant outside the institution",
            "data_it_can_touch": "Reported procedure text; full inputs are not disclosed. Customer, member, account and confidential material must be excluded.",
            "owner": "Operations procedure owner",
            "evidence_on_hand": "Staff-use disclosure; earlier controlled procedure; later working copy; supplied approval record for the earlier version",
            "question_still_open": "Which version controls, and can the permitted input boundary be demonstrated?",
            "source_ids": [
              "src-staff",
              "src-procedure-earlier",
              "src-procedure-later"
            ],
            "reviewer_observation": "The excerpts conflict on secondary review. No supersession evidence supports treating the later working copy as controlling. Input disclosure remains incomplete.",
            "review_disposition": "Retain the earlier controlled procedure as the review baseline; resolve conflict before using generated instructions operationally."
          },
          {
            "id": "use-vendor",
            "use": "Embedded AI summary feature in an existing platform",
            "where_it_runs": "The vendor's service; downstream processing is not declared",
            "data_it_can_touch": "Initial disclosure mentions event metadata; free-text reach, retention and downstream access are unresolved.",
            "owner": "Vendor-management owner with IT review",
            "evidence_on_hand": "Embedded-feature proposal and incomplete initial vendor disclosure",
            "question_still_open": "Is the feature enabled by default, what can it read, and does the institution's off setting stop the relevant processing?",
            "source_ids": [
              "src-vendor-proposal",
              "src-vendor-disclosure"
            ],
            "reviewer_observation": "The documents describe a feature but do not establish the live setting or effective off control.",
            "review_disposition": "Do not authorize activation on the supplied evidence; request configuration and data-handling evidence."
          }
        ],
        "conflicting_procedure_excerpts": [
          {
            "source_id": "src-procedure-earlier",
            "excerpt": "A second reviewer must approve an exception before staff act. If an instruction conflicts with the controlled procedure, pause and refer the question to the procedure owner.",
            "approval_state": "A supplied approval record marks this version approved through the institution's procedure-control route. The approver name and calendar date are blank."
          },
          {
            "source_id": "src-procedure-later",
            "excerpt": "Staff may act on a routine exception and notify the second reviewer afterward. The working copy does not say when an exception stops being routine.",
            "approval_state": "No approval record or supersession notice is supplied."
          }
        ],
        "open_questions": [
          {
            "id": "q-procedure",
            "question": "Which procedure version controls?",
            "reason": "The supplied excerpts conflict and the later working copy lacks approval and supersession evidence.",
            "needed_evidence": "Procedure owner's controlling-version confirmation, approval record and explicit treatment of the conflicting instruction.",
            "owner_role": "Operations procedure owner",
            "status": "Open"
          },
          {
            "id": "q-staff-data",
            "question": "What text has staff sent, and what may they send?",
            "reason": "The staff disclosure does not enumerate inputs or demonstrate exclusion of confidential material.",
            "needed_evidence": "A permitted-input rule, a redacted input example and a review of the disclosed usage boundary.",
            "owner_role": "Risk/compliance owner with operations",
            "status": "Open"
          },
          {
            "id": "q-vendor",
            "question": "What can the feature read, and is it effectively off?",
            "reason": "Default behavior, fields, retention, downstream access and effective disablement are not established.",
            "needed_evidence": "Feature-specific handling terms, field list, retention answer and authorized configuration evidence.",
            "owner_role": "Vendor-management owner with IT",
            "status": "Reopened by supplied change"
          },
          {
            "id": "q-return",
            "question": "What evidence would permit a return to the reviewer?",
            "reason": "The recommendation is conditional; no acceptance or institutional authorization is recorded.",
            "needed_evidence": "Completed role actions, reviewed supporting evidence and a separate recorded decision by the authorized institution reviewer.",
            "owner_role": "Risk/compliance owner",
            "status": "Open"
          }
        ],
        "actions": [
          {
            "id": "action-procedure",
            "owner_role": "Operations procedure owner",
            "action": "Confirm the controlling procedure and resolve the secondary-review conflict with an approval or correction record.",
            "due_milestone": "Before any generated procedure instruction is used operationally",
            "calendar_due_date": null,
            "evidence_to_return": "Controlling-version confirmation and approved treatment of the conflicting instruction",
            "status": "Assigned role; completion not asserted",
            "question_ids": [
              "q-procedure"
            ]
          },
          {
            "id": "action-staff",
            "owner_role": "Risk/compliance owner with operations",
            "action": "Define permitted inputs, collect a redacted example, and review the staff-use disclosure before allowing the limited drafting workflow.",
            "due_milestone": "Before the limited staff drafting workflow begins",
            "calendar_due_date": null,
            "evidence_to_return": "Permitted-input rule, redacted input example and documented review",
            "status": "Assigned role; completion not asserted",
            "question_ids": [
              "q-staff-data"
            ]
          },
          {
            "id": "action-vendor",
            "owner_role": "Vendor-management owner",
            "action": "Obtain feature-specific default, field-access, retention, downstream-processing and disablement answers; reconcile the revised disclosure.",
            "due_milestone": "Before feature activation is reconsidered",
            "calendar_due_date": null,
            "evidence_to_return": "Written feature disclosure and handling terms with unresolved items identified",
            "status": "Assigned role; completion not asserted",
            "question_ids": [
              "q-vendor"
            ]
          },
          {
            "id": "action-it",
            "owner_role": "IT owner",
            "action": "Inspect the authorized feature setting and document what the off control covers; use approved synthetic test material if a control test is authorized.",
            "due_milestone": "Before feature activation is reconsidered",
            "calendar_due_date": null,
            "evidence_to_return": "Authorized setting record and any separately authorized control-test result",
            "status": "Inspection and test are requested; neither is claimed completed",
            "question_ids": [
              "q-vendor"
            ]
          },
          {
            "id": "action-board",
            "owner_role": "Risk/compliance owner",
            "action": "Return the evidence and unresolved items to the authorized reviewer, then record any actual decision separately.",
            "due_milestone": "At the next reviewer decision milestone after the evidence actions",
            "calendar_due_date": null,
            "evidence_to_return": "Reviewer observations and a separately completed institution decision record",
            "status": "Reviewer acceptance and institution decision remain blank",
            "question_ids": [
              "q-return"
            ]
          }
        ],
        "retained_baseline": {
          "id": "baseline-review",
          "label": "Retained review baseline",
          "source_ids": [
            "src-intake",
            "src-staff",
            "src-procedure-earlier",
            "src-procedure-later",
            "src-vendor-proposal",
            "src-vendor-disclosure"
          ],
          "recommendation": "Retain the earlier controlled procedure as the baseline. Limit staff drafting to approved generic or redacted procedure material under human review once the input and version conditions are resolved. Keep the embedded feature disabled pending evidence of data reach, defaults and effective disablement.",
          "decision_conditions": [
            "The procedure owner confirms the controlling version and resolves the secondary-review conflict.",
            "Risk/compliance and operations review the permitted-input rule and redacted example; confidential material remains outside the public assistant.",
            "Vendor management supplies complete feature-specific handling answers, and IT provides authorized evidence of the relevant setting and control behavior.",
            "The authorized institution reviewer makes and records the actual decision separately; a source reference or completed checkbox is insufficient."
          ],
          "actual_institution_decision": {
            "decision": null,
            "reviewer": null,
            "owner": null,
            "calendar_date": null
          },
          "retention_note": "Keep the initial source register, excerpts, observations, open questions and recommendation together. The supplied follow-up does not overwrite them."
        },
        "change_event": {
          "id": "change-vendor-disclosure",
          "trigger": "A revised vendor feature disclosure is supplied after the baseline review.",
          "source_id": "src-change",
          "changed_claim": "The feature is described as enabled unless disabled, with access to free-text service notes as well as event metadata.",
          "affected_question_id": "q-vendor",
          "reopened_question": "What can the feature read, and is it effectively off?",
          "reviewer_observation": "The changed default and broader stated data reach require new configuration and handling evidence. The source change does not prove the live feature is active or that a disable control works.",
          "actions_reopened": [
            "action-vendor",
            "action-it"
          ],
          "baseline_disposition": "Retain the baseline. Add this revision and a follow-up observation; do not silently replace the earlier evidence.",
          "recommendation_after_change": "Continue to defer feature activation and request the revised handling answers plus authorized setting evidence. The staff version-control question stays open on its existing evidence.",
          "actual_institution_decision": {
            "decision": null,
            "reviewer": null,
            "owner": null,
            "calendar_date": null
          }
        },
        "actual_institution_decision": {
          "decision": null,
          "reviewer": null,
          "owner": null,
          "calendar_date": null
        },
        "disclosure": "Supporting records for a synthetic illustration; no institutional acceptance or live inspection is asserted."
      },
      "note": "Retained unchanged. Initial questions and actions remain visible as history."
    },
    {
      "stage": "Returned evidence",
      "source_id": "src-procedure-confirmation",
      "question_id": "q-procedure",
      "action_id": "action-procedure",
      "result": "Version question resolved in the illustration; assistant use remains unapproved."
    },
    {
      "stage": "Later vendor change",
      "event": {
        "id": "change-vendor-disclosure",
        "trigger": "A revised vendor feature disclosure is supplied after the baseline review.",
        "source_id": "src-change",
        "changed_claim": "The feature is described as enabled unless disabled, with access to free-text service notes as well as event metadata.",
        "affected_question_id": "q-vendor",
        "reopened_question": "What can the feature read, and is it effectively off?",
        "reviewer_observation": "The changed default and broader stated data reach require new configuration and handling evidence. The source change does not prove the live feature is active or that a disable control works.",
        "actions_reopened": [
          "action-vendor",
          "action-it"
        ],
        "baseline_disposition": "Retain the baseline. Add this revision and a follow-up observation; do not silently replace the earlier evidence.",
        "recommendation_after_change": "Continue to defer feature activation and request revised handling answers plus authorized setting evidence. The controlling-version action remains resolved in the illustration; permitted staff inputs and generated-answer review remain open.",
        "actual_institution_decision": {
          "decision": null,
          "reviewer": null,
          "owner": null,
          "calendar_date": null
        }
      },
      "result": "Vendor question and two related actions return to review. Prior record is retained; no approval carries forward."
    }
  ],
  "delivery_checklist": [
    "Declared coverage and exclusions",
    "AI use inventory",
    "Source/version register",
    "Evidence assessment and gaps",
    "Proposed risk tiers with reasons",
    "Safe-use policy gap and treatment",
    "Owned actions and milestones",
    "Examiner-request mapping",
    "Board briefing with evidence links",
    "Blank actual-institution decision",
    "Retained baseline and changed-source review"
  ],
  "examiner_mapping": [
    {
      "request": "Inventory",
      "where_answer_lives": "Declared-use summary and review boundary",
      "limit": "Declared uses only"
    },
    {
      "request": "Policies",
      "where_answer_lives": "Source register and safe-use policy gap",
      "limit": "Treatment proposed; institution accepts"
    },
    {
      "request": "Governance",
      "where_answer_lives": "Owned actions and the separate institution decision",
      "limit": "Actual acceptance blank"
    },
    {
      "request": "Risk assessment",
      "where_answer_lives": "Tiering method and proposed tier reasons",
      "limit": "Proposed CSBS-aligned tiers"
    },
    {
      "request": "Vendor documents",
      "where_answer_lives": "Source register and evidence assessments",
      "limit": "Disclosure is not configuration inspection"
    },
    {
      "request": "Monitoring",
      "where_answer_lives": "Retained baseline and supplied-change history",
      "limit": "Supplied updates, not automatic monitoring"
    },
    {
      "request": "Risk tier worksheet",
      "where_answer_lives": "Proposed risk tiers and reviewer status",
      "limit": "Institution reviewer still required"
    }
  ],
  "export_boundary": "Preparation and illustrative reviewer observations are separate from actual institution acceptance. Blank decision fields remain blank.",
  "example_edition": "2026-10-17",
  "as_of_state": "After returned procedure confirmation and the later vendor disclosure; institution decisions remain blank.",
  "method_review": {
    "status": "Proposed illustration; qualified reviewer signoff not recorded",
    "reviewer": null,
    "date": null,
    "selection_note": "Use the existing supporting record four-factor method consistently. No new institutional or regulator acceptance is asserted."
  },
  "board_brief": {
    "recommendation": "Keep embedded-feature activation deferred. Consider staff drafting only after input limits and human review are accepted.",
    "rationale": "The procedure version conflict is resolved in this illustration. Vendor handling, data reach and shutdown evidence remain incomplete.",
    "conditions": [
      "Retain Revision 1 as the controlling procedure baseline.",
      "Return an accepted input rule and evidence of generated-answer review before operational use.",
      "Obtain feature-specific handling terms and authorized shutdown evidence before reconsidering activation."
    ],
    "tiers": {
      "use-staff": "Tier 2 provisional; unknown factors may raise the tier",
      "use-vendor": "Tier 3 provisional pending data and control review"
    },
    "institution_decision": null,
    "institution_reviewer": null,
    "decision_date": null
  }
}
