The Regulatory
Horizon

Every one of these rules creates a duty to hold a record.

None of them defines what makes a record believable.

Below is each instrument, its date, and the operative text quoted from the primary source — followed by what that text does not say. The omissions are not oversights. They are the same omission, four times.

01The first clock
14 JAN 2027EU Machinery Regulation (EU) 2023/1230 · repeals Directive 2006/42/EC the same day, with no transition

AI enters machinery safety law by name.

What brings AI into scope
Annex I, Part A, point 5
“Safety components with fully or partially self-evolving behaviour using machine learning approaches ensuring safety functions.”
Part A is the mandatory third-party conformity-assessment list. Point 6 extends the same treatment to embedded systems never independently placed on the market.

Note what is absent. Article 3 defines neither “self-evolving behaviour” nor “machine learning” nor “artificial intelligence” nor “autonomy.” These terms carry legal weight in the Annexes while remaining undefined in the instrument that uses them.

What must be recorded
Annex III, 1.2.1 — third block, point (b)
“recording of data on the safety related decision-making process for software based safety systems ensuring safety function including safety components … is enabled and that such data is retained for one year after its collection, exclusively to demonstrate the conformity of the machinery or related product with this Annex further to a reasoned request from a competent national authority”
The block applies to control systems “with fully or partially self-evolving behaviour or logic that are designed to operate with varying levels of autonomy.”
Annex III, 1.2.1 — second block, point (f)
“the tracing log of the data generated in relation to an intervention and of the versions of safety software uploaded after the machinery or related product has been placed on the market or put into service is enabled for five years after such upload”
Retention is asymmetric: five years for the software-version and intervention trail, one year for the safety decision-making data itself.
Article 10(3)
“Manufacturers shall keep the technical documentation and the EU declaration of conformity at the disposal of the market surveillance authorities for at least 10 years …”
And “the source code or the programming logic … shall, upon a reasoned request, be made available to the competent national authorities” where needed to check compliance.
What it does not define

The Regulation says the recording is enabled and the data is retained, and stops. There is no standard for tamper-evidence, no requirement that the record be complete, no declared scope, and no method by which an authority — or a claimant, or an insurer — could establish that what was produced is what was recorded.

The party holding the record is the party whose conformity it evidences. Nothing in the instrument addresses that.

It does not say
tamper-evident
It does not say
complete
It does not say
verifiable
It does not say
scoped
Leaves you holding

A statutory duty to record your machine’s safety decisions, two retention clocks, and a production obligation on reasoned request — with no defined way to show that what you hand over is complete or unaltered.

02The second clock
2 DEC 2027EU AI Act, Regulation (EU) 2024/1689, Article 12 · Annex III high-risk systems. Annex I follows 2 August 2028. Article 50 has applied since 2 August 2026.

Logging becomes a legal obligation.

What it requires
Article 12(1) — Record-keeping
“High-risk AI systems shall technically allow for the automatic recording of events (logs) over the lifetime of the system.”
12(2) requires that logging ensure traceability appropriate to the intended purpose — identifying risk situations under Article 79(1) and substantial modifications, facilitating post-market monitoring under Article 72, and supporting deployer monitoring under Article 26(5).
Articles 19 and 26(6) — Retention
Providers keep the automatically generated logs under their control, and deployers “keep the logs automatically generated by that high-risk AI system” — each for a period appropriate to the intended purpose and in any case at least six months.
Financial institutions may maintain these as part of the documentation already kept under Union financial-services law.
Article 50(1) — In force since 2 August 2026
AI systems intended to interact directly with natural persons must be designed so that the persons concerned “are informed that they are interacting with an AI system” — unless obvious from the context.
What it costs

Article 99 sets three tiers.

CeilingFor
€35,000,000 or 7%
of worldwide turnover
Prohibited AI practices under Article 5
€15,000,000 or 3%Breach of operator obligations, including Articles 16, 26 and 50 — the tier Article 12’s record-keeping sits under
€7,500,000 or 1%“The supply of incorrect, incomplete or misleading information to notified bodies or national competent authorities in reply to a request”
Read the third tier again

It is a penalty aimed squarely at producing an incomplete or misleading record for a regulator. The failure has been priced in statute before anyone has defined how to avoid it.

What it does not define

Article 12 requires that events be recorded. It does not say the log must be tamper-evident. It does not say it must be complete, or define what complete would mean. It requires no declared scope, so a produced log cannot be distinguished from a partial one. It provides for verification by no one outside the company holding it.

Leaves you holding

A logging duty satisfied, on paper, by a file your own administrator can edit.

03The third clock
ALREADY RUNNINGSix US state conversational-AI disclosure statutes, 5 November 2025 through 1 July 2027. Two are operative today.

Tell the customer they are talking to a machine.

StateInstrumentEffectivePrivate right of action
New YorkGBL Art. 47, §§ 1700–17045 Nov 2025No — Attorney General only, up to $15,000 per day
CaliforniaBus. & Prof. Code §§ 22601–22606 (SB 243)1 Jan 2026Yes — $1,000 per violation
WashingtonHB 2225, ch. 168, Laws of 20261 Jan 2027No express action; per se Consumer Protection Act violation
OregonOr. Laws 2026, ch. 85 (SB 1546)1 Jan 2027Yes — $1,000 per violation
IdahoIdaho Code §§ 48-2101–2105 (SB 1297)1 Jul 2027Expressly none — $1,000 per violation, $500,000 cap
NebraskaLB 525, §§ 12–181 Jul 2027Expressly none — $1,000 to $500,000
The duty, in their words
New York, § 1702
“An operator shall provide a clear and conspicuous notification to a user at the beginning of any AI companion interaction … at least every three hours for continuing AI companion interactions which states either verbally or in writing that the user is not communicating with a human.”
California, § 22602(a)
“If a reasonable person interacting with a companion chatbot would be misled to believe that the person is interacting with a human, an operator shall issue a clear and conspicuous notification indicating that the companion chatbot is artificially generated and not human.”
Idaho, § 48-2103
“If reasonable persons would be misled to believe that they are interacting with a human, an operator shall clearly and conspicuously disclose that the conversational AI service is artificial intelligence.”
Oregon, Washington and Nebraska impose materially the same duty in their own words, with three-hourly reminders and, in Washington, hourly reminders for minors.
What none of them requires

Six for six: not one requires any record that the disclosure was made.

No log. No receipt. No timestamp. No retention period. No per-user or per-session documentation of any kind. Every one of these statutes mandates the act of disclosure and is silent on evidencing it.

The only record-adjacent duties in the entire set are three annual aggregate crisis-referral reports — California from July 2027, Oregon, and Washington. They count suicide and self-harm referrals. None of them records an AI-identity disclosure.

Leaves you holding

In California and Oregon, statutory damages of $1,000 per violation and a private right of action — against a claim that turns entirely on what you can show about a conversation your machine had, with no statute anywhere telling you to keep it.

04The precedent

Not a clock. The receipt.

The rules that produced more than two billion dollars in recordkeeping penalties are the oldest and most heavily enforced of the four — and they are the clearest demonstration of the gap.

The duty
17 C.F.R. § 240.17a-4(b)(4)
“Originals of all communications received and copies of all communications sent (and any approvals thereof) by the member, broker or dealer (including inter-office memoranda and communications) relating to its business as such …”
Preserved, per 17a-4(b), “for a period of not less than three years, the first two years in an easily accessible place.” Rule 204-2(a)(7) imposes the parallel duty on investment advisers, retained five years from the end of the fiscal year of the last entry. FINRA Rule 4511(b): at least six years where no other period is specified.
SEC Director of Enforcement, 6 November 2024
“Since December 2021, that initiative has resulted in charges against more than 100 firms and over $2 billion in penalties.”
That remains the last cumulative tally the SEC itself has published. The most recent SEC action was 13 January 2025 — twelve firms, $63.1 million. Enforcement continued at FINRA: an accepted settlement dated 2 February 2026 fined a member $125,000 where supervisors knew associated persons were conducting securities business over personal email, and hundreds of business-related communications were lost.
Where the gap is
17 C.F.R. § 240.17a-4(f)(2)(ii)
“Verify automatically the completeness and accuracy of the processes for storing and retaining records electronically”

The completeness verified is the completeness of the process, not of the corpus. The rule asks whether the archive faithfully stored what it was handed. It says nothing about whether everything that should have been captured was.

That gap is the entire two billion dollars. The firms had compliant archives. The messages never entered them.

The finding

The rule cannot detect its own blind spot — and no amount of compliance with it would have.

And since the 2022 amendments, tamper-evidence is optional. Rule 17a-4(f)(2)(i) is disjunctive: a system must maintain “a complete time-stamped audit trail” of all modifications and deletions, or preserve records “exclusively in a non-rewriteable, non-erasable format.” Before 2022, the second was the only route.

The audit trail is generated by the same system that holds the records. The regulation asks the system to vouch for itself.

The “designated third party” of 17a-4(f)(3) is an unaffiliated person who can furnish records to regulators if the firm will not. That is a custody backstop, not independent verification. No one outside the record-holder attests that the records are complete or unaltered.

05The void, statute by statute

Every column but the first is empty.

Instrument Requires a record? Defines tamper-evidence? Requires completeness of capture? Requires declared scope? Verifiable by an outsider?
Machinery Regulation
Annex III, 1.2.1
Yes — 1 yr / 5 yr NoNoNoNo
AI Act
Arts. 12, 19, 26(6)
Yes — at least 6 months NoNoNoNo
Six state
chatbot statutes
No — none of them
SEC 17a-4
Advisers 204-2
Yes — 3 yrs / 5 yrs Optional since 2022 Process only No Access only

Two regimes now compel a record of machine conduct with a retention clock attached. Six statutes compel a disclosure and no evidence of it.

The law has finished telling you to keep the record. It has not started telling you what makes one believable.

What a believable record requires →
Sources, all primary, last checked 17 September 2026
EU AI Act

Regulation (EU) 2024/1689, Article 12, Article 19, Article 26, Article 50, Article 99.

Machinery

Regulation (EU) 2023/1230, Articles 3, 10, 51, 54; Annexes I, II and III — EUR-Lex, CELEX 32023R1230.

State statutes

NY GBL Art. 47 · CA SB 243 · WA HB 2225 · OR Laws 2026 ch. 85 · ID SB 1297 · NE LB 525.

SEC and FINRA

17 C.F.R. § 240.17a-4 · § 275.204-2 · FINRA 4511 · FINRA 3110 · SEC Enforcement remarks, 6 Nov 2024 · SEC release 2025-6.

Colorado SB 24-205 previously appeared in counts of this kind. Its disclosure duty was repealed and reenacted by SB 26-189, signed 14 May 2026, and the reenactment removed the duty to tell consumers they are interacting with AI; enforcement had already been suspended by federal court order on 27 April 2026. Tennessee SB 1580 is a prohibition on representing an AI system as a qualified mental health professional, not a disclosure mandate. Neither is counted above.