The drawings you can’t put on a vendor’s server.

• Reads specifications and CDs. Open a 200-page MasterFormat spec, a Construction Documents set, or a complex schedule, and ask questions cited back to the page. Door schedules, hardware sets, equipment schedules.
• Drafts RFIs and submittal logs. Tracked-change drafts you accept or reject in Word, with the structural and MEP context already pulled in from the relevant CD sheets.
• Compares spec versions. What changed between the 50% CD set and the 100%? What moved between the consultant’s spec and your redlined return?
• Drafts client correspondence. Letters to the owner, contractor, and consultant team. Meeting minutes from design reviews and OAC meetings. Fee proposals, scope change letters.
• Anonymises before you share externally. Strip client names, address details, and project identifiers before sharing a case study, an award submission, or a portfolio piece. Audit log per redaction.
• Reads the code book. Apply the relevant zoning, IBC, ADA, or local code section to the project at hand. The code is public; the project file is not.

AIA Code of Ethics Rule 3.401 puts the duty of confidentiality squarely on the architect: members shall not knowingly disclose information that would adversely affect their client or that they have been asked to keep in confidence. The rule was updated in 2024 and has not softened on AI use. The duty does not transfer to a vendor.

RIBA’s own 2025 AI Report shows 59% of architects now use AI, up from 41% the year before. The same report found that 86% are concerned about client confidentiality and AI. RIBA’s cybersecurity guidance is blunt: “When an architect is uploading data into an unregulated system, they generally don’t know what is going to happen with that data.” Government building drawings, masterplans for institutional clients, confidential urban-design studies, and pre-announcement campus work are the obvious examples.

• Reading and querying construction document sets.
• MasterFormat specification review and version comparison.
• RFI drafting with the relevant CD context already in scope.
• Schedule generation from drawings (door, window, hardware, equipment).
• Submittal log review and outbound submittal drafting.
• Owner-architect-contractor correspondence and meeting minutes.
• Government, defence, and institutional projects under classification or NDA.
• Award submissions and case studies, anonymised.

Autodesk shipped Assistant in Revit 2027 with an integrated MCP server that lets it operate directly on the BIM model. It is genuinely powerful and we are not pretending otherwise. It is also a cloud-mediated architecture: prompts and model context travel to Autodesk’s servers, and from there potentially to Anthropic’s, depending on the configuration.

Muet doesn’t live inside the BIM authoring tool. It lives next to it. Use Revit, AutoCAD, or ArchiCAD for the model; use Muet for the documents around it that shouldn’t leave your Mac. The two do different things.

For a small studio or solo practice, that’s less than the cost of one consulting hour. For a mid-size firm, it’s a fraction of the cost of any per-seat cloud AI subscription with the added benefit that the client’s drawings stay on the workstation they were authored on.