BUILD LOG 003 · 5 OCTOBER 2026 · NISSAN DOOKERAN

Issue 1: the idea, and what exists so far.

What BattleBlocks AI is meant to be, what has been built and checked so far, and what you will hear from us next.

BattleBlocks AI is a two-player falling-block duel we are building in public. One player builds. The other chooses what falls. This is the first issue, so here is the idea and where it stands.

The idea

As the Builder, you stack pieces: climb to a target height, recover below it, then hold your stack in the safe zone. As the Chooser, you pick each piece from a small hand of six, and try to make the Builder's job awkward. Round two swaps the roles.

What exists today

• A Rust rules foundation with checked motion and geometry, replay slices and a bounded objective scheduler. The objective work passed 30 selected cases across native Rust, Node-hosted WASM and Chromium in CI. Read it in the first devlog entry.
• A small Builder-only sandbox, with scripted pieces, that has run inside an Android emulator. It is not a phone test and not the game. See the emulator post.
• Three short concept animations on the watch page. They are concept, not footage.

Evidence snapshot: objective implementation source d67451f; verified runtime checkpoint dcc367d; CI run 36980061605; PR #131 merge c18ae660dc496ffd85f58c1da8834cf1f85fd597; Foundation run 37114251673; PR #149 merge 943ea91; PR #159 merge 957a6f8. Nothing here is a build you can try. There is no opponent yet, and no date.

Also: two hackathons

We've entered two hackathons, Solana Mobile's CLOCK IN and Colosseum's Crypto World's Fair, with the same work: a one-phone practice round against a labelled practice bot, with wallet connection through Mobile Wallet Adapter and an optional devnet memo. Today that is plans and code with host tests; none of it has run on a phone, and there is no build to try. We will say here what is checked as it lands, and nothing before.

What you get from this list

One message when there is a build to try, and these build updates until then: what changed, with links to the evidence. Nothing else is sent. Every issue has an unsubscribe link.

Next up

These are plans, not promises.

• We plan to connect the rules and controls into a single-player loop against a local AI. Whether a model can run on the Seeker is still an open question.
• We plan to put the sandbox on a physical Seeker, to learn how the controls feel under thumbs.
• We plan to add the Chooser role after that.

We will write the next issue when one of these has something to show, and not before.

Catch up

Every issue is also a devlog post, so nothing is hidden behind the list. The full history is at the devlog.

You're receiving this because you confirmed your subscription at battleblocks.app. Every issue has an unsubscribe link.