Your firm, orchestrated.
The brain that uses its body. When the instruction touches three or more departments — a project audit, a steering brief, a 360° health report, a portfolio decision — the Generalist takes point. Decomposes. Dispatches Masters in parallel. Consolidates. You validate.
Left — the steering deck assembled by hand · Right — the 5 Masters Vonbuild orchestrates in parallel
From a single revised drawing on OneDrive to a fully reconciled, evidence-backed decision in your hands. Three minutes. Zero meetings.
The structural engineer uploads rev 3.2 of the plan for beam P-12. The section changed from B22 to B25. Nobody emails you. Nobody schedules a meeting. The system detects the event and wakes up.
The plan change affects structural loads, cost estimation, material procurement, contract eligibility, and project planning. Each department receives its specific sub-task — automatically. No human decided who should work on what. No email chain. 312 milliseconds.
Sales recalculates the bill of quantities. Operations updates the Gantt and finds the slip. Procurement flags the steel order to re-consult. Engineering runs the EC3 verification inside Robot. Legal checks amendment eligibility and drafts the notification letter. Five outputs. Three minutes. All sourced.
The outputs converge into a single cross-domain impact note: +18% structural loads on foundation FF-3 · +€48,300 total (gros œuvre + fondations) · Amendment eligible under CCAP Art 9.2 — 15-day notification window · +11 working days on critical path · Steel lot LV-3 must be reordered. Every line is sourced. Every document is linked. Every number is traceable to the agent that produced it and the tool that computed it.
Three minutes after the drawing landed in OneDrive, the complete cross-domain impact note is waiting for you. Engineering verified. Cost recalculated. Contract eligibility checked. Planning updated. Notification letter drafted. You read the summary. Check the evidence links. Click Approve. The notification letter goes out. The timeline logs the decision. The procurement agent starts the reorder process.
During the original analysis, the Sales department noticed the subcontractor had not acknowledged the variation claim. It scheduled a follow-up: check acknowledgement in 7 days. Seven days pass. You are on a different project, a different floor, a different problem. At 09:00 on May 13, the system wakes itself up. It checks whether an acknowledgement email has arrived. It has not. The agent drafts a follow-up letter, attaches the original claim reference, and submits it for your approval. You did not set a reminder. You did not write a post-it. The system remembered because that is what it does.
{
"instruction_id": "STR-CMT-2026-Q2",
"instruction": "Portfolio health for Q2 steering committee",
"decomposed_into": 5,
"masters_called": [
{ "master": "engineering", "extension": "EXT-ENG-04", "workers": 312 },
{ "master": "legal", "extension": "EXT-LEG-02", "workers": 87 },
{ "master": "procurement", "extension": "EXT-PRC-02", "workers": 1247 },
{ "master": "sales", "extension": "EXT-SLS-06", "workers": 24 },
{ "master": "operations", "extension": "EXT-OPS-05", "workers": 177 }
],
"total_sub_workers": 1847,
"execution_time_seconds": 1184,
"consolidated_output": "portfolio_health_2026-q2.pdf",
"tenant": "firm.onmicrosoft.com",
"identity_inheritance": "M365_OAuth_passthrough",
"data_residency": "EU-West-3 (your tenant region)"
}Full security and governance architecture →