Every thread reads this before working. The coordinator appends; entries are dated and never rewritten. Newest at the bottom.
brief/ETS27-site-brief.md and research/claude-wiring.md and do not need redesigning; only their look does.concepts/BRIEF.md; jurors score against the 35-point checklist in concepts/research/00-synthesis.md section 2. Hard grading: 7 is award-shortlist, 9 is site of the day.design/README.md (after Felix Rieseberg's "Made by mechanical means"). Inspiration comes from the owner first; the overnight concepts in concepts/ are reference material, not constraints.concepts/ are final (three-lens panel, refine, head juror, mechanics.md; round one kept in each v1/), scored in judging.json and ranked in concepts/index.html. Top three: the loom 7.5, four numerals 7.3, the pleasure principle 7.3; nothing reached site-of-the-day. They stay reference material for the studio rounds.research/genui-landscape.md section 6 (a small custom contract; A2UI, AG-UI and MCP Apps stay migration targets, not dependencies). Its plumbing is scoped to the site, no more no less: an assistant that speaks only about ETS27 and renders only the site's components, with the router, limits and evals of research/claude-wiring.md section 3. Mastra (TypeScript) is the leading candidate for that plumbing; the choice is made at the build round with a PAL consensus, not now. Appearance still comes first: the r/webdesign inspiration thread the owner shared is scanned into design/inspiration/scan-20261020/; its picks are candidates until he marks what he likes.design/inspiration/bar-stage-drawers.md). Process: nothing is built yet; the owner reviews everything on the table, then the studio makes a couple of samples (a proposed set is in design/inspiration/sharpie-on-paper.md). His open question for that review: how loud the event concept should be on the site.design/inspiration/agent-friendly.md; same scope as the mind (public event data, read-only, rate-limited). The mechanics of the site itself are unchanged. Also on the table since 2026-10-21: inspiration items 10 to 16 (the dot cloud, the bar's three states, the contact row, the name as a grid, one grid under everything the mind composes, the two-sentence newsletter, pills with tissue), all in design/inspiration/.ets27-studio, design/tools/publish-pages.sh, root page design/tools/preview-root.html, noindex). The owner's call: "whatever will let us prototype the fastest". One URL for laptop and phone, nothing to keep alive; the fsit2 mirror (sync-preview.sh) stays as the fallback; the laptop servers are no longer needed for review. The live "ask the mind" proxy is the exception: it holds the Claude key and stays on the Mac until the build round moves it to a Worker. Pages serves clean URLs (a .html link redirects to the same page without the suffix).design/inspiration/teardowns/ (Büro, Clever°Franke, Your Majesty, ED., Burn, Floema, Kōzōwood): one playbook per site with the stack, each liked component as selectors, computed styles, timings and a rebuild recipe, shots of every state and frame bursts of the transitions, each checked by a verifier that corrected it in place (VERIFY.md). Read the playbook before building any of these pieces. Corrections carried into the notes the same day: Büro's bar is a message stack that speaks for the canvas and is born in the centre on load before gliding to the bottom; Floema's tissue is drawn SVG, not a filter; Clever°Franke's discs are colours (282), not cases, and do not drag; Burn's thumbnails are one column at three heights and a landing click dismisses rather than opens; Your Majesty's bar wakes on entering the oval, on focus or on scrolling up. Method note: fsit2 renders these pages in software at 0.15 to 5 s per frame, so bursts give order, not duration; durations in the playbooks come from source and in-page samplers. Teardown gallery: design/tools/teardown_gallery.py.design/inspiration/teardowns/multiversx/, verified in place. The pills are Matter.js 0.18.0 bodies driving DOM spans (restitution 0.7, the engine's default gravity of about 1000 px/s², a GSAP ScrollTrigger starts the drop when the stage's middle reaches the viewport bottom, a MouseConstraint spring does the drag and the throw, a scroll-velocity kick on re-entry); floor contact at 0.8 s and visible motion over by about 5 s at 60 Hz, double speed on a 120 Hz screen because of Matter 0.18's runner. It has no reduced-motion path and its canvas blocks page scrolling from a finger that lands on the stage. For our own drop (the speakers answer): step the engine ourselves at a fixed 1000/60 ms, Pointer Events with touch-action: pan-y, trigger on the answer arriving, settled layout for reduced motion, names kept upright; notes in bar-stage-drawers.md ("Physics on the stage"). All nineteen inspiration rows are now filed and the liked pieces of eight sites have playbooks; nothing is built until the owner's review pass.