Architecture and BIM · Pathway
From an IFC file to checked information.
Five katas on one small, openly licensed building model. Each step has a real file you can open and a check result that CI computes on every pipeline.
01 / The files
One wall, one opening, one window
The model is buildingSMART’s wall-with-opening-and-window test file: schema IFC4, lengths in millimetre. It is tiny on purpose, so every entity can be read and every check can be followed by hand. It is a test file, not a building.
- The original model (IFC, CC BY 4.0, buildingSMART International), unchanged.
- The practice requirements (IDS 1.0 XML): six requirements written for this pathway.
- The edited copy (IFC, CC BY 4.0 adaptation): the BIM-004 change, rebuilt byte for byte by CI.
- The check summary (Markdown) and every result as JSON under the manifest, with tool versions and file hashes.
- The pathway script (Python, MIT) and its pinned packages, so you can rerun every check yourself.
- README: licences, how to rerun the checks, and what they do not cover.
Mesh is not BIM. The 3D room scan is a surface you can look at; this model is data with types, properties and relationships you can query and check.
02 / What is in the model
3 elements in one storey
| Entity | Class | Name | GlobalId |
|---|---|---|---|
| #45 | IfcWall | Wall for Test Example | 3ZYW59sxj8lei475l7EhLU |
| #80 | IfcOpeningElement | Opening Element for Test Example | 2bJiss68D6hvLKV8O1xmqJ |
| #102 | IfcWindow | Window for Test Example | 0tA4DSHd50le6Ov9Yu0I9X |
The opening #80 voids the wall #45, and the window #102 fills the opening #80. Full inspection (JSON) · property sets (JSON).
03 / The steps
Five katas, in order
Each kata has a brief, prompts, checks and the evidence for the checks the Dojo has run. They are drafts: the Dojo built the example and CI checks it, and no learner has run them yet. Do the foundations first: Compare AI instructions and Spot a context trap. If you have not read an IFC file before, Find the story in a building model walks through the same sample by hand.
- BIM-001 Inspect an IFC model
Schema, units, the spatial tree, every element and how the opening and window relate to the wall.
- BIM-002 Read the property sets
Every property on the wall and window, with its type, and the ones that are empty.
- BIM-003 Check the model against IDS requirements
Run six practice requirements with IfcTester and explain the one that fails.
- BIM-004 Change the model and check it again
One scoped edit, every GlobalId kept, then IDS, schema and geometry checks rerun on the copy.
- BIM-R01 BIM Randori: an unseen requirement change
A partner reveals one new requirement after you start; meet it without breaking the others.
04 / The checks
Three separate outcomes, no combined score
Information, schema and geometry answer different questions. A model can pass one and fail another, so each is reported on its own. These results come from CI: the pipeline reruns /examples/bim-pathway/tools/bim_pathway.py and fails if any output differs from the published files.
Information: IDS requirements
| Requirement | Original | Edited |
|---|---|---|
| REQ-01 Walls say whether they are external | Pass | Pass |
| REQ-02 Walls say whether they are load bearing | Pass | Pass |
| REQ-03 Walls carry a fire rating label in the practice format | Fail | Pass |
| REQ-04 Windows have an overall width and height | Pass | Pass |
| REQ-05 Walls and windows are placed in a building storey | Pass | Pass |
| REQ-06 Windows state their thermal transmittance | Pass | Pass |
Original: 5 passed, 1 failed. Edited: 6 passed, 0 failed. REQ-03 failed on the original because the wall’s FireRating is an empty label; IfcTester reports an empty value as a missing property.
The change (BIM-004)
#45 Pset_WallCommon.FireRating: “” to “REI 60”. 24 of 24 GlobalIds kept, 0 added. “REI 60” is a practice placeholder that meets the practice pattern; it is not a fire rating. Change record (JSON).
Schema
IFC4 schema check with ifcopenshell.validate (EXPRESS rules off): original 0 issues, edited 0 issues. Result (JSON).
Geometry
| Element | Built (original, edited) | Volume m³ | Bounding box |
|---|---|---|---|
| #45 IfcWall | yes, yes | 1.5 | 0, 0, 0 to 3, 0.3, 2 |
| #80 IfcOpeningElement | yes, yes | 0.3 | 1, 0, 0.5 to 2, 0.3, 1.5 |
| #102 IfcWindow | yes, yes | 0.2 | 1, 0.05, 0.5 to 2, 0.25, 1.5 |
The wall is 3 × 0.3 × 2 m less the 1 × 0.3 × 1 m opening: 1.5 m³. Building a shape shows it can be processed; it is not a clash, tolerance or constructability check.
Randori cards
Checked against the edited copy: CARD-A fail, CARD-B pass, CARD-C pass. The cards (IDS) are for the partner; see BIM-R01.
05 / The tools
Open tools, pinned versions
| Tool or standard | Version | Licence | Source |
|---|---|---|---|
| IfcOpenShell | 0.9.0.post1 | LGPL-3.0-or-later | PyPI, validation, geometry |
| IfcTester | 0.9.0 | LGPL-3.0-or-later | PyPI, documentation |
| Python | 3.12 | PSF | CI image python:3.12-slim |
| IDS (buildingSMART) | 1.0 | Open standard | repository, schema |
| IFC (buildingSMART) | IFC4 (as the sample declares) | Open standard | Declared in the file’s FILE_SCHEMA |
The Armory lists IfcOpenShell and IfcTester with their smoke tests, and the stack recipe IfcOpenShell, IfcTester and Python.
06 / What is checked
Verified, and not verified
Verified
- The model is the pinned buildingSMART file, unchanged (SHA-256 73b0e45d931d…, checked by the site’s tests).
- Both IDS files open with XML schema validation on, as IDS 1.0.
- On every pipeline, CI installs the pinned packages by hash, reruns the inspection, property, IDS, schema and geometry checks on the original and the edited copy and the Randori cards, rebuilds the edited file, and fails if any output differs from the files on this page. (evidence)
- The edit changes one property and keeps every GlobalId. (evidence)
Not verified
- Any real building, design value or project requirement. The requirements are invented for practice, and the sample is a test file.
- EXPRESS where-rules and buildingSMART’s own validation service: the schema check ran with EXPRESS rules off.
- Clash detection, tolerances, quantities for cost, or construction sequence.
- Opening the files in a BIM authoring tool or a web IFC viewer, and round trips through other tools.
- Use by real learners: no learner has run these katas yet.
Professional review: None. Nothing here has professional, regulatory or construction approval of any kind, and a real project needs the qualified reviewers its contract and jurisdiction name.
07 / Credits
Credits and terms
- Model: wall-with-opening-and-window.ifc, © buildingSMART International Ltd., from the Certification-datasets repository at a pinned commit, licensed CC BY 4.0. The edited copy is an adaptation: one property changed and the file header rewritten by the Dojo.
- The IDS files, the pathway script and its outputs: Developer Dojo, MIT licence.
- IfcOpenShell and IfcTester: the IfcOpenShell project, LGPL-3.0-or-later.



