TraceBIM/Proof

Test run, September 4, 2026

One house, 33 sheets, and the findings log published next to them.

Cedar Lane Residence is a four-bedroom, two-and-a-half-bath, two-storey house with an attached two-car garage. It was drawn from an empty project to a full construction document set inside TraceBIM. Every file that came out of that run is on this page, and so is every fault the run turned up.

The sheets download as vector PDF. The model downloads as an IFC4 file and as a Revit exchange package. Open them in your own software and check the line weights, the dimensions, and whether the stated scale is the drawn scale.

Start a project Download the set Read the 42 findings

No blockers, 17 major findings, 7 of those still open. All 42 are published in full.

33 sheetsG, C, A, S, M, E, P and L series; 28 downloadable, 5 held pending re-export
674 elementsacross 4 levels and 47 views in one model
3,091 IFC instancesin the IFC4 file published below
42 findingsfrom the run, published with their severities

What this is

A single project was taken from an empty file to a 33-sheet permit set using every TraceBIM feature at least once. The house was designed through 42 authored rounds in the chat panel, then worked on directly in the studio for feature coverage, then exported. The drawings on this page are exactly what TraceBIM's own exporters produced. Nothing was touched up in another program.

Two things about the run have to be said before you open anything. First, no Anthropic key was available in that environment, so the model's reply was stubbed at the network layer. Everything downstream of the stub is production code: action validation, the review card, the parametric model, the sheets, the renderer, and the exporters. So this set is evidence about the drawing machinery, not about the model's judgment. Second, the set was exported through Issue for Permit in a test environment, against a made-up address. No permit was applied for, anywhere.

TraceBIM proposes and you approve. Every change the assistant suggests arrives as a list of actions you apply or reject, sheet by sheet. Nothing lands in the drawing because the model decided it should.

Permit rules are local. Many US jurisdictions accept plans prepared by the property owner or the contractor for certain residential work, but the rules are local and it is your responsibility to confirm them with your building department before you submit. TraceBIM is a drafting tool, not a licensed architect or engineer. It does not check drawings against a building code, and it does not approve, stamp or seal anything.

The sheets exported through Issue for Permit carry an issuance record in place of the "DRAFT — NOT FOR CONSTRUCTION" stamp. That record says what the person exporting the set attested to: their role, the jurisdiction they named, and three confirmations they ticked. It is not an approval and it is not a stamp. Every other export path still prints the DRAFT stamp.

Run folder: docs/test-runs/2026-09-04-cedar-lane-cd-set/. Model census: scripts/model-stats.json (674 elements, 47 views, 33 sheets; levels FOUNDATION −3', Level 1 0', Level 2 10', ROOF BEARING 19'). Attestation wording: legal/PERMIT_ATTESTATION.md.

The sheet index

Thirty-three sheets, eight disciplines, one model.

This is the drawing index as the set carries it. Each sheet number links to that sheet's vector PDF, the same file the product wrote.

SheetTitleDisciplineSheet scale
G0.00COVER SHEET, SHEET INDEX & PROJECT LOCATIONGeneral1" = 1'-0"
G1.00PROJECT INFORMATION & CODE ANALYSISGeneral1" = 1'-0"
G2.00GENERAL NOTES, SYMBOLS & ABBREVIATIONSGeneral1" = 1'-0"
C1.00SITE PLANCivil / site1" = 10'-0"
C2.00GRADING & DRAINAGE PLANCivil / site1" = 10'-0"
C3.00UTILITY & EROSION CONTROL PLANCivil / site1" = 10'-0"
A1.01FIRST FLOOR PLANArchitectural1/4" = 1'-0"
A1.02SECOND FLOOR PLANArchitectural1/4" = 1'-0"
A1.03ROOF PLANArchitectural1/8" = 1'-0"
A2.01 heldEXTERIOR ELEVATIONS — FRONT & RIGHTArchitectural1/4" = 1'-0"
A2.02 heldEXTERIOR ELEVATIONS — REAR & LEFTArchitectural1/4" = 1'-0"
A3.01 heldBUILDING SECTIONSArchitectural1/4" = 1'-0"
A3.02 heldWALL SECTIONSArchitectural1" = 1'-0"
A4.01ENLARGED PLANS — KITCHEN & BATHROOMSArchitectural1/2" = 1'-0"
A5.01 heldINTERIOR ELEVATIONSArchitectural1/4" = 1'-0"
A6.01DOOR & WINDOW SCHEDULESArchitectural1" = 1'-0"
A6.02ROOM FINISH & FIXTURE SCHEDULEArchitectural1" = 1'-0"
A7.01STANDARD ARCHITECTURAL DETAILSArchitectural1" = 1'-0"
A7.02MILLWORK & CASEWORK DETAILSArchitectural1" = 1'-0"
S1.00STRUCTURAL GENERAL NOTES & DESIGN CRITERIAStructural1" = 1'-0"
S2.00FOUNDATION PLANStructural1/4" = 1'-0"
S3.01FIRST FLOOR FRAMING PLANStructural1/4" = 1'-0"
S3.02SECOND FLOOR FRAMING PLANStructural1/4" = 1'-0"
S3.03ROOF FRAMING PLANStructural1/4" = 1'-0"
S4.01STRUCTURAL SECTIONS & DETAILSStructural1" = 1'-0"
M1.00HVAC FLOOR PLANS & EQUIPMENT SCHEDULEMechanical1/4" = 1'-0"
E1.00ELECTRICAL POWER & DATA PLANSElectrical1/4" = 1'-0"
E2.00REFLECTED CEILING / LIGHTING PLANSElectrical1/4" = 1'-0"
E3.00PANEL SCHEDULE & LOAD CALCULATIONSElectrical1" = 1'-0"
P1.00PLUMBING FLOOR PLANSPlumbing1/4" = 1'-0"
P2.00WATER & SANITARY RISER DIAGRAMSPlumbing1" = 1'-0"
L1.00PLANTING & HARDSCAPE PLANLandscape1" = 10'-0"
L2.00IRRIGATION PLANLandscape1" = 10'-0"

Scale is the sheet scale printed in the title block. Schedule, note and detail sheets carry the sheet default of 1" = 1'-0"; where a detail on those sheets is drawn at another scale, the scale is noted beside the detail. Titles and scales come from scripts/sheets.json in the run folder and match the title blocks in the PDFs.

What the S, M, E and P sheets are. They are drafted documentation. TraceBIM does no structural analysis, no load calculations, and no MEP coordination, and it never will on the basis of these sheets alone. The engineering behind a real set of those sheets is an engineer's work. Sheet G1.00 is titled "project information & code analysis" because that is what a permit set carries: the content on it was written by the person running the test. TraceBIM does not check drawings against a building code.

The files

Open it in your own software.

Nothing here is a picture of a drawing. The sheets are vector PDFs that plot to scale, the model is an IFC4 file, and the Revit download is an exchange package with its own import script.

PDF ×28 Vector sheets, one file per sheet True vector, plots to scale, about a second per sheet to export. Download them from the sheet index above. 940 KB IFC CedarLaneResidence.ifc IFC4, DesignTransferView, millimetres. 3,091 instances: 48 walls, 26 windows, 19 doors, 24 spaces, 12 columns, 6 beams, 5 slabs, 3 roofs, 1 stair, on 4 storeys. 196 KB ZIP Revit exchange package A versioned JSON model, a pyRevit import script, and a README. It is not a .rvt file and it is not a link to Revit. 218 KB

What the IFC file is, and is not. Fifteen of fifty element types reach IFC: walls, doors, windows, floors, ceilings, roofs, columns, beams, curtain walls, stairs, ramps, elevators, rooms, grids and levels. The other thirty-five are treated as annotation and are absent from the file rather than approximated. It is an architect's handoff file, not an engineer's analysis model: no element quantities, no structural profiles, no MEP subtree. A consultant can open it and coordinate against it. They cannot run their analysis from it.

The exporter's output has been checked with a third-party toolkit. IfcOpenShell 0.8.5 parsed a fixture export as IFC4 at 445 entities and built 12 of 12 solids with zero failures. That check was run against the fixture project, not against the Cedar Lane file on this page.

TraceBIM exports IFC, and does not import it. There is no DWG or DXF import either, and no round-trip with Revit of any kind.

IFC evidence: packages/engine/src/io/ifc/, wired at apps/web/src/main.ts:7143; validation record at docs/competitive/part00b-interop-update.md. Revit exchange package: packages/engine/src/io/revit/.

On screen

The same sheets in the studio.

Four of the thirty-three, as the studio renders them after the September 5 fix pass. The PDFs above are the export of these views.

Screenshots: docs/test-runs/2026-09-04-cedar-lane-cd-set/screenshots/after-fix/.

What held up

The parts of the run that worked.

Vector sheets that plot to scale

Every sheet exports as true vector through the single-sheet path, at about a second a sheet. The stated scale in the title block is the drawn scale: A1.01 prints 1/4" = 1'-0" and measures that way on paper.

One model behind every sheet

674 elements, 47 views and 33 sheets came out of a single parametric model on four levels. Plans, sections, elevations and schedules read the same geometry, so a change to a wall is a change everywhere that wall appears.

Issue for Permit, end to end

The attestation was recorded against the account, the finished PDF was fingerprinted, and the issuance footer replaced the DRAFT stamp on all 33 sheets. The record keeps the role, the jurisdiction, the sheet list, the time, and the file's fingerprint.

The model survived the abuse

Roughly 1,000 assistant actions and 70 hands-on steps ran with no uncaught page errors, and undo and redo held through mixed assistant and manual edits. The only console errors were the expected ones from the stubbed AI routes.

Openings really cut

The 3D view renders the house from the same graph the drawings come from: stacked storeys, three roofs, the garage, and hosted doors and windows cut through the walls they sit in. The IFC file carries 45 opening elements with their void and fill relationships.

The test suite ran green

During the run, 787 engine tests and 131 web tests passed, and the propagation demo printed its intentional cycle capture. The repo now carries 161 test files.

What it got wrong

The findings, published next to the drawings.

A set you cannot criticise is not evidence. Here is the whole log: 42 findings, their severities, which ones are fixed, and which faults are visible in the files you just downloaded.

SeverityCountWhere they stand
Blocker — could not produce a required deliverable0The set was produced.
Major — workaround needed, or wrong output179 fixed in the product, 1 partly fixed, 7 still open.
Minor — polish14Several fixed in the September 5 pass.
Gap — the feature is not there4Listed below, not softened into "coming soon".
Note — observation, no defect7Includes the test results and the stability record.

Faults you can see in these files

These downloads were exported on September 5, 2026. Two major rendering faults were fixed after that date, and the files still show the old behaviour. We are publishing them as they were rather than re-exporting a flattering set.

F-041 Elevations and sections are diagrammatic in these PDFs. At export time, A2.01, A2.02 and A3.01 drew every edge of every element with no hidden-line removal, roofs came out as bounding boxes, and there was no grade line, no level datums and no vertical dimensions. Fixed on 2026-09-10 — hidden-line removal against wall faces, roof planes and casework, level datums, a grade line and a floor-to-floor chain. That pass also found that every elevation and section had been mirrored left to right. These files predate all of it.
F-040 Sheet A5.01 carries no usable content. The eight interior elevations generated for the kitchen and powder room all rendered the same plan-like fragment instead of four different walls each. The quad tags were placed and the views were titled, but the sheet is empty of real elevations. Fixed on 2026-09-10 — each view now resolves its own frame and is cropped to its room. These files predate the fix.
F-032 The combined permit PDF is raster, not vector. The multi-sheet set rasterises every sheet at 150 dpi. It took nine to eleven minutes in headless Chromium and produced a 14 MB file, with the export ribbon locked and no progress indicator. The single-sheet vector path takes about a second a sheet, which is why the per-sheet PDFs above are the ones that plot to scale. Still open.
F-034 The wall-types tile prints empty in vector. The "wall types — in use" catalog tile exports its frame and its label but not its contents in the vector path. The raster path draws it. The drawing index, schedules, legends and notes do export in vector. Still open.
F-013 … F-022 The first export of this set was unusable. Every sheet came out covered in linework that belonged to other sheets: annotation was scoped only in one render path, drafting frames projected into every plan, and the load-time auto-fit collapsed plans to a dot whenever site content sat away from the building. Fixed on 2026-09-05 across every render path, and the project data was cleaned up. The files on this page are the re-export.

Still open in the product

The seven major findings that have not been fixed, as of this page.

F-005 Duplicate level datums. A new project seeds a level called "Level 1". Adding a level with that name creates a second datum at the same elevation, and references by name become ambiguous.
F-008 Custom wall types do not follow you to another device. A wall type you define is written to the server, but the studio reads its registry from browser storage. Open the project in a different browser and those walls fall back to a generic thickness and lose their layer and fire-rating definition.
F-020 One documented API endpoint is a stub. PATCH /projects/:pid/elements/:id records the mutation and marks the graph dirty, but never applies the payload. State changes all go through the client's graph upsert.
F-023 Delete removes a placed view. With a view selected on a sheet rather than an element, the Delete key takes the whole placed plan off the sheet. There is an undo toast, but a placed view deserves a confirmation and its own shortcut.
F-024 The levels panel renamed the wrong datum. Editing the last row after adding a level renamed the FOUNDATION datum and moved it to +19.5 ft, which silently relocated every foundation wall. Changing a datum's elevation has no confirmation and no undo entry.
F-030 Zoom-fit is tangled up with activating a view. Double-clicking a view to activate it also re-aimed and re-scaled it to the bounds of every element in the project, and saved that. Partly fixed on 2026-09-05: the load path no longer refits, and the remaining zoom-fit is an explicit gesture.
F-001 A first boot on an empty database volume fails. Running the SQL files straight through psql, which is what the container mount does, hits a down-migration in 009_view_add_timestamps.sql and errors. The migration runner handles it correctly; the container mount does not.

Not built at all

F-029 Missing from the studio. No units setting, so the product is imperial only. No vicinity-map or image insert except through a phone capture. Sheet text, tables, schedules, legends and notes cannot be placed from the toolbar, only through the assistant; the toolbar buttons for notes, polylines, rectangles, room tags, columns, beams, slabs, new views and templates are disabled.
F-011 Copy does not cover everything. Through the assistant, only walls, roofs, detail lines and components can be copied. Columns, beams, rooms, fixtures and annotation cannot.
F-036 AI errors are raw. With a missing or invalid key, every AI surface shows the provider's raw error text instead of one plain "AI is not configured" message with the buttons disabled.

Two numbers we are not going to make up. The run log records export timings — about a second per vector sheet, nine to eleven minutes for the 33-sheet raster set — but it does not record the wall-clock time for the whole run. So there is no honest end-to-end figure to give, and we are not going to invent one.

There is no AI cost figure either. No Anthropic key was available in that environment, so the model's reply was stubbed and nothing was billed. A number invented here would undo the point of the page.

Every finding above is quoted from the findings log written during the run. That log is an internal engineering record and is not published here, but nothing in it that bears on these drawings has been left out above. If you open these drawings and find something the log missed, tell us and it goes in the log.

Questions this page raises

Straight answers.

Can I submit a set like this to my building department?

That is a local question, and confirming it is your job. Many US jurisdictions accept plans prepared by the property owner or the contractor for certain residential work, and many do not for certain scopes. Ask your building department what it accepts for your project's scope, from someone in your role, before you draw anything. Where the jurisdiction requires a licensed design professional, you need one.

What TraceBIM does is record what you attested to when you exported the set, and print an issuance number on every sheet. That is a record, not an approval.

Does TraceBIM check the drawings against the building code?

No. There is no code checking in the product. The code corpus ships empty, and the sheet on this set titled "project information and code analysis" carries text that the person running the test wrote. Anyone telling you a drafting tool has checked your plans against your jurisdiction's code is selling you something.

Can I open the model in Revit?

You can import it. The download is an exchange package: a versioned JSON model, a pyRevit import script that rebuilds levels, wall types with their compound structure, walls, hosted doors and windows, floors, roofs, columns, beams, rooms and grids, and a README. It is not a .rvt file, there is no plugin, and nothing comes back the other way. If your consultant would rather have IFC, the IFC4 file is on this page too.

Why publish the faults?

Because a drawing set with no published criticism is a brochure. We would rather you download these files, find F-041 in the elevations yourself, and see that it was already written down, dated and fixed. The log is the product's own voice, unedited for marketing.

Draw your own set.

Start a project, mark up a plan, and see what comes out. You approve every change before it lands in the drawing, and every export that is not issued for permit carries the DRAFT stamp until you say otherwise.

Start a project Open the studio

TraceBIM is free for everyone — no subscription, no credit card.