An AEC project already contains design intent, constraints, decisions, and the judgment behind them. As work passes between people and software, those details separate across models, drawings, messages, and review notes.
We study which connections need to survive, then test how software can preserve them without hiding the decision or the person responsible for it.
Context should travel
A model, markup, message, and review comment can each record part of one decision. Our research asks how those records can stay connected as the project moves forward.
Learning by building
We turn questions into small experiments and keep the results inspectable. What we learn changes the next question. A useful result may become a note, a method, or a tool.
Agentic Colleague
Agentic Colleague explores how repeated AEC coordination can move across software while decisions, evidence, and approval remain visible to the people responsible.
Read about Agentic ColleagueWhat keeps repeating in your work?
Send us a recurring handoff, review, or coordination problem. We will start with how the work happens today.
Start a conversation