Who We Are

The team behind InviolableVeritas.

IV was founded on a single conviction: that AI governance, security, accountability, and clarity must be architectural decisions made before a line of code is written. The people below carry that conviction into the work.

The team that built Loriqa did not learn governance from a framework document — they learned it from building systems where governance failure had real consequences.

Principals

Founders

Two founders. Two continents. One architecture.

Co-founder · European Operations

Frank Mainzer

Cologne, Germany

Frank is co-founder of InviolableVeritas and brings 29 years of experience delivering complex enterprise software at C-level — across ERP, healthcare platforms, and digital transformation programs across waterfall, agile, Lean, and TMAP delivery disciplines.

He has led international software development across the United States, South Africa, China, and Eastern Europe, with a deep specialty in regulated healthcare: HIS, FHIR, eRezept, telemedicine, healthcare platform development, and clinical data architecture. Frank also brings hands-on capability in cybersecurity and IT forensics — including ethical hacking and mobile forensic investigation.

Affiliation · SinCera Tech GmbH · Education · Dipl. Wirt. Inform. Universität zu Köln · Specialty · Regulated healthcare, cybersecurity, IT forensics

Co-founder · Architect

Tomas Ball

Austin, Texas — United States

Tomas is co-founder and architect of InviolableVeritas and the Loriqa platform. His work is in applied AI, agentic systems, and secure enterprise architecture — translating large language model capability into governed production deployments at enterprise scale. His broader work covers intelligent automation, enterprise data strategy, and the emerging architecture of autonomous and agentic workflows.

Education · MBA, Management of Technology — Georgia Institute of Technology · BS, Computer Information Systems — Tarleton State University
Background · Enterprise AI delivery, secure system architecture

Why this team built this product

Both founders have spent careers inside regulated industries — financial services, healthcare, government — where governance failure is not an inconvenience but a liability event. They have watched compliance frameworks struggle to keep pace with software that has become non-deterministic, autonomous, and capable of consequential action at machine speed.

The conviction behind IV is that this gap will not close by adding more controls to the same architecture. It closes by making governance, security, accountability, and clarity properties of the architecture itself.

Our Polestar

Our polestar is the Organic Security Posture, expressed through the IV pillars: Governance, Security, Accountability, Clarity. The constitution is published. It does not depend on the founders to enforce.

OSP defines five phases — PDR³: Prevention, Detection, Response, Recovery, Reinforcement — with named architectural ownership at every phase and a cryptographic evidence trail. The EventStore is append-only at the database layer, not by convention. Four-eyes gates are schema constraints, not policy. The heartbeat dead man's switch is enforced by infrastructure independent of the API layer. None of these are commitments we maintain by attention. They are properties of the architecture.

A future contributor cannot quietly remove the heartbeat dead man's switch — the framework will not run without it. There is no mode where the audit trail is optional. There is no path where containment requires human approval before it begins. Disabling any oversight component is itself an immutable audit event.

The IV product is not what the founders carry in their heads. It is what the architecture cannot do without. OSP is published in detail on the Loriqa architecture page — any buyer, regulator, or future contributor can verify the constitution rather than trust it.