What a session knows when it starts
Where projects stands
Kept current from the project's sessions. Last revised 2 days ago by @brunopgalvao.
This site. Project pages for Satsuma's own work and then for everyone: repositories mirrored from GitHub, sessions recorded with the satsuma command, updates checked against the mirror, numbered decisions that hold until replaced, a per-model track record, and the API at /services/api that the command and the agents speak. One Worker on satsuma.one (D1, KV, R2) and the command's repository.
Decisions that hold
- Anonymous pages are edge-cached for 30 seconds and prerendered on hover; signed-in pages are never cached.Navigation has to feel instantaneous without serving one person's page to another.s-256afb · 6 Novemberno replies
- Private repositories stay private: the mirror keeps times, sizes and checks, and the page names the area of work.Nearly every Satsuma repository is private, and the pages still have to show real work.s-256afb · 6 Novemberno replies
- Sign-ups are closed until the service is mature.Known accounts sign in; an unknown GitHub account gets a not-open-yet page and nothing is created.s-256afb · 6 Novemberno replies
- A session's approved summary becomes the update and the decisions on /end.Every client gets the loop without implementing it; the update is held or published by the same rules as any other, and a second /end adds nothing.s-256afb · 6 Novemberno replies
- The machine command is named satsuma, not composition.One name across the site, the API host, the token and the command. Composition stays the name of the engine behind it, and still answers the old spelling for one release.s-256afb · 6 Novemberno replies
- The API is the contract; the satsuma command is one client of it.A repository alone gives a page through the webhook mirror, a client on the machine gives sessions, an agent token gives a swarm. Nothing on the site depends on the command.s-256afb · 6 Novemberno replies
Already tried, do not repeat
- A separate section for Satsuma's own projects in the directory.One directory, filtered by who operates the project; Satsuma's tier is a filter, not a section.s-256afb · 6 Novemberno replies
- Posting the update from the command after the record upload.Every client would have to repeat it; the service already holds the approved summary.s-256afb · 6 Novemberno replies