ForgeFX Simulations
Internal Working Review · 29 October 2026

Siemens Lab:
Interactive Is Not Yet Accurate.

The Island demo proves we can build an interactive lab quickly. It doesn’t yet prove we can teach Siemens’ actual work.

The biggest gaps are measurement, controls, and assessment—not more scenery.

The Top Ten Gaps

Ranked in the original review by training consequence. High confidence in the inspected-source findings; exact-build runtime verification remains separate.

01

We Show The Measurement Instead Of Teaching It

The panel automatically reports sash opening; there is no learner-positioned measuring tool. Andrew’s first priority was measuring between chosen locations, accurately to a quarter inch.

Why it matters: Reading an answer is not practicing a measurement.

Correction: Add selectable endpoints and a readable measurement tool.

Call 36:35–37:58 and 50:52–53:34 · IslandSiemensLabPanel.cpp:208–214 · Omitted · High confidence
02

Students Can’t Make The Mistake We Need To Assess

Andrew wants learners to select wrong locations, obtain wrong measurements, and submit them. No measurement submission or evaluation was found.

Why it matters: Clicking a highlighted correct spot hides whether the learner understands the task.

Correction: Preserve incorrect choices and assess the entered result.

Call 38:22–39:00 · Inspected Siemens panel and interaction inventory · Omitted · High confidence
03

The Siemens Controls Are Missing

Airflow responds to internal sash and fault inputs. No BACnet connection or point mapping was found. Andrew described responding to BACnet commands; the outline supplies the point list.

Why it matters: Local simulation is not proof of controller integration.

Correction: Demonstrate one verified controller-to-simulation round trip before claiming integration.

Call 24:42–25:09 · Outline §7 · IslandSiemensAirflow.h:61–82 · Omitted · High confidence
04

The Damper Response Is A Shortcut

The model eases airflow toward a target, without an explicit damper-position state. Siemens’ requested chain is sash movement → changed face area → damper movement → increased airflow.

Why it matters: A plausible outcome can conceal the mechanism students need to understand.

Correction: Model and expose that causal chain with Siemens-reviewed behavior.

Call 44:10–44:29 · IslandSiemensAirflow.cpp:75–90 · Partial implementation · High confidence
05

The Airflow Has Not Earned Its Authority

The model explicitly calls its parameters illustrative. Smoke follows a hand-built flow field. That is useful prototyping—not verified operating behavior.

Why it matters: Convincing motion can teach the wrong physical relationship.

Correction: Validate normal, transition, obstruction, and fault cases with the experts. Retain the illustrative label until validated; full CFD is not automatically required.

Call 33:49–35:18 · plans/siemens-lab/airflow-model.md:3–4, 61–63 · Validation gap · High confidence
06

One Sash Stands In For Three Problems

The implementation has one sash value and vertical movement only. Siemens needs vertical, horizontal, and combination configurations, with different openings to measure.

Why it matters: One mechanism cannot demonstrate the full measurement scope.

Correction: Add the three mechanisms, or clearly label the first demo vertical-only.

Call 31:40–33:05 · Outline §4 · IslandSiemensLab.cpp:574–580 · Omitted · High confidence
07

The Bypass Is Not A Measurable Task

Open face area is calculated and minimum-flow constants exist, but no separate fixed/bypass measurement workflow was found. Andrew described uncovering and measuring the bypass, replacing the cover, then measuring fixed area.

Why it matters: These are distinct inputs, not interchangeable labels.

Correction: Add accessible, separate measurable surfaces and the corresponding workflow.

Call 37:42–37:52 · Outline §4 · IslandSiemensAirflow.cpp:13–16, 33–35 · Omitted · High confidence
08

The Cabinet Exists; Useful Disassembly Doesn’t

Fascia and baffle geometry are static. Andrew wants selected covers removed to reveal relevant components—not every screw modeled.

Why it matters: A complete exterior still hides the teaching subject.

Correction: Make the necessary access pieces removable. Do not add adjustable hot/cold-air baffle calibration; Andrew excluded it.

Call 39:25–40:32 · IslandSiemensLabBuild.cpp:704–727 · Omitted · High confidence
09

One Fault Is Standing In For A Syllabus

The exhaust-fault switch reduces capacity. The outline also includes sash-sensor failure, SOAM failure, emergency purge, ODP indications, and remote diagnostics.

Why it matters: Showing an alarm does not establish authentic troubleshooting.

Correction: Select one authentic fault with Rachel and Andrew and implement its observable behavior. Do not invent the still-pending test scripts.

Outline §7 · IslandSiemensAirflow.cpp:19–25 · Broader-scope omission · High confidence
10

Development Speed Is Clearer Than The Teaching Workflow

A narrated tour and free exploration are useful, but do not establish a student-ready lab. Siemens described short exercises alternating with instruction. Rachel warned against conflating fast AI prototypes with the final simulator.

Why it matters: A successful presentation is not yet a successful learning exercise.

Correction: After the physics proof, demonstrate an instructor example followed by an independent student attempt.

Call 7:34–8:18 · Rachel’s post-call guidance · Presenter controls in IslandSiemensLabPanel.cpp:252–281 · Workflow gap · High confidence

What Survives The Roast

The sash, live airflow response, smoke, fault/recovery, and reset are genuine interactive foundations—not just a movie. Keep them.

Original recommendation: Measure → enter dimensions → connect controls → move sash → observe response → diagnose one fault, with Rachel directing the teaching sequence.

Updated immediate priority: First prove the airflow physics against agreed reference cases. Then build the measurement and instructional workflows on that foundation.

Evidence & Boundaries

Implementation review: Forge Island source at f170547d10f32260c2c51266d40a921a8f773527. Source references are relative to apps/forgeisland/unreal/ForgeIsland/Source/ForgeIsland unless noted. This was a read-only source audit—not a fresh playtest or visual inspection of the exact .28.23 teaser build. No proof of a source-to-binary match was established for that clip.

Siemens_forgebot history was inaccessible because ForgeBot was not a member. The accessible proposals channel, original outline, and client call support this report. Broader requirements are not all mandatory for the first pilot; the ten gaps are not ten approved commitments.