Systems — APEX
APEX
Status: Pre-deployment
APEX reads public data — procurement notices, sanctions lists, corporate registries, court records, and citizen tips — detects defined patterns of procurement fraud, and scores each finding with a calibrated certainty engine. No single person can escalate a case: a five-member council, each holding a hardware key, must reach quorum, and every finding is independently verifiable against a public ledger without trusting the platform. It compiles evidence and signals confidence; a human institution makes every consequential decision.
APEX is a built Phase 1 platform undergoing engineering hardening. It is not yet in operational use by any institution: the governance council is not yet formed and multi-institution federation is designed and scaffolded, not running. Nothing on this page describes a live national deployment.
At a glance
| System name | APEX |
|---|---|
| Category | Anti-corruption intelligence for public procurement |
| Status | Pre-deployment |
| Designed for | Public institutions — national oversight institutions with an investigative mandate |
| Standards | Built against the principles of UNCAC and the Open Contracting Data Standard (OCDS) |
| Authorization model | Five-member council quorum, each member authenticating with their own hardware key; no lone escalation |
| Source code | Kept strictly private; not published, mirrored, or distributed |
The problem
Public money is most often lost where contracts are awarded. The institutions that exist to catch this are not short of mandate — they are short of evidence collected at scale. Cross-referencing dozens of public sources by hand, a small team can review only a handful of contracts a year. The mechanical work of finding what to look at is the bottleneck, not the judgement of whether to act.
What APEX does
APEX automates the mechanical cross-referencing and hands human investigators a calibrated signal — never a verdict. A finding travels a defined forensic pipeline; at each stage it is confirmed, scored, or challenged, and nothing escalates on a single source or a single person's say-so.
Three architectural commitments
The platform's design rests on three rules that hold whatever the case:
Multi-source proof, never single-source
A pattern only counts when independent sources agree; a finding only escalates with several independent signals at high confidence. No single feed can move a case on its own.
No single human can act alone
Decrypting a citizen tip and escalating a finding each require a quorum of a five-member council, every member authenticating with their own hardware key. There is no lone override.
Every claim is independently verifiable
Anyone — a journalist, a citizen, a foreign auditor — can check a finding against a public ledger without trusting the platform at all. Signed dossiers are deterministic, so a third party can re-render and compare.
From public data to defensible findings
A finding that cannot survive scrutiny is worse than no finding at all, so APEX treats defensibility as a property of the pipeline, not a quality of the report. It begins with what is read: public sources only — procurement notices, sanctions lists, corporate registries, court records, and citizen tips submitted to the platform. Against this material it applies defined patterns of procurement fraud — 43 patterns in 8 categories — rather than open-ended suspicion, so every match traces back to a stated, reviewable rule.
Each match is then scored by a calibrated certainty engine, challenged in an adversarial counter-evidence review, and corroborated across independent sources; nothing escalates on a single source or a single person's say-so. What survives corroboration goes before the five-member council; only on quorum is a signed, bilingual, deterministic dossier produced and delivered to the mandated institution — a dossier a third party can re-render and compare. What APEX hands investigators is a calibrated signal, never a verdict. A mandated human institution decides whether to investigate, and it alone makes every consequential decision.
Standards and posture
APEX is built against the principles of the United Nations Convention Against Corruption (UNCAC) and the Open Contracting Data Standard (OCDS). It operates on public data only — mandated-disclosure portals, open APIs, and licensed access to public records. It does not decide guilt, does not prosecute, and does not publicly accuse; it compiles evidence and signals confidence, and a human institution makes every consequential decision.
Sovereignty guarantees
| Guarantee | How APEX delivers it |
|---|---|
| Public data only | Every source is mandated disclosure, an open API, or licensed access to public records. The platform does not ingest private or covertly obtained data. |
| Data residency | Designed to run on national infrastructure; findings and their evidence stay in-country. |
| No lone escalation | Escalation and tip decryption require a quorum of a five-member council, each authenticating with a hardware key. |
| Independent verifiability | Every finding can be checked against a public ledger without trusting the platform; signed dossiers are deterministic and re-renderable. |
| Human decision | The platform signals calibrated confidence; a mandated human institution makes every consequential decision. It does not decide guilt or prosecute. |
| Audit chain | A triple-witnessed, hash-linked audit chain makes every state change tamper-evident. |
| Source code | Kept strictly private; not published, mirrored, or distributed. |
Questions institutions ask
Does APEX decide whether someone is guilty?
No. It compiles evidence and reports a calibrated probability that something warrants investigation. It does not decide guilt, prosecute, or publicly accuse. A five-member governance council decides whether the evidence is strong enough to forward, and a mandated human institution makes the consequential decision.
What data does it use?
Public data only — mandated-disclosure procurement portals, sanctions lists, corporate registries, court records, open APIs, and citizen tips submitted to the platform. It does not ingest private or covertly obtained data.
Can a single person escalate a case?
No. Decrypting a citizen tip and escalating a finding each require a quorum of a five-member council, with every member authenticating using their own hardware key. There is no single-person override.
Is APEX deployed?
No. It is a built Phase 1 platform undergoing engineering hardening, pre-deployment. It is not in operational use by any institution; the council is not yet formed and multi-institution federation is designed and scaffolded, not running.
Is APEX's source code available?
No. All APEX source code is kept strictly private. It is not published, mirrored, or distributed.
How can a third party verify a finding?
Without trusting the platform. Every finding can be checked against a public ledger, and signed dossiers are deterministic: a journalist, a citizen, or a foreign auditor can re-render a dossier and compare the result with what was signed. Verification rests on the public record and the signature, not on APEX's word.
What happens when the evidence cuts both ways?
It is weighed, not ignored. Every finding passes an adversarial counter-evidence review — a stage whose purpose is to challenge the finding, not to confirm it — and must then be corroborated across independent sources. A pattern only counts when independent sources agree, and a finding only escalates with several independent signals at high confidence; no single feed, and no single person, can move a case on its own. A finding that does not survive this scrutiny is not escalated.