Fliproom: a room changeover is a content problem

Zackary Loevseth — Mon, 21 Sep 2026 02:10:02 +0000

What I Built

Fliproom turns a room changeover into an ordered, visual checklist. A volunteer selects the current layout and the next one, then sees what stays, what moves, and what goes into storage.

The demonstration is a fictional community hall called The Commons: a 12-by-8-metre room with eight pieces of equipment and three layouts—Workshop, Presentation, and Open floor. The room and its content were created for this application. They do not represent a real venue or customer deployment.

The interface shows numbered furniture on a floor plan, before/after views, and a move list connected to the same equipment. Dependencies keep a step locked until its destination has been cleared. If two items exchange positions, the planner can introduce a temporary parking step. Checkmarks survive a browser reload; changing layouts starts a fresh checklist. A text download lets someone carry the instructions away from the screen.

This is a deliberately small planning aid. It checks rectangular footprints and room bounds, not carrying routes, lifting arrangements, or venue safety. It assumes outside storage is available when in-room parking will not fit. Its time estimates are fixed per equipment operation, not measured results.

Demo

Public application: Try Fliproom

Start with Workshop → Presentation. Compare the floor views, inspect the numbered moves, and complete the prerequisites for a blocked step. Then undo a prerequisite and watch its dependent checkmark clear. Reverse the changeover or select Open floor to produce another plan.

No login is needed. The deployed demo loaded published Sanity content and displayed a ready plan without browser errors. Local checks also inspected the downloaded seven-move checklist and found no horizontal overflow at a 390px viewport.

Code

Repository: Fliproom on GitHub

Source revision: 88ad482

The MIT-licensed application uses Next.js, TypeScript, React, and Sanity. The public planner is hosted on GitHub Pages. It makes no model calls at runtime.

My Build Process

Codex was the development environment. AI agents designed and wrote the implementation, reviewed the code, ran the tests, and drafted this post. My role was account signup/sign-in and approval of the project, fictional content import, source release, and demo publication. The technical work and checks described here were performed by the agents.

The brief was to build a useful application whose behavior depends on structured content. The key decision was to derive moves from layouts rather than author a second set of instructions. An equipment document owns its dimensions; every layout references it. The planner then compares placements and produces instructions from that shared model.

The work was divided among the interface, planning engine, and Sanity integration, with another agent reviewing the results. Three problems made that review worthwhile.

First, a move from 90° back to 0° originally omitted the target orientation in its text. The floor diagram could be correct while the printable instruction was incomplete. Move labels now state the absolute target orientation, and a regression test covers that transition.

Second, subtitles were optional in Studio but required by the read validator. Clearing a subtitle could therefore break an otherwise valid catalog. The GROQ projection now turns an omitted subtitle into empty text. A test evaluates the actual query against the seed documents, rather than checking a separate approximation of the query.

Third, authenticated success concealed a public-access failure. Studio imported 12 documents and reread 12 exact matches, but an anonymous count returned zero. The generated IDs contained dots and landed on private document paths. The generator now uses hyphenated IDs, with a regression test. After reimport, a separate unauthenticated check read all 12 public documents and confirmed that both the raw documents and resolved GROQ catalog exactly matched the reviewed seed. The authenticated receipt and public-read check answered different questions; both were needed.

The local suite passes 21 tests, and typechecking passes. Tests replay all nine sample-layout transitions, check collisions and final positions, and exercise parking, rotation, invalid inputs, dependent undo, and GROQ reference resolution. Production and static-export builds passed. Browser checks with live Sanity content verified that saved progress restored after reload, prerequisites unlocked step 6, and undoing a prerequisite cleared and disabled it. No console errors or warnings were reported in that check.

No full agent session or private conversation context has been exported. The application content and this writeup are confined to this build.

Sanity Project Details

Project: fliproom — i5bjg9lg

Dataset: production, publicly readable. An unauthenticated check verified 12 published documents: one room, eight equipment items, and three layouts.

The content model separates rooms, equipment, and layouts. Placements reference equipment and store coordinates and orientation; layouts reference their room. GROQ resolves those relationships into the planner's input. Tests reject unresolved references and equipment belonging to another room.