Verified autonomous discovery
Governed discovery. Verified advancement.
Verinex is the flagship Prodia Systems platform: a governed discovery system that advances capability through evidence, verification and control rather than unconstrained generation. Work moves through a defined cycle — discover, test, verify, govern, retain, advance — and only candidates that survive that cycle are retained.
Visit Verinexverinex.dev(opens in a new tab)Verinex is the flagship Prodia Systems platform: a governed discovery system that advances capability through evidence, verification and control rather than unconstrained generation. Work moves through a defined cycle — discover, test, verify, govern, retain, advance — and only candidates that survive that cycle are retained.
Every retained advance carries signed evidence and content-addressed, replayable artefacts, so an outcome can be re-examined rather than taken on assertion. Acceptance is evidence-led, reuse is controlled, and separate verifiers judge candidate work independently of the process that produced it.
The problem
Autonomous systems can generate far more candidate work than an organisation can responsibly accept. The constraint is no longer production; it is defensible acceptance — knowing which results were tested, by what, under which protocol, and whether the record can be reproduced later.
Intended users
Prodia Systems research and engineering, and controlled research partners engaged under access agreements.
What Verinex does.
Governed discovery cycle
Discover, test, verify, govern, retain and advance as explicit stages, each with defined entry and exit conditions rather than an open-ended generation loop.
Separate verifiers
Candidate work is judged by verification components that are independent of the machinery that produced it, so acceptance does not rest on self-assessment.
Signed evidence
Accepted results carry signed evidence describing what was run, what was checked and what was concluded.
Content-addressed replayable artefacts
Artefacts are addressed by content so a preserved result can be located and replayed exactly, not approximately.
Evidence-led acceptance gates
Continuation is gated on evidence rather than throughput; rejected candidates are archived with their record intact.
Controlled reuse
Retained capability is made reusable under explicit control, so downstream work inherits a defined and inspectable basis.
- Acceptance decisions are recorded, not remembered.
- Results can be re-examined from preserved artefacts rather than re-argued.
- Verification is structurally separated from generation.
- Rejected work remains archived and inspectable.
- A defensible basis for discussing autonomous results with reviewers and partners.
- Reproducibility, transfer and capability-delta hypotheses can be tested against a preserved package.
- Reuse of prior capability is bounded and traceable.
Verification as an architectural boundary
Verinex treats verification as a structural boundary rather than a review step. The engine that proposes work does not adjudicate it, evidence is produced as a first-class artefact, and continuation depends on that evidence surviving independent checks.
- Independent verifier components with their own acceptance criteria.
- Content-addressed artefact store supporting exact replay.
- Signed evidence records bound to the protocol under which they were produced.
- Explicit continuation gates separating candidate work from retained capability.
Private platform, operated by Prodia Systems Limited. The Verinex research page reports that the frozen V1 engine reached the defined Depth-13 protocol state under a frozen experimental protocol on 28 August 2026. That is a first-reach result — not exhaustive enumeration of Depth 13, not independent external reproduction, and not a demonstration of thirteen economically meaningful capability gains. The 63/63 certificate evaluation is internal controlled evidence, not externally certified production telemetry. Independent reproduction and real-world capability transfer remain distinct validation steps.
Visit Verinexverinex.dev(opens in a new tab)