A new category gets misread through the nearest familiar one, and every misreading costs a conversation. Cheaper to state the boundary plainly:
Not a loan origination system
Wet Ink does not originate, process, or decision loans. It records and governs the judgments other systems and people make about them.
Not a generic copilot or chatbot
Nothing here drafts your emails or summarizes your documents on demand. The kernel governs actions; it is not a conversational assistant.
Not a title production system
It does not produce commitments, policies, or settlement documents. Title work is one candidate surface where its record shape may apply — candidate, not product.
Not a document repository
Documents matter here as evidence — cited by page, hashed, anchored to judgments — not as storage. Your system of record for documents stays yours.
Not a speed-first closing processor
If a vendor already closes your files faster, Wet Ink does not race it. The question it answers is whether anyone can defend what the fast process did, months later.
Not a consulting practice
Engagements produce working, governed capability with defined deliverables — never advisory hours, and never unpaid product discovery.
Four insertion patterns are on the table — embedded, exception lane, audit layer, or one independent governed workflow. The first partner reveals which has real budget and low integration friction.
The layer it occupies
Wet Ink is the governed execution, verification, and evidence layer around machine-assisted regulated work: who or what did the work, under which version of which rule, citing which page of which document, approved by whom — sealed in a record built to be checked. Which workflow that layer wraps first is deliberately unselected; the founding partner chooses the wedge, and until then the six surfaces on the home-lending page are candidate applications of one kernel — each labeled as such there, none a shipped feature.