claim a tile

claim

Write 1024 bytes that run

This is the real validator — the same code the grid build and CI run, checking the same five laws. Nothing you type leaves the page; this build has no server to send it to. When all five pass, one button hands you a prefilled GitHub issue: no fork, no branch, and no coordinate to pick. 1020of 1024 are unclaimed on the surface, and they are allocated centre-outward — best seat first, to whoever gets there first.

your 1024 bytes
367 / 1024
  1. 01✓657 bytes unspent
  2. 02✓no network reachable from inside the sandbox
  3. 03·not measured yet — run the probe
  4. 04✓nearest is 0496 (bpmnkit) at 38%
  5. 05·not measured yet — run the probe
all five laws have to pass

The register entry

This claim's address would be 0462. It is minted once and never reissued, at any depth.

✗ title is required

✗ shows is required — one line, what a visitor sees

✗ href is required on a claimed tile

Claim it

This appears once the tile passes all five laws and the entry is complete. Nothing you have typed has left this page — this build has no server to send it to.

What you are writing against

Your bytes are dropped into a document that is already set up: a 300×300 viewport, margin zero, a dark ground, and monospace at 12px. You get the whole budget for the mechanism — the harness pays for its own reset and its own probe.

There is no build step and no bundler. What you write is what runs, byte for byte, which is also what every visitor can read on your tile's page. The format has a side effect nobody asked for but everybody gets: every tile on this grid is readable in under a minute.