Learn
Engineering at Aedifice.
How we build agentic systems that earn the trust of licensed professionals.
A short account of our engineering culture, the constraints we work inside, and the writing we publish about the work.
Our constraints
Wren is built under four constraints that shape every technical decision. Memory is per-building and persistent; the agent does not start from a blank page on a building it has seen before. Outputs are audit-complete; every draft carries its sources and the reasoning behind them. The architecture is review-first; no work leaves the building without a human seal. Correctness is jurisdictional; a filing that is right in New York is not automatically right in London, and the system treats the two as different problems.
These constraints are load-bearing. When a design choice conflicts with one of them, the design choice loses.
How we write
We write about the work the way we do the work. Honest about trade-offs. Slow to ship. Fast to revert. A post goes up when we have learned something a licensed professional would want to know before trusting the system with a building, not when we have a feature to announce.
If you read a post and find a claim we cannot defend, write to us. We will update the post and note the correction at the bottom of it.
Featured posts
Per-building memory and why it is not RAG
Retrieval-augmented generation is a search pattern. A building’s record is a ledger. The difference matters when the reviewer asks why a filing reads the way it does.
The review queue as primary artifact
We treat the review queue as the product, not the drafts inside it. The queue is where a licensed professional’s judgement is recorded, and it is what survives the engineer of record.
Jurisdictional correctness as a testing discipline
Correctness for Wren means correctness in a specific city, under a specific code cycle, on a specific building type. We test every change against a jurisdiction matrix before it ships.
Why we stayed out of the critical path of every filing
Wren never files. A licensed human does. The post explains the trade-offs we accepted to hold that line, and the feature requests we have declined to honour as a consequence.
Work with us
Aedifice hires engineers who want to work on systems that stand behind licensed professional work. The constraints are real, the feedback loop is the building itself, and the writing is part of the job.