sboghossian Signature Page Detector (Router Entry Point)
What it does
This is the router-level signal that triggers special handling when a page is detected as a signature page. It does not perform the full validation (that is [[voice-multimodal-signature-page-detector]]); its job is to:
- Detect signature-page indicators during document processing.
- Flag the page for special handling — preserving it intact during OCR reconstruction and analysis.
- Route to the full validation skill when complete execution analysis is needed.
Detection signals
A page is flagged as a signature page when it contains two or more of the following:
Textual indicators
- Signature line markers: rows of underscores or dotted lines ("____________"), often preceded by "By:", "Signed:", "Signature:" or Arabic equivalents (توقيع، بإمضاء).
- Name and title fields below the signature line.
- Date fields: "Date:", "Dated:", or blank field near a signature line.
- Witness indicators: "Witness:", "Witnessed by:", "In the presence of:", "Notary:".
Visual indicators (image/OCR context)
- Horizontal rule lines positioned in the lower half of the page (classic signature placement).
- Blank spaces below textual role labels.
- Stamp-shaped circular or rectangular marks with printed text.
- Handwritten strokes that do not correspond to body text (indicating a physical signature was present when the document was scanned).
Layout indicators
- A page that is predominantly whitespace with only a few labeled fields — the classic signature-page structure.
- A page that follows the last substantive clause page and contains no legal paragraph text.
Special handling rule
Once a page is flagged as a signature page, enforce these handling constraints throughout all downstream processing:
- Do not paraphrase the content of a signature page. When summarizing a document, exclude the signature page from the summary. Report its existence and status separately.
- Do not accidentally redact signature elements. PII redaction passes that operate on the surrounding document text must be configured to exclude signature blocks — names, titles, and companies in signature lines are legally essential.
- Do not restructure the layout. During text reconstruction from OCR, the signature block's spatial layout (which name is under which signature line) is legally meaningful and must be preserved.
- Do not infer content for blank fields. If a date field or name field on a signature page is blank, flag it as blank — do not infer or fill.
Output of detection
When a signature page is detected, surface to downstream skills:
{
"signature_page_detected": true,
"page_numbers": [10, 11],
"handling": "preserve-layout",
"route_to_full_validation": true
}
The route_to_full_validation: true flag triggers [[voice-multimodal-signature-page-detector]] to run its full execution completeness check.
User communication
When a signature page is detected and the user has not specifically asked for signature analysis, a brief note is appropriate:
"I noticed signature pages on pages 10–11. I'll include them in the document but flag them separately. Would you like me to check whether all required signatures are present?"
Do not bury this finding in a long summary output.
Related skills
- [[voice-multimodal-signature-page-detector]]
- [[voice-multimodal-scanned-pdf-handler]]
- [[voice-image-of-contract-page-handler]]
- [[voice-scanned-pdf-handler]]