Homologation is mostly proof: that each regulation applies or does not, that each test was passed, and that the vehicle being built is the one that was approved. The documents carrying that proof are where the time goes.
Vehicle homologation is the process of proving a vehicle, system or component meets the technical regulations of the market it will be sold in, so an approval authority can grant type approval. In the EU that runs under Regulation (EU) 2018/858, with the General Safety Regulation (EU) 2019/2144 and dozens of UN regulations under the 1958 Agreement, from lighting and braking to cybersecurity (UN R155) and software updates (UN R156). The US instead relies on manufacturer self-certification to the FMVSS.
The work is documentary. An information document describing the vehicle, test reports from a technical service for each applicable regulation, and conformity-of-production arrangements showing that production matches what was approved. When a part, a supplier or a software release changes, someone has to work out which approvals are affected.
That impact question is where AI helps most: reading the change against the information document and the regulations, and listing every approval it could touch, with the clause cited. The homologation engineer and the approval authority still decide.
part, supplier, software
information document, reports
UN and EU, current series
approvals affected, cited
extension, retest or none
raised with the technical service
It is the certification that a vehicle, system or component meets the technical rules of a market, granted by an approval authority after testing by a technical service. In the EU it is called type approval and runs under Regulation 2018/858 and the UN regulations of the 1958 Agreement. Without it, a vehicle cannot be registered for road use in that market.
Broadly: determine which regulations apply to the vehicle category and market, prepare the information document, test the vehicle or systems with a technical service, submit the reports to the approval authority, and set up conformity-of-production controls. After approval, every relevant change must be assessed and, where needed, approved as an extension.
Yes, with the documentary part: building the applicability matrix, drafting information document entries from engineering data, keeping test reports linked, and assessing which approvals a change could affect. It cannot take any regulatory decision. Each output cites the regulation and source record, so your homologation engineer can verify it quickly.
What we built, what stage it is at, and a link to the live thing wherever there is one.
yourOS is an operating system with an AI at its heart. You talk to it like a person, out loud or typed. It makes your calls, plans your days and works on your projects with a crew of agents, on your own private server. Our own product, built from the first commit; the waitlist is open.
Website, backend and app assets for Sonora, a free AI sound-therapy app on iOS and Android published by Cognitive AI.
Brand, website, prototype, apps on five platforms, the AI backend and the algorithm-intelligence pipeline for Podswap, a social growth engine that runs without a human in the loop.
In closed beta: Roxy, a private AI assistant with permanent memory running on infrastructure the user owns. Brand, site, product, backend and conversational design.
Live at coherence.com: brand identity generated with AI agents we directed, the motion system and website for the group behind Sonora, AboutAI, WakeUp and MudShadows. Agent work remains in build.
Live at domainbooth.com for DomainBooth, a premium domain brokerage: a new animated mark, every page redesigned and rebuilt with designed mobile layouts, and a custom CMS for its sales record, featured names, press and enquiries.
We start with one recent engineering change and show the impact list we would have produced for it.
30-minute technical call · no deck