Real case: when AI doesn't just read, but recalculates (in-depth audit)

Anonymised real case. New-build single-family home, in-depth audit (Lince) with the D-LINIEX AI verifier.

A standard audit reads and cross-checks the documentation. The in-depth audit (Lince) also verifies the numbers and connects each finding to the applicable case-law doctrine. On this project, the difference was clear.

What it verified numerically

• CTE DB-SE: checking that the ELU/ELS verifications were documented, not merely stated.
• DB-SE-C: a genuine cross-check between the geotechnical survey and the foundation sizing.
• DB-HE1: limit transmittances contrasted numerically, not "by declaration".
• DB-HR: acoustic justification with values, not generic.
• DB-SI 6 / REBT / DB-HS4-HS5: fire resistance and installations with verifiable calculation.

The preventive legal layer

This is where "case law in document form" comes in. Each critical finding is accompanied by the liability framework it triggers:

• LOE Art. 17 — ten-year liability (structural damage), three-year (habitability) and one-year (finishes).
• Art. 1591 of the Civil Code — the historical doctrine of ruinous defects, which the Supreme Court has consolidated over decades for serious damage that compromises the building's soundness or habitability.

We do not invent judgment numbers: we work with the consolidated body of doctrine and with ranges of amounts documented in the sector, so that the technician understands not only what fails to comply, but how much it might cost them and how to protect themselves before signing.

The in-depth audit is like going from "I'll read your project to you" to "I'll recalculate it for you and explain how to defend it if someone makes a claim one day".

---

Want the reinforced analysis for a sensitive project? Discover the verifier and in-depth mode.