RULE-EXEC-SIGNATURE: Required signature blocks are signed
| Kind | execution |
| Severity | exception (blocks approval until it is overridden or a corrected re-run clears it) |
| Ruleset | v1.0 |
| Inputs | execution zones from the locate stage (execution_checks) |
What it checks
Section titled “What it checks”Every signature block the execution template requires for the document type must carry a signature.
How it decides
Section titled “How it decides”The locate stage reports each required zone (borrower, lender, guarantor…) as filled or empty; every empty signature zone is an exception, with one finding per document listing the zones and pages. The required zones per document type come from the execution templates (setting execution.templates). The decision is deterministic code, not a model: extraction only supplies the zone results and their provenance.
Thresholds (Settings → Other options → rules)
Section titled “Thresholds (Settings → Other options → rules)”- none (no bank-policy threshold applies)
The thresholds in force are recorded on every reconciliation run. An administrator can switch this rule off under Settings → Rules; a disabled rule is skipped by later runs, and the skip is recorded on each run and in the evidence chain.
Example
Section titled “Example”BK-DEMO-003: the Note’s borrower signature line is blank → exception on the Note listing borrower_signature (p.3).
Resolution
Section titled “Resolution”Correct the documents and re-process the package (a new reconciliation run is created; nothing is edited in place), or override the finding with a reason code from review.reason_codes and a written justification of at least review.justification_min_length characters. Overrides need the manager or administrator role. Accepting an exception records that a person reviewed it but does not clear it. Every action is recorded in the finding history and the evidence chain.