A sandbox needs a flywheel — boards are meant to be shared, forked, and reused.
Public play links
From the Share dialog, publish a game to mint a public /play/<shareCode>
link. Anyone with the link can play it or fork it into their own bucket.
Unpublishing clears the link.
Templates
Toggle Save as a template to keep a board in your personal template library — forkable from there. A friend-only leaderboard toggle lets players who fork the board compare progress with their mutual follows (never global).
Discover
The Discover tab (/games/discover) lists 20 curated templates spanning all
seven presets. Filter by preset, then Use this template to fork it into a
game-enabled bucket and open it in the builder. Location-based templates carry an
honor-system note.
Import & export
A game exports to a portable, environment-free JSON envelope — owner and bucket stripped, external references (todo / place / workflow ids) recorded. Importing rebuilds it as a draft for the target bucket, remapping those references to your local ids. The round-trip is lossless, including inline expressions.
Forking a shared or template game is exactly this import path with the references mapped for you.
Location boards: honor-system
Location play (Atlas, location-gated spaces) is honor-system in v1 — you self-report a check-in; there's no GPS gate. The guardrails (plan §17):
- No global leaderboards for honor-system boards — friend-only.
- Self-contained rewards — location XP doesn't bleed into shared currencies or global ranks.
- An optional two-checkin pattern (a
reviewspace) for creators who want stronger validation.
The share dialog flags a board's trust model so anyone forking a location preset knows what they're getting.
Security model
Every state-changing move goes through the server (never the client); shared and imported games run workflows only under your own access; and inline expressions run in a sandbox with no JavaScript, no IO, and a finite recursion bound. The event log is the source of truth for any dispute.