Two Sparks, Four Models

In about 120 words, explain how two small desktop computers joined by a single 200 gigabit cable can run an AI model that is too big for either one alone. Plain language, no lists.

Make "Night Bloom": a twenty-second film, rendered live in the browser, of a dark meadow coming alive. It opens on near-black: a few fireflies drift in. Bioluminescent flowers begin to unfurl one by one, glowing from within, their light spilling onto the grass around them. The bloom spreads across the meadow in waves, colours shifting from deep teal through violet to warm gold, until the whole scene is a field of light under a slow aurora. Then it settles and dims back toward the opening, so the film loops without a seam.

Build it as a single HTML file with everything inline: no other files, images, libraries or web fonts, so it runs offline. Canvas 2D or WebGL, your choice. Aim for something people stop scrolling for: depth, soft glow, motion that feels organic, not a screensaver.

Requirements: - It fills the window at any size and aspect; it must look composed both in portrait (1080x1920) and in landscape (1920x1080). - No text, no UI and no controls on screen. - The film is exactly 20 seconds long and loops seamlessly. - Deterministic: the same frame time always draws the same picture (seed any randomness from a fixed number). - Expose one global function, window.renderAt(seconds), that draws the frame for that time (0 to 20) immediately and synchronously, so the film can be recorded frame by frame. The normal animation loop just calls it with the current time. - Keep the file under 30 KB. Write clean, careful code: it runs exactly as you write it, with no chance to fix it afterwards.

Write a bot for the four-player light-cycle game below. Your bot plays against three other bots written by other AI models. The referee runs 200 seeded games; the bot with the most points wins. One shot: you will not see results before your bot is final.

THE GAME - Grid: 64 columns x 64 rows. x grows to the right, y grows downward. Cells outside the grid are walls. - Four players start in four corners (8 cells in from each edge), each facing clockwise along the edge. Seats rotate between games, so every bot plays every corner equally often. - Obstacles: each game has some wall cells placed with four-fold rotational symmetry, so every corner faces the same layout. - Every tick all living players choose a move at the same time: "L" (turn left), "R" (turn right) or "S" (keep straight). Turns are relative to the current heading. Then every living player moves one cell forward and leaves a permanent trail in the cell it left. - A player dies if it moves into a wall, an obstacle, any trail (its own included) or any cell another player occupies or enters this same tick (both die on a head-on or same-cell collision). - Dead players' trails stay on the board. - The game ends when at most one player is alive, or after 4,000 ticks. - Points per game: the last player alive gets 3, the second-last 2, the third-last 1, the first out 0. Players that die on the same tick share the points of the places they cover equally. If the game reaches 4,000 ticks, all living players share the points of the top places equally.

YOUR CODE Reply with one JavaScript code block that defines exactly this function, and nothing the referee must call besides it:

function createBot() { // called once per game; keep any memory you want in this closure return { move(state) { // return "L", "R" or "S" } }; }

state (read-only, a fresh copy every tick): - state.width, state.height: 64, 64 - state.tick: 0 on the first move - state.me: your player index (0-3) - state.players: array of 4 objects { x, y, dir, alive }, dir is 0 = up, 1 = right, 2 = down, 3 = left - state.grid: Uint8Array of width*height cells, index y*width + x: 0 = empty, 1 = wall or obstacle, 2 + i = trail of player i. Current heads are also marked as 2 + i.

RULES FOR THE CODE - Plain JavaScript (ES2020). No require, import, fetch, timers, DOM or global objects beyond Math, JSON, Array, typed arrays, Map, Set and Date.now. Math.random is allowed; the referee seeds it, so games repeat exactly. - At most 50 ms per move on a modern CPU core. A move that takes longer, throws, or returns anything other than "L", "R" or "S" counts as "S". - At most 40 KB of source. One code block, no explanation needed after it.

Design a single-story home of about 2,400 square feet: 3 bedrooms and 2 bathrooms. Everything else is up to you: the style, the layout, the rooms you add, how the house lives.

Deliver it as one HTML file with everything inline (no other files, images, libraries or web fonts), containing:

1. The floor plan as an inline SVG blueprint, drawn to scale: exterior and interior walls with real thickness, doors with their swing arcs, windows, room names with their dimensions, overall dimension strings on the outside, a scale bar, a north arrow and a title block (project name, total area, scale, date). Make it look like a real architect's blueprint. 2. A short design note under the drawing (at most 120 words): the idea of the house and how it lives. 3. A room schedule as machine-readable JSON in `<script type="application/json" id="plan">`, in this shape: {"total_sqft": <number>, "rooms": [{"name": "...", "type": "bedroom|bathroom|kitchen|living|dining|garage|utility|circulation|other", "width_ft": <number>, "depth_ft": <number>}]} Count conditioned living area in total_sqft (not a garage or covered porch, if you add one); it should be within 5% of 2,400. List every room. Exactly 3 rooms of type "bedroom" and 2 of type "bathroom".

The drawing must fit the window at any size. Write it carefully: it is used exactly as you write it.