What it does
get_dd_redflags returns Lexomat's authored due-diligence red-flag taxonomy for one review area as a structured scaffold — the podklady (document-type) registry and, per review area, every red-flag category with its norm references, the document types it is checked against, the authored severity band, the authored checks, remediation and report wording. The calling AI reasons over the scaffold; it does not invent categories or severities outside it.
Like every tool in this connector, it is read-only, covers Slovak law only, and its output is informational, not legal advice.
Trust model — read this first
Every served item carries a status of draft or confirmed and a confirmed_by. Today every item is draft: unratified authored content that the advocate must verify before use. The response says so on its face — a fixed Slovak ratification_notice opens the text output and is repeated in structured_content, and every line is marked [DRAFT] or [ratifikované]. The tool changes nothing about the taxonomy's status; it makes that status visible on the wire.
Inputs
| Name | Type | Required | Description |
|---|---|---|---|
area | string | Yes | The due-diligence area. Known today: real-estate-dd. An unknown value is refused with a message naming the known areas. |
review_area | string | No | Narrows to one review area of that area, e.g. tarchy. Known for real-estate-dd: title, tarchy, uzivacie-vztahy, stavebno-spravne, spory-a-konania, identifikacia-pozemkov. The podklady registry is always included. |
Returns
{
"area": "real-estate-dd",
"area_title": "...",
"document_types": [
{
"id": "list-vlastnictva",
"title": "...",
"required": true,
"missing_severity": "condition",
"freshness_days": 30,
"norms": ["..."],
"status": "draft",
"confirmed_by": null
}
],
"review_areas": [
{
"id": "tarchy",
"title": "...",
"categories": [
{
"id": "zalozne-pravo",
"title": "...",
"norms": ["OZ §151a", "..."],
"applies_to": ["list-vlastnictva", "zalozna-zmluva"],
"severity": {
"default": "condition",
"modifiers": [{ "when": "...", "then": "deal_breaker" }]
},
"checks": [{ "q": "...", "sources": ["..."], "status": "draft" }],
"needs_external": false,
"remediation": "...",
"report_wording": "...",
"status": "draft",
"confirmed_by": null
}
]
}
],
"draft_items": 32,
"confirmed_items": 0,
"ratification_notice": "..."
}
The severity scale is closed: deal_breaker | condition | price_adjustment | note. A category's severity.default is the authored band; its modifiers are the authored conditions under which the band shifts. needs_external: true means the check needs a document the spis usually does not hold (e.g. a fresh list vlastníctva) — a podklad request, never a live registry query.
Example
Useful when the calling AI is asked to review documents before a property purchase — it calls get_dd_redflags with area: "real-estate-dd" (optionally review_area: "tarchy" for encumbrances only), and gets back the checklist the review should follow: which documents are required, which red-flag categories apply to each, what to check, and how severe a finding is by default.
Notes
- Deterministic — no LLM, no database. Debits your monthly corpus quota (see Usage limits).
- Serves the authored text verbatim; it never rewrites, trims or summarises an item.
- One call returns a whole area (the podklady registry plus every review area, or one review area when narrowed).
- Does not issue a provenance receipt, so its results cannot be passed to Verify answer's
receiptsinput.