Skip to main content

Application map

One judgment shape across home lending.

Five operating surfaces. One oversight layer. The same authority contract. A first-mortgage purchase file, a refinance, a HELOC, and a home equity loan all sit in the same verification kernel, and so do the closing table's own artifacts: a title commitment, a settlement package, an escrow ledger. The kernel is subject-polymorphic from its first migration: a loan file is the first subject, not a hardcoded one.

What changes subject · judgment · documents · rules · queue
What does not actor · authority/version · source · distinct approval · provenance · chain

What changes per surface is content. What never changes is the record.

Application status

Where each surface stands

Operating surfaces
candidate applications
Worked example
post-close QC
Delivered customer result
NO

This is the one authoritative status for every surface on this page. If it changes, this is where it changes. For current implementation state, see Architecture.

The lending coverage map

One kernel, five surfaces, one oversight layer

The existing wetink brand-primary rail beneath the five surfaces is one continuous line, not five separate blue cards. Breadth is shown through orthogonality: lifecycle surface, subject, payload, and oversight stay separate dimensions rather than one implied matrix.

The invariant authority contract

Across every surface, the record answers the same questions.

Actor
Who made the judgment.
Authority
Which rule, and exact version, governed it.
Source
Which document and page support it.
Approval
Who independently resolved or approved it.
Provenance
Machine and runtime facts, cost where relevant.
Chain
What authoritative state preceded it.

The domain changes. The authority contract does not. Every surface named below shares this one contract; none restates it.

A shared kernel does not make borrowed facts portable.

The architecture can travel across surfaces. A surface-specific regulatory or policy claim appears only with its own verified source and applicable version. Kernel portability does not create claim portability.

Post-close QC — the worked example

CANDIDATE WEDGEWORKED EXAMPLE

The mandate

Post-closing quality control is not optional. Fannie Mae Selling Guide D1-3-01 requires a lender to select, for post-closing QC review, "a minimum of 10% of the loans that it originates or acquires using a random selection methodology" (quoted from the Selling Guide; verified 2026-08-17). That floor exists because human reperformance costs real money: whole departments or outsourced audit spend, file by file. The incumbent answers are mortgage QC software that manages the sample workflow, and audit-services firms that supply the reviewers. Sampling itself is a cost compromise, not a method anyone would choose with free review.

The walk

What the QC application does with that mandate: a reviewer opens a closed loan file and checks it against the requirements that governed origination — did the file, at close, actually satisfy the applicable requirements. The review works from the loan-file documents themselves, the rules that applied to that file, and any prior findings, and it produces a finding, a rationale, a disposition, and the evidence that supports it. Sampling decides which closed files reach a reviewer this cycle; it does not change what gets checked once a file is pulled — the same requirements, the same documents, the same disposition categories, whether the file arrived through the 10% random sample or a full-population pass.

The domain record

Primary subject loan file
Domain inputs loan-file documents, applicable rules, prior findings, supporting evidence
Domain output finding, rationale, disposition, supporting evidence
Control today human post-closing QC review, internal or outsourced as applicable
Architecture design basis full-population reperformance, every-file addressability
Product truth architecture exists for this basis; not a delivered customer result unless and until that status changes
Minimum random sample 10%
Addressable population 100%
Delivered customer result NO
A design basis, not a delivered customer result.

Verify and source the current regulatory number before publishing anything that quotes it; this page is not the authority for a time-sensitive regulatory requirement.

The operating surface register

Comparing the five surfaces on what actually varies

Operating surfaceJudgment being madeHuman attestor today
OriginationAre the required documents present and interpreted correctly?Processors / underwriters.
UnderwritingDid returned evidence actually satisfy the condition?Underwriting operations / staff clearing conditions.
Closing / fundingIs the file complete and consistent before funds move?Closers / funders / settlement or escrow actors.
Post-close QCDid origination satisfy applicable requirements?QC / audit reviewers.
Servicing transferDoes boarded state match the reviewed/agreed state?Transfer / boarding teams.

This table compares only the dimensions that genuinely vary. What every surface's record contains regardless of surface is stated once, above, in the authority contract.

Application doctrine 02

The loan file is the first subject. It is not a hardcoded one.

A subjectis the object whose judgment state the kernel governs. The register below shows the loan subjects and closing-table subjects the architecture already accommodates.

Loan subjects

  • Purchase
  • Refinance
  • HELOC
  • Home equity

Closing-table subjects

  • Loan file
  • Title commitment
  • Settlement package
  • Escrow ledger
This shows architectural capability, not a claim that every subject and surface combination is already modeled or deployed.

The oversight layer

Oversight consumes the record.

Origination, underwriting, closing, QC, and servicing produce governed records. Risk, compliance, investors, or examiners can later ask what happened across those surfaces and receive an inspectable account, rather than reconstructed testimony.

Suggested questions

What judgment was made?
By whom?
Under which rule and version?
From which source?
Who independently resolved it?
What authoritative state followed?

Fannie Mae's LL-2026-04 makes disclosure-on-demand a live obligation across origination and servicing; the details are in the explainer.

Where to go next

Inspect the enforcement model, Architecture
"I understand where this applies; show me how the authority boundary works."

Walk the post-close case file, the worked example
"I understand the umbrella; show me one judgment end to end."

Select the first governed surface.

The architecture is broad. A commercial deployment should be narrow, paid, production-bound, and explicitly scoped.