Article 12, clause by clause.

High-risk systems shall technically allow for the automatic recording of events (logs) over the lifetime of the system.

The SDK records every model call, tool call, and agent step from inside your process — automatic, not manual documentation. Capture is a single import, or OpenTelemetry if you already emit spans.

Logs shall enable identification of situations that may result in the system presenting a risk, or a substantial modification.

Policy rules evaluate on every gated tool call and record the decision — allowed or blocked — as part of the run. A blocked action carries the rule that blocked it, so a risk situation is a queryable event rather than something inferred from prose.

Logs shall facilitate post-market monitoring (Art. 72).

Runs aggregate into a period report — volumes, error rates, policy evaluations and blocks, redaction counts — computed from the database, not sampled, so the report's numbers are the data's numbers.

Logs shall enable monitoring of operation by deployers (Art. 26(5)).

Per-agent coverage reconciles the agents you declared against the ones actually reporting: declared but never instrumented, reporting then gone silent, or running while absent from your register.

Logs shall include the period of each use, the reference database checked against, the input data, and the identity of the persons verifying results.

Start/end timestamps, exact inputs, retrieved context, and tool results are captured per run. Human verification is captured where an approval gate is used. If your process has a reviewer step outside Runback, that identity isn't in our record — record it yourself.

Logs shall be kept for a period appropriate to the intended purpose, at least six months.

Retention is per plan, enforced by a scheduled sweep: Enterprise unlimited, Pro 90 days, Scale and Growth 60, Starter 30, Community 7, with regulated verticals raising the floor (healthcare 180 days). Meeting the six-month obligation therefore means Enterprise, a vertical floor that covers it, or self-hosting with your own retention. Legal hold suspends deletion for runs under a preservation obligation, and if the holds table cannot be read the sweep is skipped — the failure favours keeping data.

Logs must be reliable as evidence. The Act does not use the word 'tamper-proof', but a record that can be edited without anyone noticing is not evidence of anything.

Every run is hash-chained and signed; each org's runs are sealed into an append-only ledger with signed checkpoints. Checkpoints are additionally time-stamped by independent RFC 3161 authorities and published to a public append-only log — so the record is not merely signed by us, it is anchored outside our control.

Risk management system, technical documentation, quality management system.

Runback supplies evidence that feeds these; it does not produce them. A conformity assessment is an organisational process. Any vendor claiming to deliver Article 9 or 17 compliance as a product feature is overselling.