VGoS — Deterministic Settlement with Proof-Gated Disbursement
We don’t replace your payout rails. We become the release gate: payouts move only when the math replays identically and the right people/cryptography sign off.
The payout gate (what must be true)
Deterministic replay + acceptance matrix
Release only when the replay-computed digest equals the transcripted outputs digest, and the acceptance matrix meets freshness & quorum:
gate =
(replay_digest == transcript_digest)
∧ acceptance_matrix(ACK, SPV, CT).meets(FRESHNESS, QUORUM)- ACK — business acknowledgement/approval
- SPV — cryptographic/Merkle/light-client or ZK proof
- CT — compliance token/attestation
- F / Q — freshness bound & quorum requirement
What this prevents
- “Looks good” reports releasing wrong money
- Non-deterministic drift under concurrency/load
- Round-off/carry inconsistencies across replays
- Vendor migrations that silently alter totals
If the math doesn’t match and evidence isn’t fresh with quorum, funds don’t move — with reason-coded holds for fast resolution.
How VGoS differs (keep your rails)
Above your payout rails
Connect via CSV/API to Stripe Connect, Adyen for Platforms, PayPal Hyperwallet, Wise Platform, and others. We gate disbursement before those systems move money.
Deterministic compute contract
Canonical ordering, fixed-precision math, and deterministic carry policy make outcomes byte-identical across replays and reshards.
Dual-write & migration guard
Prove cross-version digest equality during migrations before promotion. No silent deltas, no guesswork.
Common vendor gaps we close
- No transcript-gated disbursement
- No deterministic compute guarantees
- No reshard invariance rule
- “Dashboards & approvals” without machine equivalence
- API idempotency ≠ window-bounded, transcript-scoped determinism
What we ask in discovery
- What must be true before you release a payout file today? Who signs off?
- Have you ever rolled back or reissued a payout run? Why and how long?
- How do you prove equality across shard versions or after replay?
- How are rounding/carry remainders enforced deterministically?
Acceptance matrix — starter presets by vertical
| Vertical | Typical Proofs (ACK / SPV / CT) | Freshness (F) | Quorum (Q) | Notes / Reason Codes |
|---|---|---|---|---|
| Marketplaces & Gig | ACK from Finance; CT: KYC/OFAC; optional SPV for off-platform receipts | ≤ 1 hour | 2 of 3 (Finance + Compliance + Ops) | DUPLICATE, STALE_PROOF, CT_INVALID, DIGEST_MISMATCH |
| Creator / Ads Networks | ACK; CT: tax/withholding tokens; SPV if ad-spend proofs used | ≤ 24 hours | 2 of N incl. Finance | Add CAPPED_BY_POLICY for bounded-loss caps |
| Gaming / Web3 | SPV (headers+Merkle) or ZK light-client; ACK | ≤ 12 blocks (chain-specific) | 1 SPV/ZK + 1 ACK | Add INSUFFICIENT_WORK (header chain below threshold) |
| Exchanges / Brokerage | ACK; SPV from custody/chain; CT: AML attestation | ≤ 5 minutes | 3 of 4 (Ops, Risk, Custody, Chain) | Add QUORUM_SHORTFALL |
| Royalty / Media | ACK; CT: rights/contract attestation | ≤ 24 hours | 2 of 3 (Label/Publisher/Finance) | Add RIGHTS_MISMATCH |
| B2B SaaS Rebates | ACK; CT: contract SLA token | ≤ 7 days | 2 of N with Legal | Add SLA_UNMET |
Presets include: deterministic carry tie-break (ascending principal_id), bounded-loss cap order, INVALID ⇒ no pay, and two-checkpoint promotion during resharding.
Integration
Where VGoS sits
VGoS runs beside your data pipeline, fraud/compliance stack, and payment processors. You enable transcripts and verifier hooks, gate a cohort, then expand. No schema rewrites; no PSP change.
- Mirror a cohort (e.g., 5–10%) and dual-run
- Policy-as-code for acceptance matrix (ACK/SPV/CT)
- Reason-coded holds; privacy-first transcripts (digests over raw PII)
Architecture visuals (placeholders)
Replace these with your own diagrams in /public/images/product/.
Pilot in 30 days
Targets
- Worker/creator DSO → ≤ 1 day
- Dispute rate → ≤ 0.5%
- Fraud leakage → ≤ 0.3%
Why teams like it
- Fewer clawbacks & faster close
- Privacy-first audits via transcript digests
- Controls that don’t punish good users
Next step
Gate one high-risk cohort for two windows; measure replays, reason codes, and promotion time. If we don’t meet the targets we agree up front, you don’t expand.
Why it matters
From promises to guarantees
“Dashboards & approvals” aren’t machine equivalence. VGoS requires digest equality and evidence before human approvals even matter. It’s a different class of control.
Provable, privacy-first compliance
Auditors and regulators verify transcript digests without needing raw personal data. Reveal raw data only when warranted.