Thesis

Why now

The market transition behind Wet Ink, stated in four steps — what review looked like, what changed, what follows, and what has actually been built in response. No workflow product is claimed on this page, because none has been selected yet, and we say so.

Before

• Review and verification performed by people.
• Controls designed around human actors — maker-checker, QA sampling, access reviews, change boards.
• Institutional knowledge held implicitly, in the reviewers themselves.
• Logs that record status — cleared, approved, complete — rather than reasoning.

Now

• Machine-assisted execution entering regulated document work.
• Automation pressure rising faster than the controls around it.
• Agency, investor, and enterprise expectations shifting: Fannie Mae's LL-2026-04 AI/ML governance framework took effect on 2026-08-06 — the obligations are walked, with sources, in the explainer.
• A growing need to preserve evidence, rule versions, approvals, and reproducibility across work a machine touched.

The implication

If machines participate in regulated work, the control system must govern theaction, not merely store the output. A status log tells you a file was cleared. It does not tell you what evidence supported the clearing, which rule version governed it, who or what approved it — or whether anyone could have quietly changed the answer afterwards. Every control built for human workers assumes a human's incentives, memory, and accountability. A nonhuman workforce needs the control expressed where it cannot be argued with: in the system of record itself.

The current Wet Ink response

What has actually been implemented — stated without productizing a workflow: a sealing architecture where every judgment records who judged, against which version of which rule, citing which page of which document, at what cost, appended to a tamper-evident record no one — including us — can quietly change. The AI judgment layer that will run inside it does not yet exist, and the first commercial workflow is deliberately unselected —see what runs today for the exact boundary, andthe founding partner program for how the first deployment gets selected.