AI Audit Exchange
Go back

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

Importing CRAClock Evidence Into an Audit Room

What is conformity-timing evidence?

Conformity-timing evidence is the deadline and timing material produced by CRAClock and imported into AI Audit Exchange rooms — imported read-only and unchanged, SHA-256 sealed at intake, and recorded in the manifest under the CRAClock source label. The Exchange never generates conformity evidence packs or timing records itself; it preserves CRAClock's output as part of a room's multi-source record.

What timing evidence contributes to an audit

Every audit is partly an argument about time: what was due when, what was known when, whether action preceded or followed obligation. Timing material produced by CRAClock gives that argument a system-generated spine inside the room — records of conformity timing as the producing product tracked it during the period. Auditors use such records to anchor chronology questions that otherwise dissolve into competing recollections: when a milestone was assessed, how a deadline was being tracked while it approached. As with all suite evidence, the authority comes from production in the ordinary course; a timing record created by the tracking tool during the period outweighs any timeline composed afterwards, however elegant the slide.

The import routine, tuned for timing material

Import CRAClock exports on the room's monthly circuit, and additionally whenever a timing event completes — an assessment, a milestone review — so the record of the event lands in the room near the event itself. Confirm manifest entries as usual: CRAClock badge, format, size, hash, import date. Resist consolidating timing exports into a single year-end chronicle: a merged chronicle is a derivative document no product produced, and it destroys precisely the property timing evidence exists for — the grain of when each record was made. Parts stay parts; the manifest supplies the chronology when read in import-date order. The unchanged rule is detailed in how to import evidence.

Chronology questions auditors ask

Expect the auditor to use timing artifacts to cross-examine the rest of the room. A decision record dated after a milestone the timing record shows as assessed — does the sequence make sense? A freshness flag elsewhere in the room — does the timing record explain the gap or deepen it? This cross-reading is healthy and is precisely why multi-source rooms outperform single-source folders: the sources corroborate or challenge each other inside one sealed record. Prepare by performing the cross-read yourself in the readiness review: pick three timing artifacts and check the room's other sources against the chronology they imply. Discrepancies found by you are tasks; discrepancies found by the auditor are findings.

Timing evidence across products and regimes

CRAClock artifacts sit in the manifest alongside ReviewDesk, CompanionGuard and ProvenanceGuard entries, and the source column keeps the division of labour visible: decisions, safety, provenance, timing — four products, four testimonies, one room. The same timing exports can be filed into both an SB 1119 room and a CPPA room where both engagements run, each room sealing its own copy. Timing questions differ by regime — broader accountability chronology in one, certification-cycle chronology in the other — but the artifacts' contribution is constant: contemporaneous, badged, verifiable dates that other evidence can be arranged against. In rooms where timing is the thinnest source, a small count is normal; plausibility, not volume, is the test.

When timing records are thin or missing

Some organisations adopt timing tooling late, or track deadlines outside any product for stretches of a period. The room's honest handling mirrors every other gap: file what CRAClock produced from adoption onward, note the adoption and any pre-tooling period in the thread with dates, and file the organisation's own timing documents — plans, milestone sign-offs — as direct uploads badged as such. What never helps is a reconstructed chronology uploaded as though it were system output. Timing evidence is the source where backfill temptation runs highest, because everyone believes they remember the chronology correctly. The room's design assumption is that memory is not evidence; contemporaneous records are. File the true, thinner record and let its honesty argue for the rest of the room.

Freshness and the moving clock

Validation flags artifacts recorded more than 365 days before the run as stale, and timing evidence gives that rule a special case: by nature, timing records describe moments that recede. Read CRAClock flags as prompts to confirm the timing line reaches the present — the latest milestone assessment, the current cycle's tracking — rather than as defects in old records. A timing source whose newest artifact is old means the tracking went quiet, which is itself the finding-shaped fact the review should surface. Keep the line alive with the same monthly circuit that feeds every other source, and the room's chronology never has an unexplained terminus.

Five actions to take

  1. Import CRAClock exports monthly and at every completed timing event — contemporaneity is this source's authority.
  2. Never merge timing exports into a chronicle; import parts as produced and let the manifest order them.
  3. Cross-read timing artifacts against the room's other sources in every readiness review.
  4. File timing exports into both regime rooms where both engagements run.
  5. Adopted the tool late? File from adoption, note the pre-tooling period in the thread, and badge organisational timing documents as direct uploads.

Worked example

A fictional device-cloud firm, Granite Peak Devices, files CRAClock exports on its monthly circuit: 9 artifacts across its CPPA room's period — fewer than its ReviewDesk count by design, each tied to a timing event. In the readiness review, the team cross-reads: a milestone assessment dated in the timing record precedes a cluster of decision-record imports by eleven days, exactly the sequence the engagement narrative claims. One discrepancy surfaces instead — a timing artifact implies an assessment the safety record dates a week later.

The discrepancy resolves innocently (the assessment's planning record vs its completion record, both present once the team looks), and the resolution is noted in the thread with both artifacts cited. When the auditor performs the same cross-read — auditors always cross-read timing — she finds the note waiting and spends her question on something new. That is timing evidence earning its keep: not by being voluminous, but by being contemporaneous, checkable, and already reconciled.

Frequently asked questions

Does AI Audit Exchange generate conformity or timing packs?

No. Conformity-timing material is produced by CRAClock and imported unchanged. The Exchange never generates conformity evidence packs, notices, decision traces, SBOMs or safety records — it hosts the suite's output.

Our CRAClock count is much smaller than other sources. Is that a problem?

Not inherently. Timing evidence is event-grained, not volume-grained. The tests are plausibility and continuity: events across the period, no unexplained silent stretches, the line reaching the present.

Can we consolidate a year of timing exports into one summary file for the room?

Do not. A summary is a derivative no product produced. Import the parts as produced; if an organisational summary helps readers, file it additionally as a badged direct upload and let it sit beside — never instead of — the source records.

We tracked deadlines in spreadsheets before adopting CRAClock. How is that filed?

As direct uploads, badged as the organisation's own documents, with the adoption of CRAClock noted in the thread. Organisational records are legitimate evidence in their own voice; they must not wear the product's badge.

How does timing evidence help in an SB 1119 room specifically?

It gives the examination a contemporaneous chronology to arrange other evidence against — what was assessed, tracked and due, as recorded during the period rather than reconstructed for the audit.

Keep reading

All AI Audit Exchange guides · Auditor directory · About AI Audit Exchange · Security · Pricing · AI Audit Exchange home · Previous: Importing CompanionGuard Evidence Into an Audit Room · Next: How to Answer Auditor Evidence Requests Faster

Common AI Audit Evidence Mistakes (and Their Fixes) · AI Audit Evidence for Small Companies: The Minimum Viable Discipline · How to Keep Audit Evidence for Ten Years (Practically)