I can't wait until we're vibe coding construction documents.

Im vibe-coding my way through thousands of pages of specs, submittal rebuttals and FAT / SAT / Documentation requirements. All locally. AI rules.

Frankly amazing. I think liquidai released a local model that outperforms qwen recently. I haven’t tried it but can’t wait to wire it up

The speed of progress is amazing. Have you made a decision about the file format?

The model persists to a postgres database. So there is no file necessarily. However it does support IFC import and export.

Makes sense. Once each firm runs its own database, will two Mutiny users only be able to share models through IFC? Or will there be a native export that keeps everything (sheets, views, editable elements)?

This is a very good question. And it comes down to the document server. Right now it deploys as multiple containers collocated near the database. One of those is the source of truth for realtime sync. I’ll need to study how this arrangement would support interoperability between firms. This would be where the branch concept (like git) applies. You could perhaps branch the ifc model like forking a git repo so you could collaboratively iterate on someone’s live model. During that time then the document servers could just agree under the hood who is the main sync engine. I’ll have to think more on this thanks for asking!

Thank you! I love the live co-editing idea.

Part of what makes structural tricky here is that every member needs a check the engineer of record can trace and sign. I have been building a structural calculator with Claude Code, and small tested steps worked best. Happy to share notes from the structural side.

Let’s talk!

It’s not very advisable to vibe assemble construction documents. Unlike code that may not be hazardous a badly built building can be a significant problem. Creating may be fine but checking and verifying cannot be automated.

Not automated. Vibe coded. Very different concepts. Human stays in the loop. And engineers and architects still have final say on what gets shipped and stamped. Same thing happens with software. There is someone responsible for the final merge to production. I always say that we don’t validate the Boolean logic used on our calculators when they produce complex calculations. Same will likely be true based on where frontier intelligence is headed. The models will be so good that much of what we consider critical for validation today will be legacy. Like using trig tables for calculating cosin of theta

I've been following your mutinous journey and I love it!

Isn’t that a normal day today thing anyway? At least the jobs I work on, it seems like that’s the case

We're already there.

Awesome. My new favorite prompt is video gamer style. We added a 3 minute screen capture and system audio capture recently to our harness. It auto attaches to agent, transcribes, and optimized images sequences in 9x9 frame images. Always looking for ways to make the idea to agent interpretation less lossy.

Nice. I've had claude and grok work in rhino pretty well so far. Also revit but I technically can't share that.

why... are you not?

Not at full scale. zero mouse clicks in drafting applications by Q2 next year.

why are you doing this? there is no benefit to you or anyone else by publishing this.

There is no benefit to me or anyone else?

nope, just short term grat.

What do you do, Stephen hawking?

I want in! Where do I signup

Let’s do it!

Almost there...

Just followed you to keep up with this

The opportunity for tech in the MEP space is WIDE OPEN! We should have a chat - I am knee deep in the space

Keep it up guys. Almost there

can vibe code CDs since last year if you setup workflows for it. even 2yrs ago it was probably possible with the models ppl who take time to craft the workflows generally dont share them

Super interesting approach, how are you handling edge cases when scaling concurrent workloads?