AI Data Guard

The product runs in the window beside this column, and every control in it works.

Step 8 of 10

The examiner evidence package

One artifact, dated and print-styled: the bank’s charter and who supervises it, the obligations that follow from it, control mapping by data class with its citation, the policy version history with who proposed and who approved each one, the monitoring evidence, sampled provenance chains, the accuracy record with its sampling rule and what it does not measure, every override with the justification as it was written, and a custody statement saying what this demo holds and what it does not. Assembled from the same event log the console reads, over the same window.

Examiner-ready is the promise the site makes twice, and this is what it has to mean — every figure in the package ties to the events under it, and section 4 carries the workbook chain from the step before this one, printed. Section 4 also says how its chains were chosen: a chain is printed only if every stored span comes back from the detection engine at the same offsets, and the events that carry a seeded identifier pairing instead are counted there rather than quietly left out.

Look atSection 4, and the event id in it: the same movement you just drilled, in the document the examiner is handed.