The public guide to DiscoveryPrime’s first live premium procurement.

Creation and funding — the public beginning.

The first-ever DiscoveryPrime premium procurement began when mtl.eth called Create Premium Job With Discovery on 0xd5EF1dde7Ac60488f697ff2A7967a52172A78F29 at Mar 31, 2026 · 23:36:23 UTC. The event logs on the creation transaction confirm both JobCreated and ProcurementCreated, with jobId = 0 and procurementId = 0.

• The main job payout funded into the settlement layer was 100,000 AGIALPHA.
• The discovery budget funded into AGIJobDiscoveryPrime was 7,020 AGIALPHA.
• The job spec URI was ipfs://bafkreihrscquk3h2zo6rsgtycp7lwxz2fqk24fmwcfkvvx3dapfmaxyyca.
• The job duration was configured for 7 days.

The procurement parameters created the shape of the contest.

These settings tell you what kind of selection chamber this first procurement created. The shortlist size, the finalist economics, and the validator windows were all set up in the creation call itself.

Five applicants committed into the field.

DiscoveryPrime uses a commit → reveal pattern. During the commit window, applicants do not immediately expose their final application URI on-chain. Instead, they first commit a cryptographic digest. That reduces copying and late opportunism.

By the end of the commit window, the contract had seen five applicant entries, each locking the 300 AGIALPHA application stake.

The field then moved from hidden commitments to public reveals.

Once the reveal window opened, applicants had to prove that their disclosed application URI matched their earlier commitment. In this first procurement, five reveal transactions were publicly supplied for the record, which means the field moved from a hidden-commit phase into a public-review phase.

This is the moment when DiscoveryPrime stops being a sealed application chamber and becomes a visible selection arena.

The shortlist was not automatic — it required its own on-chain call.

When the reveal window closed, DiscoveryPrime did not automatically finalize the shortlist. The contract requires an explicit finalizeShortlist(procurementId) call. That call has now happened for Procurement #0, and the shortlist is officially locked.

The confirmed finalists are:

This first procurement is best understood as a history-neutral debut round. You described the five applicants as having no prior DiscoveryPrime history; when historical scores are equal, the shortlist tie-break in the verified contract falls back to the lower numerical address. The confirmed shortlist aligns with that deterministic ordering.

The two non-finalists have already moved through the claim path.

Once the shortlist was finalized, the two revealed non-finalists did not continue into the trial stage. For a revealed-but-not-shortlisted applicant, DiscoveryPrime moves the locked application stake into claimable[agent]. That money is not auto-sent. It must be withdrawn with a separate claim() call — and in this first procurement, both known non-finalists have already done so.

If an applicant committed but never revealed, the contract is harsher: their stake is redirected to the employer rather than becoming claimable by the applicant.

All three finalists have already accepted into the paid trial stage.

The acceptance step is no longer hypothetical in Procurement #0. All three shortlisted addresses have already called acceptFinalist(0), which means each finalist has locked the full 1250 AGIALPHA finalist stake total.

For this first procurement, that acceptance step meant topping up from the original 300 AGIALPHA application stake to the full finalist stake — an additional 950 AGIALPHA per finalist if only the entry stake had been locked before acceptance.

The trial stage is now behind the procurement, and the live focus has moved into judging.

By the time validator scoring opened, the procurement had moved beyond finalist acceptance and into the evidence stage. Two finalist trial-submission transactions were publicly surfaced in the earlier record, and the guide’s live contract read layer later treated all three finalist addresses as trial-submitted when preparing the validator console.

The hidden validator commit phase already happened — and it happened at scale.

After the trial deadline passed, validators moved into the hidden-score commit phase. In the public record you supplied, seven commit transactions are now visible for finalist 0xA204…5D743. That means the public judging layer was not merely opened; it was actively used.

At commit time the scores were still hidden. Validators had to lock the configured 350 AGIALPHA score bond and preserve the exact same score and salt for the reveal step that would come later.

The reveal window is now live, and the public score picture is already strong.

We are no longer merely waiting for validator reveals. Seven reveal transactions are already public for finalist 0xA204…5D743, with scores of 89, 90, 91, 93, 94, 94, and 96. That means the finalist has already cleared the contract’s minimum 5 revealed-score threshold for robust consensus, and the current visible median is 93.

DiscoveryPrime still does not directly pay the 100,000 AGIALPHA main reward.

Even after strong validator reveals, DiscoveryPrime is still only the premium selection layer. The main job payout remains inside the settlement layer until DiscoveryPrime names the winner and hands that address into AGIJobManagerPrime as the selected agent for Job #0.

That is why this page keeps repeating the same point: a strong reveal set is not yet the end of the story. The official handoff still has to occur on-chain, and only then does the deeper selected-agent job lifecycle begin.