AI Audit Exchange
Go back

Guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

What Is Source Badging on Audit Evidence?

What is source badging?

Source badging is the intake labelling of artifacts on AI Audit Exchange: each artifact's manifest entry records a source label — the generating product for suite imports, which are imported read-only and unchanged, or the direct-upload designation for auditee-filed material. The badge is assigned from the intake path the artifact actually took and is part of the sealed record thereafter.

A label assigned by the path, not by a person

Badges are trustworthy because nobody writes them. The platform knows which door an artifact entered by — the import path from a suite product or the upload path on the room — and the badge is that fact, recorded at intake and carried into the manifest. There is no dropdown to mis-select, no metadata field to optimise, no later editing pass where a badge can be upgraded. This mechanical assignment is the entire design: provenance that depends on human labelling inherits human error and human temptation; provenance derived from the mechanism inherits the mechanism's indifference. When an auditor reads a badge, they are reading the system's memory of an event, not a person's description of it.

What the two badges mean

A product badge — ReviewDesk, CompanionGuard, ProvenanceGuard, CRAClock — asserts that this artifact is that product's own record, imported unchanged: the decision-review system produced this file, the safety system produced that one. A direct-upload badge asserts the artifact is the auditee's own filing: a signed approval, an attestation, a policy document — material no suite product generates. Neither badge is a quality grade. Each is a voice attribution: who is speaking in this file. Examiners weigh voices differently by design — system output testifies about the system; organisational filings testify about the organisation — and badges are what let them do it accurately at manifest speed. The fuller treatment is in direct upload vs suite import.

Badges in the room and in the manifest

In the room, each artifact displays its source on its face, so browsing the evidence is browsing attributed evidence. In the manifest, the source label sits in every entry alongside filename, format, sha256, size, import date and retention note — the provenance column of the room's inventory. That column is a working tool for the owner before it is a comfort for the auditor: filter it and coverage gaps appear (a product absent for a quarter), rhythm appears (imports spread or clustered), and the upload share appears (organisational residue at a sane minority, or a symptom that suite exports are not being filed). Owners who read their source columns monthly rarely meet a provenance surprise in an engagement.

Badges and the Exchange's scope discipline

Badging also enforces the platform's scope lock, quietly and continuously. The Exchange never generates notices, decision traces, crisis-runtime evidence, SBOMs or conformity packs — those are produced by the suite products. A room full of product-badged imports demonstrates that division on its face: the Exchange hosted, sealed and organised; the products produced. If the platform generated evidence, its badge would have to exist, and its absence from the badge vocabulary is the scope lock made visible. When an auditor asks who created a given artifact, the badge answers with the producing product — and the answer is checkable, because imports are held unchanged exactly as that product made them.

Misbadging: how it happens and why it ends careers of rooms

Since badges are mechanical, misbadging requires misrouting: a suite export sent through the upload path (badge: direct upload, contents impersonating product output's authority) or an auditee-made summary dressed as an export and imported (rarer, worse). Both are filing errors with credibility consequences far beyond their content, because a single provenance failure re-prices every badge in the room — if one label lied, the auditor must verify all of them, and the room's core convenience dies. The prevention is a filing rule your team can hold in one sentence: a file travels the path of its true origin, always, and corrections are made by refiling correctly and noting it in the thread — never by relabelling. The room's honesty is a common-pool resource; every filing either maintains it or spends it.

Badges across time: successors and strangers

A badge's longest service begins after the engagement ends. The successor auditor reading the room next cycle, the diligence reviewer in year five, the future colleague reconstructing why a file exists — each reads badges as the artifact's first fact, before content. Because badges are mechanism-assigned and manifest-preserved, they survive every handover without translation. Organisations underestimate how much of an audit's cost is orientation: new readers learning what things are. Badging front-loads that orientation into the record itself. It is a small feature with a long shadow — most of evidence practice is.

Five actions to take

  1. Route every file by its true origin: product exports through import, organisational material through upload.
  2. Read the manifest's source column monthly for coverage, rhythm and upload share.
  3. Never relabel — correct a misrouted file by refiling it properly and noting the correction in the thread.
  4. Explain badges in your brief: the auditor should know the room's provenance model before the first session.
  5. Treat every filing as maintaining a common resource: the room's provenance credibility.

Worked example

A fictional telehealth firm, Sonoran Telehealth Partners, prepares its room of 66 artifacts and reads its own source column first: ReviewDesk 24, CompanionGuard 17, ProvenanceGuard 15, CRAClock 3, direct uploads 7. The CRAClock count is the finding — the product operated all year but its exports were filed only in one quarter, because its export step lived in a different team's runbook. The gap is closed for the current quarter and the runbook amended before any auditor sees the room.

When the auditor does sample, her coverage note quotes the same column back: sources complete after a self-identified filing gap was corrected in-period. The badges did double duty — they told her what each file was, and they told the owners what their own filing had missed. That second duty is the one teams should exploit monthly; it costs a glance and returns the room's provenance health as a single column of facts.

Frequently asked questions

Who assigns the badge — me or the platform?

The platform, mechanically, from the intake path the artifact actually took: import path yields the producing product's badge; upload path yields the direct-upload badge. There is nothing to select and nothing to edit afterwards.

Is a direct-upload badge a mark against the file?

No. It is an attribution: the organisation filed this itself. Approvals, attestations and policies properly carry it. What damages a room is a badge that does not match a file's true origin.

Can a badge be changed if a file was misrouted?

Badges are not edited. Refile the artifact through its correct path as a new entry and note the correction in the room's thread; the record then shows both the error and its honest repair.

Why is there no 'AI Audit Exchange' badge for generated evidence?

Because the Exchange generates none of the evidence types: notices, decision traces, safety records, SBOMs and conformity packs are produced by the suite products and imported. The badge vocabulary mirrors that scope lock.

How do badges relate to the hash seal?

They are complementary intake facts: the badge says where the artifact came from; the seal proves the artifact has not changed since it arrived. Provenance plus integrity is the room's whole trust model in two mechanisms.

Keep reading

All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: Version Control for Audit Evidence Without Editing the Past · Next: Importing ProvenanceGuard Evidence Into an Audit Room

Importing ReviewDesk — ADMT Decision Review Evidence Into an Audit Room · Importing CompanionGuard Evidence Into an Audit Room · Importing CRAClock Evidence Into an Audit Room