How Sahul works

Everything on this page is true of the app today. Things that are designed but not built say so, in those words.

Your account, and why syncing is gated

There are no passwords. You sign in with an emailed link, or with Discord or Google when those are switched on. One way to sign in lets you browse and keep a collection in this browser. Two ways unlock syncing — because a synced collection that one lost sign-in method would strand is worse than a local one. Your profile shows which side of that line you are on, and says so rather than leaving you to infer it.

Your collection

Tick models you own, and how many are built and painted. It lives in your browser; with a secured account it also follows you between devices. Syncing never loses a miniature: when two devices disagree, the higher count wins on each model — the worst case is deleting something twice, never losing something you own. Photos you attach stay in your browser and never reach us.

The inbox

Where the app talks to you: security alerts now (every new sign-in files one), event notices and requests as those features light up. Security items never auto-file themselves away; everything else tidies itself after 90 days read. Archiving removes a notification from the list —nothing in the inbox is ever deleted.

Reporting something

Any signed-in person can report a game system or (once galleries ship) a photo. Two speeds, deliberately: content that should not be anywhere is hidden first and reviewed after; a“that is a photo of me” request goes to the gallery owner, who has7 days before it hides automatically — silence is not a defence, and you do not need an account to ask. Every report ends in a decision, and you are told the outcome in your inbox.

Clubs and events

Communities exist: create one and you own it; Members and Organisers groups are set up for you, renameable, with permissions you control. Events exist and do not need a club — an independent event is first-class, and clubs connect to events as host, co-host, participating or listed. Your presence at an event is a five-step ladder — watching, interested, going, registered, checked in — and “did not go” deliberately does not exist. Checked-in is a fact recorded at the event, not something you set on yourself.The pages for browsing all of this are still being built — the machinery works over the API today.

Logging games

A logged game is stamped with the system, its name and version as they were that day — renames and retirements never rewrite what you played. A quiet game gets warnings from 90 days and is marked abandoned at 120, with no result — resume it any time, which resets everything. Editing a submitted result follows the game system's own rule; for Infinity that is both-players-agree. At an event, an organiser can end a game and enter the result — and the record shows it was adjudicated, and by whom.The screens are being built; the rules above already run.

Game systems — including your own

Eight systems ship in the library. You can add your own — Chess, a house system, anything — through the API today (a form is coming): it needs a name and a kind, nothing else, and it checks for close matches so near-duplicates are offered before a new one is created. Caps of 10 a day and 20 total per person; ask and the limit can be raised. Systems are never deleted, only retired — games played under them keep working forever.

Your own tools and agents

Create API tokens on your profile, scoped to what they may do. Everything a token does is recorded as done by that token — “did I do this, or did something do it for me?”always has an answer. Two things are never available to any token: deleting your account, and changing how you sign in. Those need you, signed in yourself. Details for developers are on thedevelopers page.

Being built

Photo galleries and uploads · the pages for clubs, events and game logging · force builder versioning · the MCP connector · collection migration across catalogue editions. Each arrives on this page when it is true, not before.