saascode
hr, payroll & talent·run 255 · Jun 2026

Provenwork

A settlement-control workspace that freezes task acceptance criteria, collects proof and human verification, routes jurisdiction-specific tax and worker-classification questions to accountable professionals, and reconciles approved payout-provider events.

Genesis score5.94/10
Make Provenwork real.0/500
500 more votes and Provenwork is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
1Confirmed results-based payout provider
90+Confirmed provider coverage countries
0Verified proposed integration interfaces
The case

The research confirms a live results-based payout provider with reporting and identity controls, while proof-of-work and payer-side tax or classification consequences remain outside its reviewed offering. It also identifies a regulatory timing signal. No direct combined competitor was found, which is not proof of legal or commercial feasibility.

Provenwork should separate task agreement, completion assertion, evidence, deterministic check, human acceptance, tax and classification facts, qualified determination, payout proposal, approval, provider instruction, acknowledgment, settlement, reporting event and dispute. A model cannot determine whether a person is an employee, whether withholding is owed or whether work legally qualifies for payment.

The system should calculate transparent scenarios only from approved rules and facts, never issue tax or legal conclusions autonomously. Signed records prove version and approval scope, not the truth of work, classification, tax treatment or government acceptance.

Who pays — and why

Marketplace, finance, payroll and operations teams administering results-based payments to human contractors or other authorized payees.

What it unlocks
A task agreement with parties, authority, jurisdiction facts, scope, acceptance predicate, evidence requirements, amount or formula, currency, deadlines, dispute process, classification and tax owners, signatures and effective dates
An acceptance case separating completion assertion, artifacts, provenance, deterministic checks, uncertainty, conflicts, reviewer finding, rationale, correction and appeal
A jurisdiction review packet with worker and payer facts, work location, entity and contract status, payment character, prior relationship, approved rule source, effective date, qualified determination and expiry
A settlement chain separating proposed amount, budget reservation, tax and withholding instructions, approvals, provider command, acknowledgment, settlement, reporting event, remittance evidence, reconciliation, dispute and correction
How Genesis scored it
5.94across seven criteria
tension 6temporal 7blindspot 5buyer 5leverage 7convergence 5why-not 6
7
Temporal window

New payout rails and a confirmed regulatory trigger support timing.

7
Asymmetric leverage

A maintained rule and evidence corpus can scale with professional review.

5
Convergence

Related payment-control ideas and live provider evidence support the category.

Why it scored well

A live payout rail, a specific unserved control layer and a versioned evidence-to-settlement model make the direction concrete.

What's holding it back

Buyer, integration and legal treatment remain underverified; worker classification, withholding, disputes, cross-border payment and proof of work are high-risk.

Signals detected3 sources crossed
SignalGenesis research

SignalGenesis research

SignalGenesis research

Direction briefprovenwork.md
provenwork.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.