AI you can stand behind.

Every claim an agent writes is checked against the record behind it, and every action it takes against who authorised it, without a model in the loop. The first is ProveML and Vera; the second is PAC and Elixir. A person releases it to your customers. The checks are what let it run further.

eight years on digital trust, agents its newest test

What runs.

  • ProveML

    Checks what an AI writes against your data and your thresholds, claim by claim. Open source.

  • PAC

    Sets what an agent may decide on its own, earned with evidence rather than configured.

  • Elixir

    Governs a fleet of client systems under those rules today, and acts only as far as its own record allows.

the PAC framework in full, on trustedagentic.ai →

Where it comes from.

We come from eight years of research and pilots on the European side of digital trust, at Howest’s Cyber3Lab: EBSI and the Digital Europe project EBSI-NE, self‑sovereign identity, verifiable credentials and the digital product passport; Hyperledger Fabric since 2021 and Besu, certified on both; the 2025 LF Decentralized Trust Community Award. The question then is the question now: how a claim can be believed by someone who was not there when it was made. ProveML’s trust adapter reads a record as a signed credential, so it is one answer, not two.

how a signed source is checked →

What we build against.

  • Confidently wrong

    The answer that reads perfectly and is not true. Every claim is bound to its measurement and checked.

  • Doing more than asked

    Credentials used for whatever the agent decides the goal is. Access is scoped to the task and expires with it.

  • Failing quietly

    A stopped job looks like a calm week. Systems have to prove they are alive.

  • Drifting from intent

    Between what you asked and what it did there has to be a record.