Technology
One verifiable system, layer by layer.
The architectural overview — how AI, the open record, and the commit-reveal mechanism fit together into one system you can verify.
Veraq is built so that the parts you would normally take on faith can be opened and read instead. Four things sit underneath every wave: a record of what happened, a mechanism that decides each outcome, AI held to a narrow role, and open infrastructure anyone can inspect. This page walks each layer in turn, then shows how they hold each other to account.
The order matters. The mechanism is committed before a wave runs. Participation and outcomes are written as they happen. The defined share to a chosen cause is recorded after. Read end to end, the layers form a single account of a wave that you can check rather than trust.
The layers
The open record
Every participation, outcome and contribution is written down to be read. Seven entities — Wave, Mechanism, Participant, Participation, Outcome, Contribution, Cause — link into one auditable account of each wave.
The commit-reveal mechanism
commit-reveal-v1 is the published method that decides each wave. It is committed to the open record before the wave begins and revealed after, so the math can be read first and verified later.
AI, used responsibly
AI assists with the work around a wave. It never decides an outcome. Selection runs only on the published mechanism, and where AI is used it is held to the same checkable standard as everything else.
Open infrastructure
The contracts and protocol references are published so anyone can inspect, verify, or build on the same rails Veraq runs on. There is no privileged path and no hidden state.
A wave, layer by layer
- 01
Commit
Before participation opens, the mechanism for the wave is committed to the open record. The commitment fixes the method in advance, so it cannot be changed once the wave is under way.
- 02
Participate
Participants join the wave on terms already published. Each participation is written to the open record as it is made, linked to the wave it belongs to.
- 03
Reveal
Once the wave closes, the committed mechanism is revealed and run. Anyone can confirm the revealed inputs match the earlier commitment and reproduce the result for themselves.
- 04
Outcome and contribution
The outcome is recorded, and a defined share of it is allocated to the verified cause chosen for the wave. The contribution is written to the record too, so it can be followed from outcome to cause.
The mechanism is committed before the moment, and provable after it.
Terms on this page
- Open record
- The auditable account where every participation, outcome and contribution is written. It is read directly, not taken on description.
- Commit-reveal mechanism
- commit-reveal-v1: a method committed to the record before a wave runs and revealed after, so the selection is provable rather than asserted.
- Defined share
- The published, consistent portion of every outcome allocated automatically to a verified cause and recorded as a contribution.
- Wave
- A single round of participation, decided by its committed mechanism and recorded end to end.
How the layers verify each other
No single layer is asked to vouch for itself. The commitment made before a wave constrains the reveal that comes after it, so the mechanism cannot be quietly altered once participation is open. The open record holds both the commitment and the reveal, so the two can be checked against each other by anyone, at any time.
AI sits outside this loop by design. Because outcomes are decided only by the published mechanism, no assisting model can move a result, and any place AI touches the work is itself recorded and open to inspection. The open contracts and protocol references close the circle: the same rails Veraq runs on are the rails you can audit, so a claim on one layer can always be tested against the others.
Common questions
Do I have to trust that this works?
No. The mechanism is published before each wave and provable after, and the record is open. You can read the method first and check the outcome yourself rather than take it on faith.
Could the mechanism be changed mid-wave?
The mechanism is committed to the open record before participation opens. The reveal afterward must match that commitment, so a change made during the wave would not verify.
Does AI decide who gets what?
No. Selection runs only on the published commit-reveal mechanism. AI assists with surrounding work and never decides an outcome, and where it is used it is recorded and inspectable.
Can I inspect the infrastructure directly?
Yes. The contracts and protocol references are published so you can read the open record, verify a wave, and build on the same infrastructure Veraq uses.
One verifiable system: described so it can be checked, layer against layer.