article 12 record keeping that holds up.

the eu ai act asks for automatic records of what high-risk ai systems do. syen keeps them signed, chained, and verifiable by the people who ask.

what article 12 asks

article 12 of the eu ai act requires providers of high-risk ai systems to build in automatic recording of events over the system’s lifetime. the point is traceability: when an authority, an auditor, or a court asks what the system did, the answer has to come from a record made at the time, not a story told later.

the record, in three asks
  1. 01automatic

    the system records events as it runs. no manual log, no reconstruction after the fact.

  2. 02complete

    the record captures what the system did, so a regulator can trace a decision back.

  3. 03kept

    providers keep the logs available, at least six months under the act, ready for authorities.

where ordinary logs fall short
a log file can be edited

a signed chain cannot. one changed record fails verification at that position.

a rotated log is gone

a chained record detects the gap. nothing drops out silently.

a screenshot proves little

an openssl verification proves the record is the one created at the time.

a vendor dashboard is theirs

your auditor checks your record without access to your systems, or to ours.

independent verification

proof that stands on its own.

every event is signed with ed25519, chained with sha-256, and anchored daily to digicert’s rfc 3161 trusted timestamp authority. the auditor verifies the whole record with openssl.

ed25519 signatures·sha-256 chain·rfc 3161 anchoring·openssl verification
where teams use it

teams running agents under the act keep the agent audit trail on the same chain, and track the regulation itself with regulatory change management. see the governed workflows on the use cases page.