Market transition
Why now
Controls built for accountable human behavior now have to govern work performed partly or entirely by machines. The existing institutional control environment stays; what has to change is how far into the action it reaches.
wetink composition · control relocation
One control system, three states
The same system, shown three times as its worker assumptions change. Watch the worker, the decision, and the record: their positions do not move. What moves is what has to be made explicit between them.
The worker was part of the control system.
Access governance, maker-checker process, QA programs, change management, policy, and supervision surround the worker. The surviving record is intentionally thin: a file, a status, a time. That was not a deficiency. Personal accountability, reviewer knowledge, and institutional context supplied the rest, because they lived in the people doing the work, not in the record.
Machine-assisted execution enters the work.
Every control that surrounded the worker in the prior state still holds: access governance, QA, maker-checker, change management, policy, supervision, and the same thin record. The connection from decision to record is drawn unresolved, not removed: the relationship still exists, but its authority is not guaranteed, because assumptions that used to live in a human worker were never made explicit for a worker that is now partly a machine.
The old controls are still there. The problem is that some action-level assumptions were never encoded, because historically they did not need to be.
What was implicit becomes enforceable.
The existing control environment stays exactly where it was. Between the worker's decision and the surviving record, a governed write boundary now enforces the properties that used to live only in a person: actor identity, evidence, authority, separation, refusal conditions, chain state. The record stays in the same place and expands, rather than being replaced by a new object: it carries the judgment, the actor, the authority, the source, the checker, the provenance, and the prior state.
Machine participation does not eliminate institutional governance. It requires individual consequential actions to carry more of their own control state into the write path and the surviving record.
The implication
The obligation didn't change.
The worker did.
Controls built around accountable human behavior now have to govern actions performed partly or entirely by machines.
Status record to decision basis
A status log tells you what happened
It may not tell you why it was allowed to happen. Status can be evidence; the object it is missing is an inspectable decision basis.
Status
Decision basis
What became explicit
Human-operating assumptions, translated into action-level control properties
Identity
Assumed actor becomes Recorded actor
Evidence
Retrievable file becomes Persisted source anchor
Authority
Current policy becomes Applicable rule and version
Separation
Process expectation becomes Enforced resolver distinction
Refusal
Reviewer discretion becomes An invalid state cannot become authoritative where the architecture enforces refusal
History
Mutable status becomes Chained prior state
Why now explains what had to become explicit. Architecture explains how wetink enforces it. Worked example walks one governed decision carrying those relationships.
Market signal register
Market signal
Lender Letter LL-2026-04
Effective
Primary source: singlefamily.fanniemae.com (external link)
The response
The response is architectural
Machine-assisted work does not eliminate the institution's existing control environment. It requires the individual action to carry more of its own authority, provenance, and refusal conditions.