September 22, 2026
Before the engine builds anything, it has to prove it understands a business. We graded that understanding against software that already runs one, and the hard part turned out to be writing the answer key.
Read the update →
September 7, 2026
We spent months chasing one-off fixes down rabbit hole after rabbit hole, with frontier models telling us we were nearly there. The brutally honest account of why we stopped, redefined the goal, and started rebuilding the engine with itself.
Read the update →
August 18, 2026
When your business does something the pipeline has never built before, it does not freehand the code. It adds one reusable, tested building block and uses it forever. Here is the booking rule that showed us how.
Read the update →
August 11, 2026
The hard part of regenerating software is not the code. It is keeping the customers and records you already have. Here is the progress on doing that safely.
Read the update →
August 4, 2026
Before ArchitexIDE models a business or writes any code, it interviews it. How deep those questions go decides the quality of everything that follows. Here is a real one it asked, and the workflow behind it.
Read the update →
July 31, 2026
Reservations now hold a spot the moment someone starts checking out — so two customers can't grab the last seat at once, and abandoned checkouts free the seat back up on their own.
Read the update →
July 28, 2026
The apps ArchitexIDE builds now let customers log in with a passkey or a one-tap email link — no password to forget, reset, or leak — with old-fashioned passwords still there for anyone who wants one.
Read the update →