What people want Mutiny to do

Generate one-line electrical, flow and controls diagrams from the 3D model, plus short circuit and voltage drop calcs, easy equipment schedules, multiuser cloud and CMMC Level 2 security.

The ask: Derive one-line, flow and control diagrams from the 3D model, run short circuit and voltage drop calcs, manage equipment schedule tables easily, support multiuser cloud work, and meet CMMC Level 2.

Code-minimum checking should cover general building design too: structural loads, egress, fire ratings, insulation, waterproofing.

The ask: Extend code checking beyond HVAC to structural loads, egress, fire ratings, insulation, and waterproofing.

Prefers project-validated AI that stably finds omissions and whose results can be reviewed over flashy demos with opaque process.

The ask: Ship project-validated checking that reliably finds omissions and keeps results reviewable, not just impressive demos.

Wants companies to load their own design standards (like max flex duct run length) at fine granularity across MEP.

The ask: Let companies input granular internal design standards across MEP and have Mutiny enforce them.

Asks whether Mutiny's agent harness hits a wall with shared state across multiple agents.

The ask: Clear support for shared state and coordination across agents in the Mutiny harness.

Wants to upload a CAD or DWF file into Mutiny as a reference while modeling.

The ask: Upload CAD or DWF files as reference underlays in Mutiny.

Import manufacturer CAD models of equipment as a starting point instead of rebuilding from scratch.

The ask: Ingest manufacturer CAD as a starting point for equipment families and connections.

Validate AI checking against already-signed plans before trusting it on a live permit set.

The ask: A way to benchmark AI review against previously sealed plans and see what it misses before using it on real submittals.

Keep review notes attached to the sealed drawing so the next engineer sees what was checked, not just who signed.

The ask: Store review notes and a record of what was checked alongside each sealed drawing.

Sealed drawings should carry the design assumptions and judgment calls behind them so the next reviewer knows what they're checking.

The ask: Record the design assumptions and rationale (why it fits the brief) alongside each seal and approval so the next engineer can review and challenge them.

Quantities only count as a deliverable when the takeoff ties to standard cost rate tables and feeds estimating; interop and agents are a shell without a closed quantity-to-price loop.

The ask: Close the loop from model quantities to bill of quantities mapped to cost rate tables and estimates.

Still fighting print-and-scan plan workflows with architects.

The ask: Digital plan exchange that beats print and scan.

Wants shop drawings and submittals handled in Mutiny.

The ask: Shop drawings and submittals.

Applicant wants Mutiny to extend into interior design, which overlaps BIM but uses a different workflow and toolset.

The ask: Extend Mutiny to interior design workflows.

.NET team offering to own Revit and Civil 3D import for Mutiny.

The ask: Revit and Civil 3D importers, built on their .NET APIs.

Wants a spec for Mutiny code-check rule packages so he can package setback rules.

The ask: A Mutiny rule package spec for bylaw and setback checks.

Lessons for an AI-native tool: bring-your-own-AI instead of token upcharges, a few high-level MCP tools instead of many small ones, let AI write code, and build in immediate user feedback.

The ask: Support bring-your-own-AI, keep the MCP surface to about 10 strong tools, and build a fast feedback loop.

Suggests BIM as code: build on FreeCAD's Python BIM API with a Rust core that renders the code as BIM objects, so AI writes code instead of clicking through steps.

The ask: Let models be authored as code (Python API plus a Rust rendering core) so AI can generate BIM directly.

Wants project management, site reporting, as-builts, and pull planning merged in.

The ask: Project management, site reporting, as-builts, and pull planning.

Wants each signed change record to pin the building code edition and rule version it was checked against.

The ask: Store the code edition and rule version on every signed change record.