Most Certainly Try Labs

Las Jaras BIM project | In progress

House Map Using Revit

A 30-day capture project to turn Las Jaras into a useful Revit model: site, rooms, lighting, smart-home devices, safety notes, furniture anchors, and schedules that can guide real household decisions.

Red Room Test Case Weekend Lighting Sprint Build Notes Exterior Readiness Source Notes

Project facts

4priority rooms for the weekend lighting pass
75 x 137working parcel dimensions in feet
1,800public-record living sqft target to reconcile
3capture levels: architecture, systems, inventory context

What Revit Gets

Anything that changes decisions.

  • Walls, doors, windows, ceiling heights, floors, closets, built-ins, cabinets, porches, deck, and storage structures.
  • Outlets, switches, fixtures, fans, vents, appliances, plumbing fixtures, TVs, smart bulbs, and smart-home devices.
  • Major furniture placeholders with IDs: Gramercy beds, Reese sectional, Elowen chairs, dining table, TVs, apothecary drawers, and storage anchors.

What Stays In Inventory

Small objects do not need BIM drama.

  • Dishware, pantry items, most tabletop decor, and small household goods stay in inventory records unless they affect placement, safety, provenance, insurance, or guest experience.
  • Furniture can be simple blocks with exact dimensions before anyone wastes time modeling curves, carvings, or upholstery texture.

First Test Case

Red Room Revit Capability Test.

Before scaling to the whole house, this project will test Codex/Revit help on the Red Room because it already has measured dimensions, a wall map, door/window/closet notes, saved layout coordinates, object IDs, and furniture anchors.

  • Known room: 136 in x 115 in, with Wall 1 as door/closet, Wall 2 as bed, Wall 3 as window, and Wall 4 as TV/apothecary drawers.
  • Known objects: Gramercy bed, headboard, footboard, TV, apothecary drawers, vintage chair placeholder, side tables, side lamp, ceiling fan, and outlet markers.
  • Test command: Las Jaras > Model > Create Red Room Test

What This Proves

Advice is not enough. We need Revit output.

  • Can Codex translate house notes into Revit-ready room data and a manual modeling checklist?
  • Can Codex generate a pyRevit command that attempts to create walls and named placeholder objects?
  • If the command fails, are the errors actionable?
  • If it succeeds, can the model export JSON for Codex to inspect and improve?

Test Files

Where the Red Room test lives.

  • revit-automation/tests/red-room-field-capture-sheet.md
  • revit-automation/tests/red-room-revit-capability-test.md
  • revit-automation/tests/red-room-revit-test-data.json
  • revit-automation/pyrevit/LasJaras.extension/Las Jaras.tab/Model.panel/Create Red Room Test.pushbutton/script.py
  • revit-automation/pyrevit/LasJaras.extension/Las Jaras.tab/Model.panel/Export Room Data.pushbutton/script.py

Known Gaps

The test is intentionally rough.

Door/window/closet openings may start as notes or placeholders rather than fully cut Revit families. Ceiling height, closet depth, outlet heights, switch placement, bulb bases, fixture labels, TV mounting height, and curtain hardware dimensions still need field capture.

Tooling Decision

Borrow Bibim's pattern, not the whole tool.

Bibim is a useful reference because its Revit add-in plans, generates, validates, and executes code inside Revit. For Las Jaras, the better first move is a narrower helper that understands our rooms, source stack, capture checklists, and repeatable model tasks.

  • Now: pyRevit commands plus structured JSON for Red Room, lighting, room capture, exports, and area reconciliation.
  • Later: a small C# add-in only if we need live context, compiled validation, dry-run previews, undo support, or a persistent task library.
  • Trigger: build the Las Jaras Revit Helper only after the Red Room test proves the bridge is worth scaling.

Why Not Clone It

The house needs a tool with opinions.

A broad AI coding add-in would be impressive, and also a fine way to avoid measuring the hallway. The useful custom work is smaller: capture forms, model validators, scheduled exports, source reconciliation, and repeatable placement commands tied to Las Jaras.

Adjusted Schedule

Lighting moves up. Exterior gets verified before it becomes geometry.

Day 1

Set up Revit standards, room names, shared parameters, pyRevit export path, and the first empty structured model.

Day 2

Weekend lighting/electrical/smart-home sprint for Kitchen, Living Room, Red Room, and Hallways.

Day 3

Review the existing garden site plan as a Revit site reference and list what still needs field measurement.

Days 4-6

Measure the exterior shell: wall lengths, setbacks, porches, deck, storage, openings, utilities, and roofline photos.

Days 7-19

Build the interior architectural shell, kitchen/bath/laundry, bedrooms, closets, living/dining, garage, and storage zones.

Days 20-30

Clean up remaining electrical rooms, add finishes, safety, sheets, schedules, QA corrections, exports, and next actions.

Weekend Capture

Kitchen, Living Room, Red Room, Hallways.

  • Photograph every outlet, switch, ceiling fixture, lamp, TV, cord path, and smart-home device.
  • Record outlet type: 2-prong, 3-prong, GFCI, switched, power strip, or unknown.
  • Record what each switch controls and where guest path lighting feels weak.
  • Capture bulb bases, fixture labels, dimmers, fan controls, and compatibility risks.
Lighting Electrical Hue Smart Home

Exterior Status

The site plan is a base, not a survey.

The Labs garden site plan gives a schematic parcel, sun zones, water assumptions, and public-record structure pieces. That is enough to create a marked-up Revit reference layer.

It is not enough for final house geometry. The house, addition, deck, porch, storage, setback, roof, door, and window locations still need measured field capture.

Automation Path

Revit stays local and controlled.

The automation path starts with read-only model exports through pyRevit, then adds Dynamo or batch scripts only after the basic model and capture schedule are trustworthy.

First target: export levels, rooms, sheets, views, and schedules as JSON so Codex can inspect the model before suggesting changes.