Specialization kata · BIM-R01

BIM Randori: an unseen requirement change

Start from the edited model; a partner reveals one new requirement card after you begin. Check, fix and recheck without breaking what already passed.

Draft. This recipe is a draft. Its checks may not have been run, and it can change.

Status
Draft
Kata ID
BIM-R01
Maintainer
BIM pathway maintainer
Last verified
Not available. Built and checked by the Dojo maintainers and CI; no independent or professional review yet.
Found a problem?
Report it

The outcome

Meet one requirement you did not see in advance, with evidence, without breaking the requirements that already pass.

For: Learners who finished BIM-004, working with a partner or Sensei.

Done when

  • The drawn card's specification passes on your copy, or you show it already passed and why
  • All six practice requirements still pass
  • Schema and geometry are rechecked and reported separately

You make: Ids report, Edited model. Outcome: Revise and revalidate model.

Showcase and provenance

The Dojo’s worked example, made by the maintainers rather than by a learner: buildingSMART’s wall-with-opening-and-window sample, a practice IDS, an edited copy and every check result, computed by the site’s CI.

See the showcase

Made by
buildingSMART International (sample model); Developer Dojo maintainers (IDS, edit and checks)
Source
buildingSMART Certification-datasets, pinned commit 80d976a9b193a26a8e928c3e79bff67af1de68a8; checks from /examples/bim-pathway/tools/bim_pathway.py
Licence
Sample model CC BY 4.0 (buildingSMART International); IDS files, script and outputs MIT
Date

Brief, inputs and constraints

Inputs

  • wall-with-opening-and-window.edited.ifc. Source: /examples/bim-pathway/generated/wall-with-opening-and-window.edited.ifc. Terms: CC BY 4.0 adaptation of buildingSMART International's sample.
  • randori-cards.ids. Source: /examples/bim-pathway/randori-cards.ids (the partner keeps it; the learner sees only the drawn card). Terms: Dojo content, MIT licence.

Constraints

  • Licensed sample only
  • No paid tools
  • Offline capable

Capabilities practised

  • Validate information
  • Edit model

Stack, permissions and cost

Stack components with version, permissions and cost
PartComponentVersionPermissionsCost
ToolIfcOpenShell and IfcTester0.9.0.post1 and 0.9.0Read and write your own copy onlyFree (LGPL-3.0-or-later)
DataThe edited sample from BIM-004 and the Randori cards2026-11-21Practice copiesFree

Stack recipes

  • Ifcopenshell and python

Why this stack

Same stack as BIM-001 to BIM-004, so the only new thing is the requirement.

Alternatives

  • Draw a stack card instead of a requirement card. The partner can say: no Python, use another open IDS checker. That tests whether your evidence holds when the tool changes. Not tried for this pathway. Not tested for this recipe.

Agents and review gates

  1. Partner or Sensei

    Draws one card after the learner starts and keeps the others hidden.

    Review gate: Asks for the before and after report for the card and the six practice requirements.

  2. Learner

    Reads the card, predicts the result, checks, changes only what is needed and rechecks.

    Depends on: Partner or Sensei

    Review gate: The prediction is written down before the check runs.

Setup and smoke test

  1. Use the environment from BIM-004.
  2. The partner downloads randori-cards.ids and keeps it; the learner downloads only the edited model.

Sign-in and access: None.

Smoke test

Do
Check the edited copy against all three cards
Expect
Card A fails (window FireRating is an empty label); cards B and C pass
Result
Passed /examples/bim-pathway/generated/randori/ids.json, recomputed by CI on every pipeline

Prompts

Copy a prompt into the assistant you use. Replace anything that does not fit your situation, and never paste private or personal data you are not allowed to share.

Predict before you check

Make the learner commit to a reading of the model before the tool answers.

You can also select and copy the text.

Practice exercise

Information Delivery Specification (IDS). From Information Delivery Specification (IDS) (buildingSMART International).

Terms: buildingSMART publishes the standard openly; read the repository's own licence before you reuse its files.

Execution and handoffs

  1. Partner or Sensei: Waits until the learner has started, then reveals one card. Hand-off: The learner writes a prediction.
  2. Learner: Checks the card, makes the smallest change if it fails, and reruns the card and the six practice requirements.
  3. Partner or Sensei: Reviews the before and after reports.

Tests, failures and corrections

Checks with expected and recorded results
CheckExpectedResultEvidence
Check the three cards against the edited copy with the pathway scriptCARD-A fails on the window (#102), CARD-B passes, CARD-C passes (0.24 W/(m2 K) is at most 0.30)Passed on /examples/bim-pathway/generated/randori/ids.json
A learner meets a drawn card and keeps the six practice requirements passingBefore and after reports, with the prediction written firstNot runNot run, so there is no evidence. This is not a pass.

Failures and corrections

  • Observed: Card C compared with the wrong unit Correction: IDS values are in SI units. The sample declares no thermal transmittance unit, so its value is already in W/(m2 K).

Adapt it

  • The partner draws two cards Fix one at a time and rerun everything after each, so you know which change fixed what.

Unseen Randori

Meet one requirement card you have not seen, revealed after you start, on the edited sample.

Constraints

  • Write your prediction before you check
  • Change only what the card needs
  • Keep all six practice requirements passing
  • Report information, schema and geometry separately

How it is judged: The card passes or is shown to pass, the six practice requirements still pass, and the partner agrees the evidence comes from the model.

More Randori challenges

Belt evidence

Belt stages are proposed practice stages, not issued credentials. Evidence below is what a reviewer would look for; it is not a record that anyone has shown it.

Evidence a reviewer looks for

  • For the card drawn, an IDS report before and after the learner's change, and all six practice requirements still passing (Automated check, against Information Delivery Specification (IDS))
  • A Sensei or partner checks that the learner proved the card from the model instead of assuming it (Sensei review)

Belt criteria

  • Practice: Handles card B or C by proving from the model that it already passes
  • Adapt: Handles card A with a scoped edit and keeps the six practice requirements passing
  • Demonstrate: Writes a fourth card for a partner and predicts its result before running it

See the belt stages · Prepare a practice review

Connections

Used by
No other kata names this one as a foundation yet.
Professional review
Required. Any real use of this outcome needs independent validation and any approval required from a qualified professional. Practice here does not grant a licence.

Standards in scope

  • Industry Foundation Classes (IFC), IFC4 ADD2 TC1 (ISO 16739-1:2018), as declared by the sample file. Applies to: The buildingSMART practice sample and copies of it only. Review scope: What the listed checks test: the schema the file declares, its entities and relationships, and the IDS requirements. No claim about any real building.
  • Information Delivery Specification (IDS), 1.0. Applies to: The practice requirements and Randori cards written for this pathway. Review scope: Whether each requirement in the IDS file holds for each applicable element. The requirements are invented for practice; meeting them says nothing about a real project's requirements.

Sources

  • buildingSMART International

    Information Delivery Specification (IDS) (opens the publisher's site in a new tab)

    • Free
    • Docs
    • Intermediate

    buildingSMART's computer-readable XML standard for stating which information an IFC model must contain: the repository holds the schema (version 1.0 is published at standards.buildingsmart.org/IDS/1.0/ids.xsd), the user manual and the implementers' documentation. An IDS check covers information requirements only; it is not a geometry check, a design review or an approval.

  • IfcOpenShell

    IfcTester (opens the publisher's site in a new tab)

    • Free
    • Docs
    • Intermediate

    Documentation for IfcTester, IfcOpenShell's library and command-line tool that reads IDS files and checks IFC models against them, with console, JSON, HTML, ODS and BCF reports. LGPL-3.0-or-later.

Maintenance and caveats

Review cadence: Every six months, when IfcOpenShell or IfcTester releases a new minor version, or when buildingSMART revises IFC or IDS

  • This recipe is a draft: the example was built and checked by the Dojo maintainers and CI, and no learner has run it yet.
  • The sample is a three-element test file, not a building. Nothing learned from it is evidence about a real project.
  • No model, property value or check result here is professionally reviewed or approved. A real project needs the qualified people its contract and jurisdiction name.
  • Information (IDS), schema and geometry checks are separate outcomes. Passing one says nothing about the others, and there is no combined score.
  • The cards are invented practice requirements, not a client brief.

All kata recipes · Back to katas