The calc you stamped
isn't the calc you have.
Every engineer knows the Monday: the span changed on Friday, the spreadsheet was updated, the Word report wasn't, and the model belongs to another team. Three artifacts. Three different truths. One signature: yours.
Logic you can't review.
That formula is load distribution across a six-pile group, but nothing on screen says so. Cell references hide engineering intent, so checking means reverse-engineering. And on most projects, that means it doesn't happen.
model updated 12 Nov
Deliverables that rot.
The PDF was true the day it was printed. Four days later the founding level changed and the report didn't. Now the stale copy carries your stamp while the truth lives in somebody else's file, and nobody is sure which numbers were checked.
Units on the honour system.
Spreadsheets will add anything to anything. A kip that should have been a kilonewton survives every review that doesn't recompute by hand: the exact class of silent error behind some of the industry's most expensive failures.
Every copy is maintained by hand. OctoMeta removes the copies: one graph underneath, so nothing to reconcile, nothing to go stale, nothing to take on faith.
Position is for humans.
Order is for the graph.
Your document reads top to bottom. It computes by dependency, never by where a block sits on the page. No hidden state, no run-order bugs, no stale cell three tabs away.
Every number carries its units.
Dimensional mismatches surface as typed errors, not silent bugs. Ask for the full substituted derivation on demand, so a checker reads the logic, not cell references.
"Show steps" renders the derivation with values and units substituted. Mixing dimensions is a typed error that propagates, never a silent wrong number.
Geometry is a first-class value: formulas return content-addressed handles into a real B-Rep kernel. Scalars unbox straight back into ordinary math.
Type a formula.
Get a footing.
=EXTRUDE(plan, t) returns real B-Rep geometry, computed by a proper CAD kernel, live in the viewer. Pick a cell, highlight the object, and back again. No export, no round-trip, no separate tool.
From calc to PDF and IFC. One artifact.
Your calculation isn't transcribed into a deliverable. It is one. Export a paginated report and a schema-valid IFC4X3 model from the same graph; nothing to reconcile.
Paginated, submission-ready. Show-steps included where the checker needs them.
The geometry you calculated is the geometry you deliver, straight into the BIM workflow.
Every value knows how it was derived, who authored it, and whether it's been checked.
Reviewable by design.
Provenance and "show steps" make verification fast and trustworthy: a workflow made for ISO 19650-style checking, not bolted on after.
Connected to the tools you already run.
The numbers you need already exist: in Revit models on Autodesk Construction Cloud, and in the business systems that hold your rates and quantities. OctoMeta binds them into the graph instead of asking you to retype them.
Autodesk Platform Services publishes official MCP server samples for its AEC Data Model API: Revit elements on ACC, queried over GraphQL, no plugins. OctoMeta consumes exactly this class of server, so a bound element property enters the graph with provenance, like any other input. The same pattern reaches the MCP server in front of your ERP: unit rates land in the same checked graph as your quantities.
First connectors ship read-only: Revit via APS, plus any MCP server you already run. Exposing the document graph as its own MCP server is on the roadmap, built on the same mutation API.
Model data and cost data meet inside one graph. Bound inputs carry provenance (source, query, pull time), and the whole document recomputes when they're refreshed: checks, cost and geometry together.
Every edit flows through one typed API, with provenance built in, so when AI arrives, it's just another careful reviewer, not a bolt-on.
For structural, civil & infrastructure engineers: design engineers, checkers, and BIM leads who are done reconciling spreadsheets, Word calcs, and models by hand.
Test the platform first.
We're onboarding a small group of structural and civil teams. Bring a real calc package; leave with a document that recalculates, verifies, and exports.
- Private beta is free; we ask only for honest feedback on real work.
- Founding Engineer pricing locked for beta users who continue.
- One email when your invite is ready. Nothing else.