Domokos is a record layer for regulated automotive engineering. It binds every compliance artifact — who produced it, when, under what competence, against which clause — into an append-only chain, so a reviewer can confirm for themselves that nothing was altered after the fact.
Illustrative extract. Seq 0150 is a finding, not an error — Domokos records what happened, it does not prevent engineering.
The problem
They are engineering that happened without a record able to carry the weight later put on it. A review that genuinely took place, with nothing showing the author and the reviewer were different people. Independence that existed in practice and nowhere in the artifact. A supplier capability conclusion held as a judgement rather than a referenced document.
None of it is discovered early. It surfaces about six weeks before an assessment, when the only remaining options are expensive.
Engagements
A two-week engagement against one programme or one assessment scope. Fixed price, fixed duration, no discovery phase.
Gap register delivered within 14 days of signature, or no fee.
For programmes where the record has to stay current between assessments rather than be rebuilt before each one.
Verification
An integrity claim you can only check with the vendor's own tool is not an integrity claim. Exported packages are verified by a standalone open-source checker that shares no code with Domokos, reads only the published bundle format, and runs as a single file on a locked-down machine with no build step.
It checks chain integrity end to end, sequence continuity including voids and declared filters, timestamp anchors against the chain root, and that the human-readable continuity statement matches the bundle. Exit code zero only if every check passes.
Neutrality
A record is only worth auditing if whoever holds it has nothing at stake in the verdict. These are structural commitments, not preferences:
Ádám Domokos also works as an independent consultant, including subcontracted assessment labour for third-party assessment firms, at a published day rate.
No data, finding, document, or observation obtained through any such engagement enters the Domokos record layer or the finding corpus. That separation is enforced by the schema — engagement-sourced rows are rejected at the write boundary rather than filtered afterwards.
Stating this is cheaper than being found out for it. It is the same principle the product runs on: a declared exception preserves the record, a silent one destroys it.
Who
Development engineer working on whole-vehicle HIL simulation and virtual test drive systems at Audi Hungária. Previously design engineer at Porsche Engineering. BEng, Technical University of Cluj-Napoca; MSc, Széchenyi István University. Hungarian, Romanian, German, English.
Domokos is operated independently through Domokos Ádám EV, a registered Hungarian sole proprietorship. It is not affiliated with, endorsed by, or operated on behalf of any employer.
Contact
If you have an assessment or a type-approval submission coming, a 30-minute conversation is usually enough to tell whether Domokos is relevant to it.
adam@domokos-automotive.com