About AirOrchestra
Who built the architecture, what problem kept showing up, and how others can use it.
Who builds it
Two people. Sergey Sysoev works as a union sheet metal installer in the Pacific Northwest and has spent his working life on commercial mechanical jobsites. Andrey Tcelikov works in commercial HVAC operations, closer to the office side — estimating, scheduling, the paperwork the field never sees. The architecture is built around their day jobs, not instead of them. That matters because the system stays honest: every change has to survive contact with a real crew the next morning.
Why we built it
Every commercial HVAC operation seen up close has the same two problems, and neither of them is about technology.
The first is knowledge drain. The senior guys know how the company installs a VAV box, how it sequences a rooftop unit, which fittings get used where, why a particular detail matters on a particular job. That knowledge lives in their heads and leaves when they retire or move on. Nothing captures it.
The second is phone tag. A crew in the field has a question. The journeyman calls the foreman. The foreman calls the PM. The PM digs through a shared drive, a submittal log, or an email chain from four months ago. Thirty minutes of three people's time gets spent finding something that was already written down somewhere. The job waits.
Both problems share a single shape: knowledge that should live in the company keeps living in individual heads. The four constraints — fixed role, fixed source, fixed scope, citation or refusal — are the mechanism by which that locus moves. Every question becomes a logged interaction, every answer a cited document, and the indexed corpus deepens at the rate the operation already runs. The work is the same; the residue is different.
How others can use this
The architecture is built and operated inside one HVAC company. The constraints, the prompts, the retrieval rules, the lint-at-ingest checks, and the post-processing gate are described across this site so other operations can build their own. If you run a similar company and want to compare notes on what worked, what failed, and what we would do differently, write.