The Office Was Ready. The Information Was Not.

Illustrative EICARS scenario. The Regional Public Services Agency, Riverton office, documents, dates and responses in this article are fictional. The responses illustrate desired and undesired behavior; they are not results from an AI test or evidence of EICARS conformance.

A straightforward question with a difficult answer

The Riverton office has new desks, finished workspaces and a completed facilities inspection. Its director asks an enterprise AI assistant: “Can we open on November 1? What remains unresolved, what evidence supports the assessment, and who can authorize the outstanding actions?”

The assistant finds an early relocation schedule and a recent facilities report. It answers that the office is ready. The answer sounds reasonable. It is also unsupported.

The approved target date has changed to December 1. Network acceptance is still pending. An unsigned contract modification describes work that has not yet been authorized. Staffing information is held in a restricted HR system. Facilities readiness is only one part of operational readiness.

The information exists across the agency. Its meaning depends on knowing which office controls each subject, what was approved, when it applies and what remains unknown. Connecting a model to more files does not settle those questions.

Stage one: the organization relies on individual cognition

At the start, Facilities keeps inspection reports in a shared drive. Acquisition manages contract files in its procurement system. Finance tracks funding in its financial application. IT maintains installation tickets. HR holds staffing information in a protected system. The mission office coordinates the opening through email and a SharePoint site.

Each employee has a workable personal approach: a folder structure, an inbox, a spreadsheet or remembered conversations. An experienced coordinator knows that “final” in one filename means reviewed, while another office uses it to mean approved. She knows the director changed the target date and that a positive inspection does not authorize opening.

When the coordinator is unavailable, her colleagues must reconstruct that understanding. The AI assistant faces a similar problem, with the additional risk that a fluent summary can conceal missing evidence. A filename, upload date or confident sentence does not establish organizational authority.

Stage two: responsibility and information become shared

The agency begins with one bounded task: supporting the Riverton opening decision. It names the participating offices, the required decisions and the information needed to support them. It assigns an executive sponsor, business owners, a records official and security, privacy, accessibility and IT representatives. These roles coordinate preparation; they do not acquire powers held by other officials.

The agency identifies the designated source for each subject. Acquisition remains responsible for its contract records. Finance remains responsible for funding information. HR retains control of protected personnel information. Existing systems can remain in place. The common architecture describes how authorized users identify and reach the relevant information across those systems.

The director’s approved opening-date decision is captured in the designated repository. The earlier schedule remains identifiable as an earlier plan. The unsigned modification is clearly distinguished from an executed modification. The IT acceptance status has a responsible office and a date of assessment.

Staff can now assemble a supported readiness briefing without relying on one person’s memory. This is distributed information cognition in the sense used in this story: understanding is supported by shared information and assigned responsibilities across the organization. It does not mean that a repository thinks or that a new decision authority has been created.

Stage three: the environment is prepared primarily for AI use

The next design question is whether an authorized machine can consistently retrieve and interpret the information needed for the task. The agency prioritizes machine usability when choosing its shared information structure. Personal filing preferences no longer determine the enterprise structure.

Staff receive useful views, familiar application access and workable contribution processes within that structure. Accessibility, privacy, records obligations, security, human decision authority and operational requirements remain governing constraints. A convenient AI connection cannot override them.

The agency uses capabilities suited to its existing platforms: stable references, identifiable revisions, supported approval information, useful descriptions, accessible content and controlled access. It checks that integrations preserve the information needed for the task. It does not assume every model needs an identical corpus layout or that every repository must be replaced.

The assistant can use an authorized HR readiness attestation prepared for the project, if the agency has approved that disclosure. It does not receive unrestricted personnel files to make the briefing more complete. A permission boundary may properly limit the answer. Access controls also apply to search results, titles, summaries, caches and logs.

The same question, with a more useful response

After preparation, the agency evaluates the assistant separately from the information environment. The following is an illustrative response for a user authorized to see the cited project material:

The approved target opening is December 1, according to the director’s opening-date decision, decision reference RIV-DEC-02. The November 1 date belongs to the earlier relocation schedule.

The facilities inspection is complete, as recorded in facilities report RIV-FAC-017, revision 2. That does not establish overall readiness. IT acceptance ticket RIV-IT-031 remains pending in the project information available for this assessment.

The proposed contract modification in the procurement file is unsigned. It does not demonstrate authorization for the proposed work. Acquisition must resolve its status through the responsible contracting official.

I cannot establish the remaining staffing condition from the information available to this account. The project coordinator should obtain an approved readiness confirmation through HR. I am not disclosing protected personnel information.

The director retains the opening decision under the agency’s stated delegation. This briefing does not authorize opening or substitute for the required acceptance and approval actions.

These references are fictional labels, not a prescribed identifier syntax. An actual response should provide usable citations to the supporting sources, identify its assessment date and limitations, and distinguish evidence from conclusions. If the available sources conflict or cannot support a conclusion, the answer should make that uncertainty visible and route the issue to the responsible office.

A different model may still make an error. The agency must evaluate retrieval, interpretation, citations and permission handling for the actual system and use case. A prepared information environment is a foundation for those checks, not a guarantee of AI accuracy or permission for autonomous decisions.

Preparing the environment while the office keeps operating

Riverton does not stop work during preparation. The agency discovers the current environment, identifies authority and responsibilities, designs its shared architecture and prepares the existing platforms while staff continue authorized operations.

Records and information classification follow the business purpose and applicable obligations. A workforce communications program explains what is changing, why shared information must support machine use, where employees will work and when the new arrangements will take effect. Training and a practice period let staff find problems before the transition.

At the agreed cutover, the agency prioritizes active project information and the supporting history needed to use it responsibly. “Active first” does not mean “active only.” Required records, dependencies, legal holds and historical evidence remain protected. The agency documents where information outside the active environment remains and how authorized staff can obtain it.

The responsible offices assess the prepared information, remediate gaps and verify the declared scope. AI evaluation then tests the proposed use against that environment. During ongoing operations, ownership, approvals, access and retention remain managed as information changes. Historical holdings receive a separately planned assessment; their inactivity does not authorize disposal.

How the scenario connects to the checklist

The Riverton case can recur throughout the guidance series. Each example illustrates a business need, a suggested approach and evidence an organization could inspect. It does not prescribe a proprietary technical method.

On smaller screens, scroll the table horizontally to view every column.

Checklist group	Riverton example
R01 — Identity	Distinguish the facilities report, its revisions and distributed copies.
R02 — Authority	Identify who approves the opening and who can authorize contract actions.
R03 — Provenance	Retain supported authorship, approval and change history.
R04 — Relationships	Connect the briefing to the relevant project sources without treating proximity as proof.
R05 — Time	Distinguish the earlier November plan from the approved December target.
R06 — Records	Apply actual schedules, holds and preservation obligations to project information.
R07 — Interoperability	Keep source references and necessary context usable across participating systems.
R08 — Security	Enforce access restrictions, including for protected HR information.
R09 — Retrieval	Support the briefing with usable citations and explicit evidence gaps.
R10 — Governance	Assign owners to unresolved issues and recheck material changes.
S01–S04 — Scope	Declare the Riverton decision, included information and assessment boundaries.
T01–T10 — Transition	Prepare platforms and staff, manage cutover and assess historical holdings.
AI01–AI03 — AI evaluation	Evaluate the intended assistant and use case separately from information conformance.
V01–V04 — Assessment	Retain evidence, exceptions, corrective actions and the limits of any conformance claim.

Start with a decision the organization needs to support

An organization can apply this approach to a service launch, policy change, acquisition milestone or office relocation. Define the question, identify the responsible officials and establish what evidence is needed. Prepare a manageable scope across the existing systems, then verify both the information arrangements and the proposed AI use.

The shift is from information that makes sense mainly to its individual keeper toward information that authorized people and machines can use within a governed enterprise environment. The organization becomes less dependent on personal memory while retaining accountable human authority.

Read the EICARS framework and the persistent artifact identity guide for the standard and the first implementation example. EICARS is a GovKM-proposed public draft, without external accreditation or government endorsement.

Government Authority and References

References checked November 5, 2026. The eCFR pages displayed Title 36 currency through November 3, 2026; eCFR is authoritative but unofficial. The mappings below describe relevant public authority, not an endorsement of this scenario or EICARS. Agency-specific delegations, schedules, orders, security requirements and other applicable law must be added for a real organization. This section is not an exhaustive compliance determination.

• NARA — 36 CFR 1220.34. Assigning records responsibility, integrating records management into business processes, training and evaluation support the scenario’s shared governance. Regulation; mandatory for federal agencies within its scope.
• NARA — 36 CFR 1222.26. Recordkeeping arrangements address record-copy responsibility, related records and retrieval. Regulation; mandatory for covered federal records. A convenient project copy does not automatically replace the designated record copy.
• NARA — 36 CFR 1236.10, 1236.12, 1236.14 and 1236.20. These provisions support electronic-record controls, system design, migration preservation and recordkeeping capabilities. Regulation; mandatory for covered federal agency records and systems. They do not require a single repository or prescribe the scenario’s AI design.
• NARA — 36 CFR 1226.10–1226.20. Approved disposition authorities and applicable exceptions govern records treatment. Regulation; mandatory within scope. An active-information cutover is not a disposal authority; retention extensions also have limits.
• U.S. Access Board — Revised Section 508 Standards. Accessibility remains a design constraint for covered federal ICT, subject to the standards’ scope and exceptions. These requirements do not become optional because information is prepared for AI.
• NIST — AI Risk Management Framework. Voluntary guidance supporting contextual evaluation and management of AI risks. It is not a certification of this scenario, a guarantee of model performance or an independent source of permission to deploy an AI system.

The agency’s fictional opening delegation, HR attestation, transition stages and checklist mapping are illustrative GovKM recommendations, not requirements imposed by these references. Actual privacy and security obligations depend on the data, system, organization and use. A real procurement must additionally establish its governing acquisition authorities and current agency implementation.