Contracts / e-sign

Canvas signature capture with public token-link signing. Tokens are 20 bytes from crypto.getRandomValues (160 bits) and signing is single-use.

What it is and how it feeds the rest

Mechanically

Canvas signature capture with public token-link signing. Tokens are 20 bytes from crypto.getRandomValues (160 bits) and signing is single-use.

How it connects

Should bind signed terms to the computed revenue split; currently sits beside the money domains rather than driving them.

Worth knowing

CORRECTION: the first domain sweep called token generation 'broken'. It is not — verified correct at contracts.ts:6-10. See research/CANONICAL-NUMBERS.md.

Components

src/components/contracts/

Convex modules

contracts.ts

Tables

contracts

The decision — what we do here

KEEP+WRAP-later — tokens correct; wrap documenso as a service for legal-grade audit later.

Repos we analyzed for this domain

WRAP documenso/documenso

Legal-grade e-sign with audit trail, run as a service behind his signing page.

STUDY OpenSignLabs/OpenSign

E-sign alt — multi-signer/expiry/cert patterns, AGPL so study.

LIFT = copy the code into the fork · WRAP = run underneath as a service · STUDY = architecture only. Verdicts from the OFM sourcing campaign.

Open questions

Research priority for this domain is low. Agent findings splice in below this line and survive regeneration.