Build a frontier architectural organisation
VITRUVIUS™ is the agentic practice platform behind mWz Consortium — thirty-five specialist agents that research, check and assemble the technical work of a building project, so a registered architect spends their time deciding rather than compiling.
Agents draft · The architect attests
Mixed-use tower, Kuala Lumpur. 42 storeys, podium retail, plot ratio 1:6. Test the planning envelope, run egress and envelope thermal checks, assemble the building plan pack.
- CHKEgress travel distances against UBBL By-Law 165 — 34 of 34 cores pass
- CHKOTTV computed at 46 W/m² against the MS 1525 limit
- CHKAccessible route continuity to MS 1184
- FLGPlot ratio relies on a draft local plan — retrieve current instrument
- FLGFire tender access width unconfirmed by BOMBA pre-consult
Grounded in the instruments your work is judged against
Two ways to engage the consortium
Take VITRUVIUS as your technical back office, or bring us a decision that needs answering this month.
A technical bench you don't have to hire
Consortium partners run their submissions, compliance matrices and competition pursuits through the same legion. Your architect stays the author and the signatory; the compilation, cross-checking and evidence trail arrive done.
Explore the partner model →Answers before the land deal closes
Feasibility, planning-envelope tests and code exposure on a fixed fee and a stated date. You get the working — clause by clause, with every assumption named — not a slide that asserts a conclusion.
See the fixed-fee products →VITRUVIUS™ — a studio of thirty-five agents. One architect signs.
One Opus-class controller, nine practice-lead Legates, seventeen specialist Centurions and eight Auxilia, sampled from the operating models of ZHA, HOK, Foster + Partners, Gensler, SOM, BIG and Arup — and built for the Malaysian, Indonesian and GCC corridors.
Built for the way a building project actually moves
Six capabilities, one orchestrator. Nothing advances a stage until its gate is closed, evidenced and logged.
The Legion
A single engagement fans out to six to fourteen agents at once, then reconciles into one coordinated position. Where two agents disagree, the orchestrator does not average them — it states both, rules between them, and records why.
- Command tier arbitrates design intent against technical constraint
- Legates own the nine practice lines and may sub-task specialists
- Every AI-originated move is logged against the human who accepted it
- Adversarial review runs before any human sees a deliverable
| Tier | Role | Count | Model class | Representative agents |
|---|---|---|---|---|
| Tier 0 — Command | Orchestration, stage gating, arbitration | 1 | Opus | VITRUVIUS |
| Tier 1 — Legates | Practice-line leads | 9 | Sonnet | CONCIPIO STATUTA PRAXIS |
| Tier 2 — Centurions | Specialist analysis and production | 17 | Sonnet | ORDO CALOR LUMEN STRUCTOR |
| Tier 3 — Auxilia | Retrieval, QA, records, translation | 8 | Haiku | CENSOR BIBLIOTHECA NOTARIUS |
Stage Gates
RIBA Plan of Work 0–7 mapped to the local equivalent. Work belonging to a stage that has not been gated open does not get produced — which is how scope creep is caught before it is invoiced.
- Gate checklists closed, evidenced and logged before advance
- Design intent, technical fact, code requirement and assumption labelled separately
- Assumptions never travel downstream unlabelled
| Stage | Local equivalent | Gate deliverable | Lead agents |
|---|---|---|---|
| 0–1 Strategy & Brief | PAM Stage 1 | Mobilisation note, site and code exposure | SITUS PROGRAMMA |
| 2 Concept | PAM Stage 2a | Parti, envelope test, area schedule | CONCIPIO ORDO |
| 3 Spatial coordination | PAM Stage 2b | Coordinated position, planning submission | CONCORDIA STATUTA |
| 4 Technical design | PAM Stage 3 | Building plan pack, specification | TECTONICA SPECIFICATIO |
| 5 Construction | PAM Stage 4 | RFI register, instruction log | PRAXIS NOTARIUS |
| 6–7 Handover & use | CCC / SLF | Completion evidence, post-occupancy delta | CUSTODIA |
Code Register
Every clause relied on for a live project is retrieved verbatim from the current instrument and marked VERIFY until it has been. Codes are amended, states adopt national codes with local modifications, and editions supersede — so the platform cites, it never recalls.
- Applicable Code Register issued at mobilisation, per project
- Clause-by-clause check results with the retrieved text attached
- The platform never asserts compliance — it reports what was checked
| Subject | Malaysia | Indonesia | GCC |
|---|---|---|---|
| Planning consent | Kebenaran Merancang | KKPR / KRK conformity | Affection plan, plot data |
| Building approval | Local authority OSC | PBG | Municipality permit |
| Fire authority | BOMBA | Regional fire service | Civil Defence |
| Envelope / energy | MS 1525 OTTV | SNI envelope standards | Emirate green regs, SBC |
| Accessibility | MS 1184 | Permen PUPR | Universal design code |
| Completion | CCC | SLF | Completion cert. + CD clearance |
Endorsement Pack
Every regulated deliverable leaves the practice in the same shape: what was checked, by which agent, against which retrieved clause, and what remains unverified. A named registered architect reviews, corrects and signs. That signature is the product.
- A CRITICAL finding from adversarial review stops the issue
- Open items are listed, not buried — the unverified column is the point
- Authorship ledger travels with the pack for PI and competition disclosure
| Pack section | Contains | Status convention |
|---|---|---|
| Check register | Clause, retrieved text, result, evidence | PASS FAIL |
| Open items | Unverified clauses and consultant dependencies | VERIFY |
| Assumption schedule | Every assumption the work rests on, named | ASSUMED |
| Authorship ledger | AI-originated moves against human acceptance | LOGGED |
| Endorsement block | Architect review, correction, signature | SIGNED |
Compute Bridge
The agents reason; the engines calculate. Analysis agents are instructed never to compute a physical result themselves — they set up the model, invoke the solver, and interpret what comes back. That distinction is the difference between a practice and a plausible-sounding liability.
- Every number in a deliverable traces to a named engine run
- Model inputs and version are recorded with the result
- Where no solver is available, the output is marked as judgement, not analysis
| Engine | Invoked by | Produces |
|---|---|---|
| EnergyPlus | CALOR | Envelope thermal and load results |
| Radiance | LUMEN | Daylight factor, glare, autonomy |
| OpenFOAM | VENTUS | Wind comfort and natural ventilation |
| Rhino.Compute | GEOMETRA | Rationalised geometry and panelisation |
| IfcOpenShell · Speckle | MODULUS | Model audit, clash and data exchange |
Practice Memory
Every resolved detail, authority comment and post-occupancy delta is written back as a corrected practice rule. A conventional studio forgets when a project team disperses. This one does not — and that compounding is the only real moat in the model.
- Authority comments captured as reusable rules, not filed as correspondence
- Measured performance compared against prediction and published
- Correction rate per agent tracked and used to reprice the work
| Signal captured | Written back as | Used for |
|---|---|---|
| Authority comment on submission | Jurisdiction rule with citation | Pre-empting the same comment next time |
| Adversarial review finding | Check added to the gate list | Raising first-pass quality |
| Human correction of agent output | Prompt amendment, logged | Measuring where the model is weak |
| Post-occupancy measurement | Prediction-to-actual delta | Calibrating the next energy model |
Fixed fee. Stated date. Published scope.
Priced against the value of the decision, not the hours consumed. Every product ships as an endorsement pack with its open items listed.
| Product | What you receive | Turnaround | Pod | Basis |
|---|---|---|---|---|
| Planning envelope test | Buildable envelope against plot ratio, plinth, setback and height control, with the local plan clauses attached | 5 working days | Capture | Fixed fee |
| Compliance matrix | Clause-by-clause check across egress, accessibility, envelope and statutory quantities | 10 working days | Submission | Fixed fee |
| Competition capture | Go/no-go scoring through parti, site strategy, rationalised geometry, art direction and submission text | 3 weeks | Capture | Fixed fee |
| Submission pack assembly | Planning or building plan pack with a clause-level evidence trail, ready for endorsement | By programme | Submission | Stage fee |
| Consortium back office | Standing access to the legion for partner practices, with your architect as author and signatory | Retained | Full legion | Monthly |
Turnaround runs from receipt of a complete brief and site information. Regulated deliverables are issued for endorsement by a named registered architect; the approving authority determines compliance.
Scope it before you call us
An indicative shape of the engagement — agents fanned, working days, and the review load that lands on your architect.
Indicative only. Confirmed against your brief, site information and the applicable code register at mobilisation.
What partners say
Slots reserved for named references. Replace the placeholder text below with approved quotations before the site goes live.
“Quotation from a consortium partner practice on submission turnaround.”
“Quotation from a developer client on feasibility speed and decision confidence.”
“Quotation from a consultant on the quality of the evidence trail.”
Measured, then published
Large practices publish portfolios. We publish the performance gap — prediction against measurement — because it is a claim our competitors cannot match. The figures below are the platform's design targets at full establishment.
Targets, not audited results. Live performance data is published as the register of completed engagements grows.
An agentic practice fails faster, more fluently, and at scale
One fabricated clause propagates through thirty-five agents in a single cycle and arrives looking like a coordinated professional position. These are the constraints that make the model defensible rather than merely fast.
Endorsement is not optional
Planning and building plan submissions, construction documentation and completion certification are endorsed by a registered architect — in Malaysia a LAM-registered Ar. acting as principal submitting person. No configuration of this platform changes that.
Compliance is never asserted
The platform states which clauses were checked, the result of each check, and what remains unverified. Compliance is determined by the endorsing architect and the approving authority.
Authorship stays traceable
Every AI-originated design move is logged against the named human decision that accepted it — required for copyright subsistence, competition eligibility under AI-disclosure rules, and the professional indemnity position.
Analysis is invoked, not imagined
Physical results come from named solver runs with recorded inputs and versions. An agent that cannot invoke an engine reports judgement, clearly labelled as such.
Adversarial review before human review
Every deliverable is attacked by a dedicated review agent before a person sees it. A CRITICAL finding stops the issue. Nothing ships on a single pass.
Credentials stay with the principal
Platform credentials and billing sit with the consortium principal. Keys are never embedded in a shared artefact, a client deliverable or a partner instance.
Three regulatory corridors, one method
The method does not change across borders; the register does. Malaysia is the proven register — Indonesia and the GCC are added project by project, with local licensed consultants of record.
| Corridor | Registration route | Contract form | Green rating | Register status |
|---|---|---|---|---|
| Malaysia | LAM under the Architects Act 1967; Ar. as principal submitting person | PAM Contract 2018 | GBI · GreenRE · MyCREST | Proven |
| Indonesia | Architects Law registration; IAI membership | Bespoke and FIDIC-derived forms | Greenship · gedung hijau | In build |
| GCC — UAE / KSA | Municipality consultant licensing; local consultant of record required | FIDIC-based, employer amended | Al Sa'fat · Estidama · Mostadam · LEED | In build |
Nothing on this page should be cited in a submission. Clauses relied on for a live project are retrieved verbatim from the current instrument at the time of the work.
Bring us a decision that needs answering
Send the site, the brief and the date you need an answer by. We will come back with the scope, the fee and the open questions you need to close first.