- Building
Fortune Booth Build Log
Team EveryoneKnows · Stanford vs. Berkeley Big Hack Game
Build week: November 15–19, 2026 · Demo Day: November 20, San FranciscoFortune Booth helps people start conversations at events. A guest scans one QR code and draws a fortune inspired by the bamboo fortune cup at a temple. The slip pairs a classical verse from the Zhuge Shenshu (《诸葛神数》) with an English translation and a Today’s Pick drawn from the event. At Demo Day, that might mean watching a demo from the other school and asking the team one question.
Guests can draw without an account, hang their slip on a shared tree, or open the event guide. Organizers can publish event content, manage check-ins and shared cards, and see which parts of the experience people use. Live site · Demo Day tree · Demo Day guide
Build week
November 15 · From a daily bot to an event booth
We started with a daily fortune bot paired with campus recommendations. That idea depended on building an audience before recommendations could reach anyone. An event already gathers people in one place, so we built for organizers and gave guests a single QR code to scan on arrival. The first version had a guest draw page, a venue screen, and a staff redemption page.
November 16 · The classical deck and the first AI guide
We replaced placeholder verses with a 100-slip library from the Zhuge Shenshu and added the first AI event guide. We also built a Discord fortune bot. It eventually moved into its own package as a standalone daily draw.
November 17 · A mobile flow and a directory big enough to search
CES 2026 showed us why an event guide needed more than a shortlist. Someone who already knew a company name or booth number needed a way to find it quickly. We built a searchable directory with 5,214 published records, including 38 curated picks, across 18 venues. We added event entry QR codes and confirmed booth check-ins, then tested the guest flow at phone size.
We also added sharing and the first organizer tools, moved the readings to traditional text with English translations, and began giving each AI task its own HarnessRouter instructions. Yufei explored folded paper, slip shadows, and water divination before the team chose the fortune tree. Hanging a slip gave the ritual a social purpose.
November 18 · The fortune tree meets real event data
The tree prototype evolved into v49, with hand-painted scenery, bronze-coin controls, drifting clouds, and a deer and crane that respond to phone tilt. Guests can open a hanging slip to see the details its owner chose to share, including an optional LinkedIn link. A full tree opens up more space through Shuffle for more.
The live draw pool settled at 87 slips, with 18 prepared for the opening animation. Demo Day and both CES events adopted the shared v49 flow and kept their own content and visitor records. Press Club had its own live tree. We added a homepage directory and refined Today’s Pick for Demo Day.
We also separated Check in from Hang it. A guest can share a name or photo privately with the organizer. Hanging the slip is a separate action, and the guest chooses what appears on the tree. Organizers gained event editing, preview and publication, and the ability to remove individual shared cards.
November 19 · Recommendations, access, and release
An early guide could return nothing for “health startup” even when the catalog held related entries. We removed the time-left input, improved matching, and surfaced up to five relevant options from the published program. The personal plan contains the items a guest saves. The recap uses marked activities to produce one takeaway and one next step.
We gave each event its own organizer passcode, finished the English organizer dashboard and event editor, and released the depth-of-field update. The guide and back office use English, and the fortune slips stay bilingual. We also prepared the demo video.
We tried generating a new slip every time the page opened. We reverted that experiment so a returning guest can find their original slip in the same browser and draw again when they choose.
November 20 · Demo Day
Our on-site walkthrough starts at the entrance QR. Guests draw a slip, try its prompt, and can hang it on the shared tree. We want to see whether the prompt gives someone a reason to approach a person they would otherwise pass by. Open the Demo Day entrance
Where HarnessRouter fits
The site handles the draw, fixed readings, published schedules, and recorded counts. It filters event data before sending eligible options to a model. This lets the model respond to a guest’s interests while keeping recommendations grounded in the event’s actual program.
Harness Job guideAnswers questions from published event facts and ranks a shortlist for personalized recommendations. recapTurns the guest’s marked activities and interests into one takeaway and one specific follow-up. buildTurns organizer materials into an editable event draft. The site validates it before the organizer previews and publishes it. reportUses the site’s recorded aggregates to suggest a next action. The site supplies the totals shown in the dashboard. fortuneSupports readings and single-stop recommendations on legacy fortune cards. The standalone guide uses guide.When a recommendation call fails, the site can still show matches from the filtered catalog. A failed recap can fall back to a short summary from the guest’s selections, with an option to retry.
What we learned about shipping
The early prototype could stall on phones while loading artwork and fonts. We split the art into separate WebP assets, deferred the tree painting until it was needed, and made font loading non-blocking. We also baked the cloud blur into the artwork to keep the slip readable without running a live blur effect on the phone.
A release test passed in the full checkout but depended on a design file absent from the production package. We changed it to check the files visitors actually receive. The Mac mini runs the Node.js site under
launchdwith persistent SQLite storage. The release process tests the package, checks database compatibility on a copy, backs up SQLite, and checks site health after restart. It can restore the prior release if startup fails. We verified public routes and assets after deployment and exercised the draw, private photo check-in, and public hanging flow in a phone-sized browser.November 19 snapshot: 249 commits on
main· 39 merged pull requests · 210 passing release tests · 4 live event pages · 5 configured HarnessRouter roles.
Loading