Building a foundation sizing tool where the AI part doesn't get to pick anything
It organizes the request, asks questions, looks up methods. The engineer OKs every assumption and the math runs in deterministic, tested code
Missing data stays pending, never passes by default
What the API for my foundation design tool looks like so far. Column, soil and materials in. Footing size, rebar and the checks out
Still in development, but it runs the same engine as the app. Engineer review comes back as not reviewed until a person does it
Every change in the foundation tool that moves a number the user sees, or flips pass, fail or pending, ships with a decision file in the same commit
Context, sources, decision, alternatives, effect, how it was checked. Agent-made calls need independent review before merge
An optional input in the foundation tool showed 0 on screen while the engine got undefined. The check that used it just disappeared and the footing could pass
A half-filled pair stays pending now. In the repro, actually typing that 0 made the same footing fail
burned through all 2,000 free github actions minutes this weekend lol. lots of shipping, a bit of engineering, a bit of the action rpg i'm building. any open source ci you'd self-host on a vps?
A pile result has several checks and the screen shows one as the reason. It was picking a pending check even when a firm failure was in the same list
A sweep of 1296 inputs found 392 like that. A firm failure goes first now
Angular distortion in the foundation tool was only checked for the combination with the most settlement. A lighter one can be worse if the neighbor settles more
One case showed 1/1084 and passed. Real worst was 1/277, limit 1/300. Every service combination is checked now
The foundation tool's screen showed the first column as the load origin while the calc was using values typed by hand. Nothing passed because of it, but the screen named a source that wasn't true
Now it asks you to pick the origin and stays pending until you do










