Private business coordination · Nuvixes
A buyer and provider workspace for private, interdependent commitments: the dataset, compute, and evaluation activate together—or none do.
Why this exists
A dataset without compute, or compute without an evaluation slot, can leave a team with bills and no usable outcome. Converge explores a different agreement: independent providers keep private terms, but their reservations activate together.
The demo packages a dataset license, GPU capacity, and an independent evaluation. A buyer assembles the package; each provider sees and accepts its own leg. The interface makes a shared outcome visible without exposing everyone else's commercial terms.
On September 30, the current Daml contracts compiled and passed atomic-success, rejection, and private-terms tests. A temporary Canton sandbox JSON API run created three active reservations in one settlement update. A rejection path did not activate the package.
On October 1, a restarted file-backed sandbox could not complete transaction submission. It was stopped rather than connected to the public app. The successful isolated proof remained useful, but it did not become evidence of a public Canton-connected transaction.
Build journal
Recorded milestones from the build. Dates describe these events, not the entire project history.
The saved sandbox receipt records a settlement creating three reservations; contract tests also covered rejection and privacy.
Transaction submission timed out in a restarted sandbox. The public app remained in reference mode.
Where it stands
Built, with a public reference demo, authenticated buyer/provider views, and seed providers. The deployed health endpoint still reports reference mode and canton:false; the saved sandbox proof establishes the contract path separately from the public app.
The next chapter
Connect a reliable authenticated Canton participant, verify the buyer/provider flow through the deployed app, and replace seeded availability with real provider feeds.
Based on Converge's September 30 and October 1 verification records, submission brief, and delivery phases. Later deployment progress is not asserted here.