Catch spec contradictions before they become change orders. AI that cites every clause.

Yes. The agent detects whether section numbers follow MasterFormat 2016 (six-digit, e.g., 23 05 00) or MasterFormat 1995 (five-digit, e.g., 15820) and applies the correct discipline mapping. Many renovation projects, institutional owner master specs, and older project manuals still use the legacy numbering.

The agent uses a section-pair chunking strategy for large specs. Rather than loading 500+ pages at once, it builds a cross-reference index first, then loads and compares related section pairs. This means a 1,000-page project manual is analyzed as a series of targeted comparisons — each discipline pair checked independently. Processing time scales with the number of discipline pairs, not the total page count.

The built-in standards watchlist covers ASTM (A36, A992, A572, A615, C150, C33, E84, E119, C920), ANSI/ASHRAE (90.1, 62.1, 55, 15/34), NFPA (13, 72, 70/NEC, 101, 90A), IBC/IRC/IECC, ACI (318, 301, 530→TMS 402/602), AISC (360, 341, 303), and AWS (D1.1, D1.4). It flags withdrawn editions, missing edition years, and commonly confused standards. For standards not on the watchlist, the agent states that status could not be verified rather than guessing.

No. Your specification documents, findings, and RFIs are processed only to deliver the service and are never used to train foundation models. Each project gets an isolated workspace — no cross-tenant or cross-project access. Construction specs often contain proprietary design details and client-sensitive information; Rakenne’s architecture isolates every project.

Yes. Every skill is written in plain text — you can fork a skill, add conflict patterns, modify the standards watchlist, or adjust the RFI template to match your firm’s format. The Skill Workshop template lets you author and test custom skills interactively. You could add a check for your firm’s specific standards (e.g., a utility company’s supplementary specs) without any programming.

InspectMind focuses on drawing-side plan checking — coordinating architectural, structural, and MEP drawings for conflicts. Rakenne focuses on the specification text — the written requirements that govern what gets built. These are complementary: InspectMind catches conflicts visible in drawings; Rakenne catches conflicts in the written requirements. Document Crunch focuses on contract risk — identifying liability, insurance, and payment terms. Rakenne’s spec consistency check focuses on technical contradictions — voltage mismatches, material conflicts, fire rating inconsistencies. Again, complementary: Document Crunch asks ‘is this contractually risky?’; Rakenne asks ‘does this technically work?’