RULE-GUARANTOR-SET: Every LAR guarantor has an executed guaranty
| Kind | reconciliation |
| Severity | exception (blocks approval until it is overridden or a corrected re-run clears it) |
| Ruleset | v1.0 |
| Inputs | guarantor_names |
What it checks
Section titled “What it checks”Every guarantor listed on the LAR must have a Guaranty document in the package that names them. Whether each Guaranty is signed and notarized is checked separately by RULE-EXEC-SIGNATURE and RULE-EXEC-NOTARY.
How it decides
Section titled “How it decides”LAR guarantor_names are matched against the guarantor named on each Guaranty document using rules.name_normalization. The finding lists the LAR guarantors, the guaranties found and the missing names. Skipped when the LAR names no guarantors. The decision is deterministic code, not a model: extraction only supplies the values and their provenance.
Thresholds (Settings → Other options → rules)
Section titled “Thresholds (Settings → Other options → rules)”rules.name_normalization:lenient(default) orstrictparty-name comparison
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”LAR lists Daniel R. Ortega and Maria L. Ortega; only Daniel’s guaranty is in the package → exception ending “Missing: Maria L. Ortega”. This is the BK-DEMO-002 guarantor deviation.
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.