hey PH EU AI Act Article 12 enforcement starts August 2, 2026. high-risk AI operators have to hand a regulator a verifiable per-agent action log. most enterprise stacks today produce a shared pipeline log, not a signed artifact a regulator can take home. Warrant fixes one specific thing: the deliverable. drop a trace JSON, get back a court-document signed PDF in about 60 seconds. each agent action is mapped to a specific obligation clause. the package is signed Ed25519 and anchored to a Bitcoin block via OpenTimestamps. anyone, including the regulator, can verify locally without contacting Warrant. today's coverage: EU AI Act Articles 12 and 13, FCA Consumer Duty PS22/9, NYDFS Part 500 with the October 2024 AI guidance letter, SR 11-7 plus the new SR 26-2 revised guidance, RBI FREE-AI (released August 13, 2025), SEBI's retail algo framework with the April 2026 mandatory date, India DPDP, MAS AIRM with FEAT principles. nine frameworks across six jurisdictions. EU-led on purpose because Article 12 is the first concrete enforcement deadline. three real sample evidence packages downloadable on warrant.build. each one has a real package_id you can paste into warrant.build/verify. the receipt fetches from the public ledger, then four checks run locally in your browser: published key cross-check, PDF SHA-256 match, Ed25519 signature valid, Bitcoin block confirmed. the anchor for two of the samples is Bitcoin block #948165. what Warrant deliberately does not do: - no SDK install. no agent code changes. existing agents emit a trace post-hoc, Warrant ingests it. - no enforcement at the runtime layer. Warrant produces evidence about what already happened. - no compliance certification. runtime evidence standards explicitly say compliance certification is out of scope. Warrant is the deliverable that fills the gap. V0.4 public beta. solo founder. YC S26 application in flight, tagged via the @ProductHunt × @ycombinator partnership. honest critique on the verify flow specifically welcome. that is the regulator-facing UX i most want to get right. drop any of the 3 sample package_ids at warrant.build/verify and tell me what you would change. Vivek team@warrant.build

correction to the above, three months on. the dates moved and i'd rather flag it than leave it sitting there. Regulation (EU) 2026/1744 (OJ 24 July 2026, in force 27 July 2026) amended Article 113. Article 12 sits in Chapter III, so the Annex III high-risk obligations now apply from 2 December 2027, not 2 August 2026. what does apply on 2 August 2026 is Article 50, the transparency obligation. two more, same spirit. SR 11-7 was superseded by SR 26-2 — 26-2 is the current model risk guidance, and 11-7 shouldn't be cited as live. and MAS AIRM is still a draft consultation paper, not in force; we map it in the corpus, we don't count it as coverage. current position is 20 regimes mapped in the evidence corpus, 6 published: warrant.build/regulators

Warrant

the signed PDF every AI Act operator owes their regulator

the signed PDF every AI Act operator owes their regulator