Track record · engagement #1
One engagement, registry-cleared, stated exactly.
This page separates three things a buyer usually receives mixed together: the electoral authority's record, what the operator's system did in production, and what it did not do. No candidate and no party is named.
The official record
The electoral authority's figures, not ours
Presidential runoff · June 2026 Certified
Certified margin
251,854 votesCNE · Resolución E-3181 · 24 Jun 2026
Margin by vote share
≈ 0.95 % of valid votes, per the CNE recordPer the CNE record
Final against preliminary
≈ 0.003 % difference, per the CNE recordPer the CNE record
- Historical placement
- Narrowest second-round margin by vote share. 1994 was closer in absolute votes: 156,585.
- Certification
- Certified by the CNE in Resolución E-3181, proclaimed 24 Jun 2026. A nullity demand against the declaration was admitted by the Consejo de Estado (Sección Quinta) on 24 July 2026 and is pending; there is no merits ruling and the election's effects are not suspended. Veridian takes no position on the case. (wording pending counsel review)
- Challenge
- A challenge covering approximately 33,000 polling stations was filed. The count-stage petitions were withdrawn; the nullity demand above is pending.
- Count reproduction
- The final official count reproduced the preliminary count to within approximately 0.003 %, per the CNE record.
Every figure in this box is the electoral authority's. No competing figure was published, and this page makes no claim about the outcome.
Who the client was. A principal in the contest. The engagement ran in June 2026 under the operator's campaign-side product, three months before the Veridian name was adopted (September 2026). It is shown here for its evidence chain, not as a neutral engagement. (wording pending counsel review)
What ran in production
Four things the operator's system did, at national scale
Production-proven
Field capture and evidence chain
Capture, hash at capture, and custody events ran across the client's own field structure for four days without a break in the chain.
Production-proven
Provenance or a logged N/A, on every number
Across four days, every figure the operator published carried its source or was published as N/A with a logged reason. No blank and no zero stood in for absence.
Production-proven
The gates held
No public claim was made during the preliminary count, under pressure to make one. The rule was written before the contest and it held during it.
Production-proven
Monitoring, 21–24 June
Health returned OK on approximately 42 automated monitor runs between 21 and 24 June, per the operator's monitoring log.
Operator's monitoring log · 21–24 Jun 2026
The operator's limitation, disclosed here
And what did not run, disclosed here
- Automated pipeline
- The automated tally-sheet pipeline remained simulation-proven throughout. Every published figure rested on human-confirmed verification, not on automated extraction.
- Postmortem findings
- The written postmortem produced findings the operator had not anticipated. They are now contract gates rather than intentions: reachability rehearsal, restorable monitoring, credential rotation at close, and the postmortem itself.
- The analyzed sample
- The 5,101 tally-sheet analyzed sample is held as the demonstration dataset. It is a demonstration, not a production claim, and it is described that way wherever it appears. Veridian analyzed sample · engagement #1
Request an engagement
Tell us the contest, the date, and the artifact you need. We reply with scope, refusal conditions, and a price against the published floor.