How to Redact an AI Workspace Without Breaking Its History

Removing a private file can leave a shareable copy that looks complete but no longer explains why an artifact changed. Copying everything preserves context at the cost of exposing material that never belonged outside the original workspace. Create a redaction map before making the copy. Replace private details with stable, safe labels and record what kind of material was omitted. This decision maps to “The right context for this job.” The visible component behavior is a purpose-limited set that includes useful material and excludes details the audience should not receive.

Published 2026.08.09 · 3 minute read

Preserve structure without preserving secrets

A redaction map should identify:

the original artifact's role;
the safe label used in the copy;
the relationships that must remain visible;
the reason content was removed;
the person responsible for reviewing the shareable set.

Do not substitute invented facts for removed details. A label such as private-source-a preserves a reference without pretending to disclose its contents.

Keep a truthful inventory of the copy

The NIST AI Risk Management Framework treats documentation and governance as parts of managing AI risk. W3C PROV-O can express artifact relationships through safe identifiers. RFC 8493 defines manifests and payload inventories for packaged file sets.

Those references support a clear distinction between the original set and its redacted copy. The copy should say that an omission occurred and which relationship remains, without exposing the removed detail.

Redact for a named audience

This method fits work that must be shared beyond the people allowed to see the original sources. It is unnecessary when the audience and permissions have not changed.

Redaction is not migration. It creates a purpose-limited copy. Verification is still needed afterward to confirm that every intended safe artifact arrived unchanged.

Move through the surrounding decisions

Use Keep AI Work in Files You Control to establish the owned source set. Record Provenance for AI-Assisted Work identifies the relationships that redaction must preserve. Verify an AI Workspace Copy checks the resulting file set.

Redact without inventing replacements

The synthetic material contains no private customer facts, so the redaction lesson is to preserve roles without inventing concealed details.

Decision to make: Decide whether to make a redaction map before creating a shareable copy.