Our Approach
The search is the easy half
The bottleneck
Engineers spend most of a project not deciding what to build, but iterating toward a member sizing that satisfies the standards and is not wasteful. Each iteration means re-running analysis, re-checking capacities, and adjusting by hand. The drawing is fast; the search is slow.
Sizing as search
Sizing a lateral system is a sequential decision over a large discrete space of catalogue sections. That is a search problem, and search is something software is good at. We are building a system that proposes sections and an independent one that analyses what those sections do — deliberately separate, so the thing that suggests an answer is never the thing that approves it.
Why verification is the hard part
A proposal is only worth anything if it holds up, and proving that it holds up is harder than producing it. Our analysis is being verified against closed-form solutions and an independently built reference implementation before any capability is switched on. That work is in progress, and none of those gates has passed yet — which is exactly why this site does not tell you your design will be compliant, checked or approved.
What we will claim, and when
A capability gets described here after its verification passes, not before. The boundary we hold ourselves to is written down in the engineering-output disclaimer, and a build of this site fails if any page crosses it.