What if arranging a workshop visit began with a place you could explore?
01 / THE USEFUL OUTCOME
RECOMMISSION Motor Works is a fictional Bristol workshop where a solo owner handles enquiries while working, with capacity for one owner-led inspection at a time.
The Contra × Lovable brief asks for a believable appointment business that improves either the front door or the follow-through. This concept fixes the front door for customers who often cannot name the fault: a £85, 60-minute inspection begins the brief, parts are optional and fitting is quoted separately.
The schedule offers the next four weekdays at 09:00, 11:00 and 14:00 Europe/London. These designed inspection slots leave gaps for preparation and workshop work; the schedule belongs to the fictional business brief.
BEFOREService, vehicle and availability questions repeated across an enquiry.
AFTERA server-confirmed demo appointment and complete preparation sheet, with customer reschedule and cancellation.
Owner time saved and conversion improvement have not been measured with a live workshop.
02 / REFERENCE, NOT REPLICA
We opened Bruno Simon’s portfolio, started the game, drove into physical lettering, opened the map, travelled to Projects and activated a project display. The reference is spatial navigation with real interaction, not simply a car animation behind a page.
Read Bruno’s own case studyThe initial WebGPU attempt stayed blank for approximately 60 seconds in the inspection browser. Hiding navigator.gpu allowed the site’s WebGL fallback to run.
This was a deliberate capability change, not a documented URL mode. We did not measure Bruno’s performance on physical devices or conclude that the default site fails generally.
HENN’s Porsche Pavilion and Autostadt connect circulation, exhibition and a real customer destination. Our interpretation is one compact court with an unmistakable service desk. No architectural model or branding was copied.
RSM Design’s Runway garage uses environmental graphics to distinguish places. Our floor lettering, pavilion names and screen controls use the same vocabulary. Colour supports words and numbers.
Baymard’s friction research and GOV.UK’s review pattern informed one retained draft and targeted corrections. These are usability principles, not proof that a game increases conversion.
Architecture and UX sources were inspected as public articles and guidance. No interviews, paid Mobbin review or fabricated user metrics are claimed. Full research and inspection limits. Bruno’s captured project interaction is retained as attributed reference evidence, not our artwork or a game asset.
03 / THE MOTOR COURT
An open lift and mechanical exhibit make the work understandable. An uncertain customer records intent, their vehicle and concern without booking or buying a part.
See the assemblies, read what is included and explicitly add what you want. Driving past a rack never changes the basket; the selected kits carry into the booking office.
Complete a missing brief if arriving directly, then choose a time, review the details and explicitly reserve. Saved orders live here. All three destinations also have normal screen controls.
Pale cast concrete, graphite lanes, brushed steel and oxblood enamel form a consistent material language. The staggered campus has one road spine, separate station branches, local service gantries and numbered parking bays. Its road-based GPS remains visible when a driver takes over from assistance.
The lift and parts assembly can be operated while parked, then returned to their rest state. These are illustrative exhibits, not diagnosis or verified fitment. The architecture and mechanical exhibits are original code and geometry. The driving Chiron is a licensed artist asset, adapted and attributed separately. It is not manufacturer CAD, a verified one-off replica or an engineering simulation.
WHY THIS DIRECTION
Free exploration in a small service yard. Strong landmarks, a bounded world and immediate booking.
A lift travels through a vertical cutaway workshop. Strong composition, but less meaningful free driving.
Drive across enormous exploded components. Greater modelling and camera risk, with weaker immediate service clarity.
04 / THE SERVICE DESK
The work order stays with you. Your driving skill never becomes a booking requirement.
Diagnosis, planned maintenance or parts-only. No compulsory kit and no guessed fault.
Describe the actual vehicle and an optional concern. The demonstrator does not identify your car.
See the next four weekdays at 09:00, 11:00 and 14:00 London time. Selecting a time does not reserve it.
Edit a specific answer without returning across the map. The server creates a demo reservation only after explicit confirmation.
The hosted build stores demo reservations in its cloud database and supports customer rescheduling and cancellation from the originating browser session. Confirmations are on-screen and downloadable; there are no automated booking emails, reminders, lead follow-ups, payments or verified catalogue fitment. The hosted booking review covers retry, conflicts, rescheduling, cancellation and mobile parts-only ordering. It uses reduced-motion Chrome and an emulated phone, not a physical-device benchmark.
05 / UNDER THE SURFACE
Car, camera, steering, destination and finish.
Transient; safe to reset.Intent, selected parts, vehicle, time and contact.
Shared by direct and spatial entry.Accepted price, reserved capacity and immutable snapshot.
Owned by the server.A fixed-step planar controller handles steering and swept collisions. The collision radius now encloses the measured visible car. Controller checks and browser interactions support correctness; they do not establish enjoyment for a first-time visitor.
Static architecture and car geometry merge by material, preserving moving wheels and the source triangles. Physical signs redraw when their text changes. Lower draw estimates still need a measured whole-scene rendering budget.
The booking review completed in still mode without loading the car. The experience review also checks touch, keyboard isolation, model failure, context loss and unavailable WebGL. Physical-device reliability remains open.
Implementation is not proof that every interaction has passed validation. Read the engineering research and dated decision ledger for source-level detail and current limits.
06 / PROOF & NEXT STEPS
The booking review completed eight scenario groups and the exact owner handoff passed seven checks, with no page errors and test orders cleaned up. The corrected experience review passed 25 checks and seven automated audits with no violations or overflow. These are headless-browser results, including emulated phone layouts.
Inspect the raw hosted booking and owner-handoff reports, plus the historical Next experience report. The first review’s contrast failures remain recorded. An intermediate timeout was traced to a CSS encoding error causing HTTP 500, then corrected; it was not a model-loading performance result.
The actual moving benchmark completed all six routes on Intel UHD Graphics in historical local Next development. Desktop booking reached 20.8 ms p95, missing the 20 ms target, with a longest moving interval of 69.4 ms. The phone-sized run uses the same computer. These are historical Next measurements. The hosted build has since been measured independently on the same class of graphics: all six routes arrived with moving-frame p95 of 14.1 ms at desktop size and 7.1–7.2 ms on an emulated phone, worst moving interval 28.2 ms. Frame intervals are not GPU execution timing, caches were uncontrolled, and this is not a physical-phone or zero-lag claim.
Verify the official brief. Inspect the reference live. Compare different spatial concepts.
Research documentedFixed-step controls and assisted routes have simulation checks. The browser review also covers driving, input release and recovery.
Controller + browser checksBooking, retry, conflict, customer management and the exact order’s authenticated owner handoff have browser checks.
Customer + owner checksHosted accessibility, booking, owner handoff and moving-route checks are recorded. Physical phones, assistive technology and performance across devices remain open.
Hosted checks completeThe authored court and cloud booking service now run in the hosted Lovable project. Submission remains a separate decision.
Migration completeScores run from 1 to 5 and express our current assessment. Physical-device reliability and observed user/owner value are the weakest important areas. Passing another test cannot stand in for that missing evidence.
The production build and automated tests pass. Physical-phone, assistive-technology and performance across devices remain open, as does observed customer and owner value. Historical and hosted frame measurements are useful evidence; they are not a universal performance pass.
The authored court now runs in Lovable on TanStack Start, React, Three.js and Supabase at recommission-motor-court.lovable.app. Independent checks passed the playable routes, touch controls, accessible fallbacks, complete customer booking and authorised owner preparation; the account holder has also confirmed staff sign-in. All 13 API groups and 35 database checks passed, including overlapping appointments, retries and guest privacy. On Intel UHD Graphics, the hosted moving-frame p95 was 14.1 ms at desktop size and 7.1–7.2 ms in phone-size emulation; these are historical measured frame-scheduling results, not physical-phone, GPU-time or zero-lag claims. Customer management remains tied to the originating browser session. Confirmations are on-screen and downloadable; automated emails, reminders, lead follow-ups, payments and real appointments remain disabled. Owner access requires an explicitly provisioned Cloud account and owner role. The competition entry has not been submitted.
Migration evidence and lovable-*.json reportsFull staged plan and acceptance gates