saascode

Workwitness

A contractor-controlled receipt workspace that binds authorized work orders to source-preserving field evidence, reviewer acceptance, payment requests, operator acknowledgments, settlement states, disputes, and correction under an openly versioned schema.

Genesis score7.11/10
Make Workwitness real.0/500
500 more votes and Workwitness 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
0Existing work-completion assertion standards found
0Automatic payment releases
YesPortable correction history
The case

The research confirms field-photo and mobile-form products, content-provenance standards, signing infrastructure, and improving device support. It found no standard assertion for work performed. Content provenance can describe an image's capture and edit history within scope, but it does not prove who did the work, where the device really was, that the task met specifications, that a customer accepted it, or that payment is due.

Workwitness should create a portable evidence bundle, not an automatic settlement instrument. A paying network must explicitly contract to accept a schema version, evidence class, review process, authority, exceptions, dispute rights, and payment trigger. Device attestation, geolocation, time, asset scan, photos, measurements, technician statement, supervisor review, and customer acknowledgment remain separate observations.

The contractor keeps an export and controls reuse, while customer, occupant, site, and bystander privacy is minimized. A receipt can be corrected or superseded without erasing history. It never becomes a worker-performance score, universal credential, lien waiver, safety certificate, code compliance proof, warranty, or guaranteed payment.

Who pays — and why

Field-service networks, contractors, insurers, property operators, and marketplaces that need mutually accepted completion evidence and a portable dispute trail.

What it unlocks
A work authority record with customer, contractor, technician, site, asset, work order, scope version, specifications, permissions, safety prerequisites, schedule, and acceptance policy
A field evidence bundle with device and capture metadata, location scope, time, asset scan, photo or video, measurement, source, edit history, technician statement, privacy review, and limitations
An acceptance case with required evidence class, reviewer, inspection, customer acknowledgment, exception, rejection, rework, correction, signature, schema version, and no completion inference from one signal
A commercial chain separating accepted receipt, invoice or payment request, operator acknowledgment, approval, settlement, holdback, dispute, reversal, reconciliation, warranty event, and no payment guarantee
How Genesis scored it
7.11across seven criteria
tension 7temporal 8blindspot 6buyer 8leverage 6convergence 5why-not 8
8
Temporal window

Device provenance and signing support make portable evidence more practical now.

8
Buyer persona

Networks and contractors handling disputed field completion are specific.

5
Convergence

Several evidence, closeout, claims, and worker-owned credential neighbors support the direction.

Why it scored well

The field network buyer, portable schema, accepted evidence class, contractor ownership, and payment-state separation are concrete.

What's holding it back

Acceptance is a two-sided adoption problem, provenance does not prove work, privacy and fraud are difficult, existing platforms can add exports, and contractual settlement semantics vary.

Signals detected4 sources crossed
Signalcompetitive research carried in Genesis

Signaltechnical research carried in Genesis

Signaltechnical research carried in Genesis

Signalstandards research carried in Genesis

Direction briefworkwitness.md
workwitness.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.