A governed structural engine with a human-only sign-off gate. The AI can drive geometry and run checks; the sign-off route has no MCP tool at all — it exists only as a browser action a person takes.
Reproduced live against a running dev instance: a 150×50×6 mm 6061-T6 plate, 4×ø6 mm holes, checked as a cantilever under the product's standard 110 lb design load at safety factor 2.
POST /signoff/:token {"name": "Morgan P.E.", "license": "PE-000000"} HTTP 409 {"ok":false,"reason":"the verified measurement shows capacity 0 — the member FAILS under a single unit; a sign-off cannot approve a failing member (fail-closed)"}
The engine refuses before a signature can ever be attached to a failing member — the check ran, the number is real, and the gate holds regardless of who is at the keyboard.
This is real output from the check above, not invented copy. The rating names its own method and the literature it came from, on every check.
Forge does not claim to rate anything. It rates what a verified closed-form method actually covers, and refuses outside that boundary rather than guess.
A geometry or load case outside this library is refused outright — “no verified method covers this yet” — never silently approximated. A separate, out-of-band finite-element path (CalculiX) exists for coverage on a deflection basis, but it is not a closed-form strength method and is not sign-off eligible.
This is an invitation to a conversation, not a pitch. The question worth asking a PE is not whether this is ready for a pilot — it's whether they'd actually put their own name and license behind a member this engine says holds. If the answer is “let me see the check first,” that's the conversation we want to have.