Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Importing ProvenanceGuard Evidence Into an Audit Room
Short answer
ProvenanceGuard evidence enters an audit room the way all suite evidence does: export from ProvenanceGuard, import the export unchanged, and the room seals it with SHA-256 at intake, stores it immutably and badges it 'ProvenanceGuard' in the manifest. File monthly so provenance records cover the whole period — what content was generated, under what attestations, across every month the audit will sample. The Exchange never creates provenance records itself; it preserves the ones ProvenanceGuard produced, with their origin on their face.
What is provenance evidence?
Provenance evidence is the record of generated content's origin and attestations produced by ProvenanceGuard and imported into AI Audit Exchange rooms. Imports are held read-only and unchanged, sealed at intake, and recorded in the manifest with the ProvenanceGuard source label, the artifact's format, hash, size, import date and any retention note carried from ProvenanceGuard's own policy.
What ProvenanceGuard evidence testifies to
Provenance records answer a question every AI audit eventually asks about generated content: where did this come from, and what was attested about it at the time? The producing product's records carry that testimony as system output — generated in the ordinary course, not composed for the auditor. Inside the room, these artifacts sit alongside decision records, safety evidence and conformity material as one of the four suite voices. Their evidentiary posture is the same as every import's: the file is the product's record, sealed at the moment the room received it, and any later copy can be tested against the seal. An auditor weighing provenance questions works from these badges first, because the badge is what separates the product's testimony from the auditee's account of it.
The import routine for provenance records
Export from ProvenanceGuard on the room's monthly rhythm and import each export untouched into the room matching its regime and period. Confirm each landing in the manifest: ProvenanceGuard badge present, format and size sane, hash recorded, import date current. Where ProvenanceGuard operates in bursts — campaigns, releases, content programmes — let the import rhythm follow the production rhythm rather than flattening it into a year-end bundle; the manifest's import dates should sketch the shape of the work itself. If an export is found defective, the correction path is the platform-wide one: fix the configuration or source in ProvenanceGuard, re-export, import the replacement as a new artifact, and note the supersession in the room's thread. The general workflow is in how to import evidence.
Coverage questions auditors ask provenance evidence
Expect sampling across time rather than across volume: provenance practice is judged by its consistency, so an auditor draws records from early, middle and late in the period and tests whether the attestations' story holds throughout. Gaps get questions in proportion to their position — a silent quarter inside an otherwise continuous run reads as a process interruption, and it may well have been one (a migration, a paused programme). Note interruptions in the thread when they happen; a contemporaneous note converts a finding-shaped silence into a documented event. Also expect pairing questions: provenance records read alongside the content programmes they describe, so keep your direct uploads that document those programmes dated and filed in the same periods.
Freshness and provenance
Validation's 365-day freshness rule applies to provenance artifacts as to all others, with a provenance-specific reading. Old provenance records are usually historical substance rather than staleness problems — they testify about content generated at their time, and ageing does not impeach them. The freshness question for this source is not 'are the records recent?' but 'does the record run reach the present?' — an unbroken line from period start to period end. Read flags here as continuity checks: a stale flag on the newest ProvenanceGuard artifact in the room is the signal that matters, because it means the line stopped. Keep importing while content is generated, and the line — and the room's testimony — stays alive.
Provenance across the two regimes
The same ProvenanceGuard exports can serve an SB 1119 room and a CPPA room, filed into each separately, because each audit's record must be self-contained. The readings differ by regime: an SB 1119 examination weighs provenance as part of the system's overall accountability record; a CPPA cybersecurity examination may weigh the integrity and attestation machinery itself as a security control. Either way, the room's contribution is identical — sealed, badged, manifested artifacts whose origin nobody has to take on faith. File into both rooms on the same monthly circuit and the marginal cost of the second room's completeness is a few minutes — the cheapest cross-regime insurance in the programme.
When provenance evidence is missing
If your organisation generated content in the period but holds no ProvenanceGuard records for stretches of it, the honest sequence is: say so in the room's thread with dates and reasons, file what exists with its true badges, and start the import rhythm from now. Do not backfill by manufacturing summaries and uploading them as if they were the product's voice — a direct upload labelled as the organisation's own retrospective account is legitimate supporting material, clearly badged; the same document wearing import clothing is a provenance fraud in a room whose entire purpose is provenance. Auditors forgive gaps explained contemporaneously far more readily than completeness performed retrospectively. The room is built to reward the first and expose the second.
Five actions to take
- Import ProvenanceGuard exports monthly, untouched, into the room matching regime and period.
- Confirm every import in the manifest: badge, format, size, hash, current import date.
- Note production interruptions in the thread when they occur — silence explained early is a document, not a finding.
- File the same exports into both regime rooms where both audits will read provenance.
- Keep the record line unbroken to the period's end; the newest artifact's freshness is this source's vital sign.
Worked example
A fictional media-technology firm, Agave Media Works, generates AI-assisted content year-round and files ProvenanceGuard exports monthly: 34 artifacts across its SB 1119 room's period, import dates forming an unbroken rhythm. In August the manifest shows no ProvenanceGuard import — the thread, checked first, explains it contemporaneously: a platform migration paused generation for five weeks, and the August note was written in August.
The auditor samples 6 provenance artifacts across the year — 6 seals verified — and asks one question about the August silence, which the thread answers before the meeting ends. The same exports, filed in parallel into the firm's CPPA room, serve that examination without a single extra export being produced. One product's records, two rooms' completeness, zero reconstruction: the import discipline compounding exactly as designed.
Frequently asked questions
Does AI Audit Exchange generate provenance records?
No. Provenance records are produced by ProvenanceGuard and imported unchanged. The Exchange hosts, seals and badges them; it never generates provenance evidence, notices, decision traces or the other suite evidence types.
How often should ProvenanceGuard exports be imported?
Monthly, or on the rhythm the content work itself follows. The manifest's import dates should reflect real production cadence across the whole period.
Our provenance tooling arrived mid-period. What do we file?
File from adoption onward, and note the adoption in the room's thread with its date. Partial coverage with an honest start date reads as a true record; a silent gap reads as an omission.
Are old provenance records a freshness problem?
Usually not — they testify about their own time. The signal to watch is continuity: if the newest provenance artifact is stale, the record line has stopped, and filing should resume.
Can the same export serve both our regime rooms?
Yes. Import it into each room separately; each room seals its own copy at its own intake and manifests it independently, keeping both audit records self-contained.
Keep reading
All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: What Is Source Badging on Audit Evidence? · Next: Importing ReviewDesk — ADMT Decision Review Evidence Into an Audit Room
Importing CompanionGuard Evidence Into an Audit Room · Importing CRAClock Evidence Into an Audit Room · How to Answer Auditor Evidence Requests Faster