PacSpace
Talk to us
Government · Requirements

What federal policy already asks for, in its own words.

The government already asks to monitor, review and keep what its AI systems do. Today it does that through the operator's own records.

The open question

NIST is already asking it.

NIST's National Cybersecurity Center of Excellence asks in a February 2026 draft: “How can we ensure that agents log their actions and intent in a tamper-proof and verifiable manner?”1

For what an agent did, the record is one answer. It is written as the agent acts, committed where no one can change it, PacSpace included, and checkable by anyone given the link.

Oversight of AI

Monitoring, accountability and traceability.

OMB M-25-21 · High-impact AI2

“Agencies must ensure human oversight, intervention, and accountability suitable for high-impact use cases.”

Where each action and each approval is written as it happens, whether an approval was recorded before the system acted is on the record for oversight to check.

OMB M-25-22 · Buying AI3

“Contractual terms must provide the contracting agency the ability to regularly monitor and evaluate” an AI system's performance, risks and effectiveness.

The agency monitors from a record it can check itself: what the system did, unchanged since it was committed, opened from a link the contract can require, with no data call each time.

DoD AI Ethical Principles · Traceable4

“transparent and auditable methodologies, data sources, and design procedure and documentation”

Each output can carry the model version and settings the operator recorded, so the version recorded in the field can be checked against the version recorded at test.

Scope: OMB's two memos do not cover AI used as a component of a National Security System, and M-25-21's minimum practices do not apply to the intelligence community. What this page doesn't claim

Audit records

Audit information anyone can check for changes.

NIST SP 800-53 AU-9 · SP 800-171 3.3.8, in CMMC Level 25,6,7

“Protect audit information and audit logging tools from unauthorized access, modification, and deletion”

A committed record can't be modified by anyone, PacSpace included, and a modified copy fails the check. Access to your logs, and their deletion, stay with your system's own controls.

CISA, NSA and partners · AI agent services8

“Use multiple independent monitoring systems that cross-validate agent reports and system logs.”

A cross-check needs one account the agent can't reach: what was committed as it acted. Your monitoring raises the alarm. The record gives it a signal the machine can't erase. The change shows.

Keeping records

Records that last past the work.

FAR 4.703 · Contractor records9

Contractors must make records, including computer data, available for audit for “3 years after final payment”.

Any copy kept for audit still checks against what was committed, after final payment and after the contract changes hands.

NARA AC 11.2026 · AI and federal records10

Federal records include “Audit trails an agency captures and uses to conduct official business, such as investigations.”

The agency keeps its own copy of a record and can check it against what was committed for as long as its schedule keeps it.

What this page doesn't claim

The record answers part of each rule, never the whole of it.

PacSpace is not a compliance product and doesn't make a system compliant or authorized. What a record satisfies on a given system is for the program, its assessor and its counsel.

OMB's two memos do not cover AI used as a component of a National Security System, and M-25-21's minimum practices do not apply to the intelligence community. The controls, the records rules and the guidance on AI agents each say where they apply.

The operator still chooses what to write, the same limit every log has. What it gives up is changing the record afterward. If writing stops, the gap shows: the records on either side put a start and an end on it.

Talk to us

Bring the case you think breaks it.

We would rather be evaluated by use than by description. Talk to us and we'll put you in a live environment: commit a record, do your best to change it, then check it yourself, with us out of the loop. The change shows.

The record must exist.