API

GET  /api/state            Authorization: Bearer <HQ_TOKEN>
     → { version, updated, state }
PUT  /api/state  { version, state }
     → { version, updated }   or 409 with the current document

state = {
  tasks:     { id: {id, title, tree, area, status, source, notes,
                    updated, parent, order} },
  notes:     { id: {id, text, tree|null, created} },
  decisions: { id: {id, title, status, summary, options[],
                    decision, updated} },
  focus:     [taskId, taskId, taskId],
  areas:     { tree: [areaName, ...] },    // optional
  seq:       N                             // highest task number ever issued; never lower it
}

Outline. Tasks form a tree per project and area. parent is the id of another task or null/absent for a top-level item. A child always has the same tree and area as its parent; when a parent moves, move its descendants with it, and never create a cycle. order is an integer sort key among siblings (same parent, tree and area); items without one sort after ordered items, by id. Deleting a task re-parents its children to the deleted task's parent. area "" is the General bucket; areas[tree] holds the display order of a project's areas and may list areas with no tasks yet.

Status. next · doing · parked · done. inbox is legacy: read it as next, never write it. Trees: roadmap · platform · firestrike · ground-war · vector-drift · stone-power · slime-raiser · ludus · total-loss · nft · lore · physical · biz · hq. Ids are t-NNN, max+1, never reused. Storage is KV: read-after-write can lag a few seconds on a different edge, so send the version you read.

Repo

Local: C:\Users\Whitc\Documents\CProjects\ACT. Start at CLAUDE.md. Sync with node tools/hq-sync.mjs pull / push (token from HQ_TOKEN or ~/.act-hq-token). The sync round-trips whole task objects, so parent and order survive.

Support inbox. support@actuniverse.com is stored by the act-support Worker, not in the state document: GET /api/support/messages?status=new, GET …/messages/<id>, POST …/messages/<id> {status}, POST …/messages/<id>/reply {text}, same passphrase. From a terminal: node tools/support-mail.mjs list | read <id> | reply <id>.

Questions. /questions is a board where anyone asks anyone, one answer box per question. It is the shared doc questions (/api/doc/questions, same passphrase). From a terminal: node tools/questions.mjs list | add | done <n>. Ask there when the answer can wait; say in chat that you did.

Messages. /messages sends a player a message that the hub's drone brings them as they next come into the hub (t-1105); once read they can open it again for 10 minutes. When Theo tells you to message someone, send it from a terminal: node tools/hub-message.mjs send <name or Account ID> --from "<whoever he says>" --by "<your chat>" "the message", and find or recent to check (/api/hub-messages, same passphrase).

Battle pass. /battlepass tracks each month's pass: what goes in every chest for every game, and each item's steps (art, the catalogue, checked in game; for special skins the NFT picture and the chain registration). It is the shared doc battlepass. From a terminal: node tools/battlepass.mjs list | show <month> | set <month> <n> stage=catalogue. Tick your step there when you finish it.

Generals' 1/1s. /oneofones tracks each general's 1/1 until it's delivered: brief, painted, in game, wallet, airdropped, what they asked for and one click to their references. It is the shared doc oneofones, kept by the GENERALS CHAT from its private file (node tools/oneofones.mjs push <file> | show). Names live only there and in the private tracker, never in this repo.

Rules (short)

• Shared systems are specified once, in platform/. Games depend on platform only.
• Disagreements become decision records, never silent picks.
• Engineering truth is cutty92/act-babylon docs. Read them before touching platform.