EU AI Act · Article 12 · Evidence Cron

Periodic, Receipted Art-12 Evidence Bundles

A weekly tick gathers the window's execution and decision receipts already produced by the suite's tools, maps them into an OSCAL assessment-results document and an ISO/IEC 24970 log export, and anchors the bundle. Buyers preparing for the Aug 2 enforcement window get a periodic evidence artifact they can independently verify. It is not a certificate of conformity.

Weekly Cron OSCAL + ISO/IEC 24970 Anchored Bundle Zero PII
๐Ÿ”’ All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data โ€” use synthetic or anonymised inputs only.
Evidence, not certification: the export re-expresses what the underlying execution and decision receipts already prove. It mints no new findings and asserts no new trust claims. It does not imply the resulting bundle certifies AI-Act conformity. It is receipted evidence a buyer can verify and feed into their own conformity assessment.
How It Runs

Weekly tick, four steps

Runs on the same shared weekly cron substrate as the Continuous Reserve Watch. Every fire is independent and byte-replayable.

1
Cron fires
A Cloudflare Worker scheduled trigger wakes on a weekly cadence and emits a CloudEvents envelope marking the tick.
2
Gather the window's receipts
The tick collects the execution and decision receipts already produced by tool calls in the preceding window. It generates nothing new, only gathers what already exists.
3
Map to OSCAL and ISO/IEC 24970
The gathered receipts are mapped, via the live EXPORT-1 mapping code, into an OSCAL assessment-results document and an ISO/IEC 24970 log-export document. Both mappings re-express existing receipt data; neither adds a new trust claim.
OSCAL: pinned releaseISO/IEC 24970: draft-pinned
4
Anchor and emit
The bundle is anchored through the shared anchor lineage and wrapped in a CloudEvents envelope for downstream consumers.
Related

Explore adjacent tooling