About
Who is behind wetink
Michael Silva
Founder, wetink
Designing systems for change
Years in rooms where artifacts are created, revised, reviewed, approved, and published — where the recurring question is how to know what changed, what caused the change, which policy allowed it, and who approved it.
Building in home lending
Home lending did not become interesting after the governing kernel existed. It was already a domain of deep operating experience — lending platforms, pricing and prequalification, banker tooling, home-equity experiences, servicing-transfer experiences, and regulated production systems.
Governing machine actions
A prior technical trajectory required explicit policy gates, evaluation and critic behavior, human approval where required, provider and model routing, and durable action history. That predecessor system is evidence of a technical trajectory — not wetink customer history or mortgage deployment proof. It validated an enforcement pattern that informed wetink
The collision
The collision
The same accountability question appeared in two different bodies of work.
- What changed?
- Based on what?
- Under which authority?
- Who or what acted?
- Who approved it?
- Can the action be reconstructed later?
wetink
wetink applies that governing model to consequential home-lending work, where evidence, authority, review, and historical defensibility already matter.
experience in governed change × home-lending operating experience × governed machine execution → recognition of the shared accountability problem → wetink
The name
Why wetink
Wet ink is a metaphor for accountable authorship at the point an action becomes attributable and consequential: someone or something acted, something changed, and a record now carries consequence.
Current technical state
Current technical state
wetink publishes what exists, what is enforced, and what remains unbuilt in the Architecture.
Press
Press
For press and analyst inquiries, write directly — a named mailbox, not a form.