IFC INTENT — WINDOWS PREVIEW 0.1 An offline IFC review application with reusable modeling instructions and a local Revit generation connector. INSTALL ON YOUR COMPUTER OR ANOTHER WINDOWS COMPUTER 1. Run IFC-Intent-Setup-0.1.0.exe. The offline installer includes the viewer, IFC engine and Revit connector builds. Node.js, Python and developer tools are not needed. 2. Open IFC Intent from the Start menu or desktop shortcut. 3. For viewing and exporting, Revit and an internet connection are not required. 4. For native RVT/RFA generation, install and license the target Revit version on that computer. In IFC Intent, open Settings > Install / update Revit connectors, then restart Revit. Revit may ask whether to load the unsigned connector; identify IFC Intent before choosing to load it. 5. In a desktop chat that supports local MCP tools, add the connection shown in IFC Intent's Settings. Each computer has its own executable path and connection. Connectors do not travel inside a shared instruction ZIP. The installer and add-in are unsigned preview builds. A publisher signing certificate has not been supplied. Keep project backups and validate generated models before production use. REVIEW AN IFC Open .ifc, a single-model .ifczip, an .ifcintent saved project, or an instruction ZIP with its matching IFC. Select elements in the 3D viewer or searchable tree. Ctrl/Shift-click selects multiple elements. Double-click a tree element to fit it in the view. Use the viewer controls to fit, isolate, fade other elements, section, or look from above. The tree groups elements by IFC class or spatial location. Very large groups display the first 500 entries; search to reach any element. The source IFC class and assigned type are shown. Optional target fields record IFC class, Revit category, family and type overrides. They do not alter the source IFC geometry. NOTES AND REFERENCES Create one or more notes for a selection, with text, PDF or image attachments. Each attachment may be up to 50 MB. Use the Note library to link an existing instruction to other elements. Editing a shared note updates every use. Duplicate a note to make an independent variation. Unlink a note from a selection using its X button. Attachments open in the computer's default image/PDF application for review. SAVE AND EXPORT Save project writes an .ifcintent ZIP containing the original IFC, assignments, note library and attachments. Ctrl+S saves; Ctrl+Shift+S saves another copy. Ctrl+O opens a model/project. Prepare for ChatGPT asks for the final modeling prompt, RVT/RFA/both and target Revit version. It exports an instruction ZIP containing manifest.json, START_HERE.txt and reference files. Upload the ZIP beside the original IFC and, optionally, a project RTE. The package carries the IFC's SHA-256 fingerprint and stable element identities. A mismatched source file is rejected. Keep the original IFC and export together. CREATE NATIVE REVIT FILES Revit must be open with the local connector loaded. In the connected desktop chat, ask it to read the exported instructions, inspect the IFC and attachments, inspect any supplied RTE, and use IFC Intent's tools to create and validate the requested files. The connector exposes status, template discovery/inspection, package extraction, generation guidance, C# compilation/execution and job results. Generation code runs locally with your user permissions and can use the Revit API. Use a trusted chat and inspect its planned operation. The connector creates new output documents and saves files beneath Documents\IFC Intent\Outputs\. It validates native file metadata and output version. ChatGPT must also check modeling requirements, dimensions, constraints and family behavior; metadata checks alone do not establish BIM quality. The generation tools create files on the connected computer. Whether those files appear as downloadable chat attachments depends on the chat's local-file capabilities; actual output paths are always returned. Revit 2022–2026 connector builds are included. Both original .NET 8 and updated .NET 10 editions of Revit 2025/2026 are handled automatically. The Revit 2027 connector is compiled against the 2027 API but remains experimental until tested inside Revit 2027. Each target year requires a corresponding Revit engine. Revit cannot save a newer file back to an older file format. System families such as walls are stored in RVT projects, not standalone RFAs. RFA output applies to loadable families. New loadable families require suitable RFT templates; an RTE alone is not a family template. PREVIEW LIMITS The IFC engine supports the IFC2x3, IFC4 and IFC4x3 families, subject to supported geometry and valid source data. Unsupported or missing display geometry is reported; those elements remain in the tree. IFCXML is not supported in this preview. No application can guarantee arbitrary malformed IFCs or unlimited model sizes. Project archives are limited to 2 GB unpacked; IFCZIP import is limited to 1 GB unpacked. Revit authoring is guided by the connected chat and source information. This is not a deterministic universal IFC-to-parametric-Revit converter. Complex elements may need additional instructions, specialized family templates or explicitly reported geometry fallbacks. Inputs, saved projects and instruction exports stay on the computer until you choose to share them. ChatGPT's analysis step uses its own connection and account. UNINSTALL Use Windows Installed Apps to remove IFC Intent. The uninstaller removes this app's connector registrations. Saved projects and generated outputs are retained. Remove the IFC Intent MCP entry from the chat settings when it is no longer needed. DEVELOPMENT The source uses Electron, React, Three.js and web-ifc. Dependencies are pinned in pnpm-lock.yaml. Install with pnpm install. Place the Windows x64 Node.js runtime and its LICENSE.txt in .tools/node. Build with pnpm build, test with pnpm test and pnpm qa, package with pnpm dist. UI QA uses Playwright's Electron driver. Revit connector source is in connector/App.cs. scripts/build-connectors.ps1 builds against installed 2022–2026 APIs and optional baseline/2027 reference assemblies under .tools/revitrefs. Build-only API references are not distributed in the application. See THIRD-PARTY-NOTICES.txt for third-party licenses.