Trigger: 01Change detectedAutomation posts to the ingest endpoint
Process: 02Task createdWritten straight to Postgres
Output: 03Boards updateEvery open browser, inside a second
Process: 04Optimistic editsLocal first, reconciled after
Output: 05TrackableState survives refresh and device
Email that used to need remembering shows up as a task with an owner.
The problem
Work arrived as email. You could not see what anyone else had picked up, automated notifications were something a person had to remember to act on, and nothing recorded whether they ever did.
What I built
Check a box, edit a task or leave a comment and it shows up on every other open browser inside a second. Writes go in locally first and reconcile against the server after, so the interface never waits on the network.
Postgres holds the state, so a board survives a refresh, a new device and a re-login. Row-level security protects the data, which is what makes the browser key safe to ship.
An edge function takes a change from an upstream automation and files it as a task. The product-change notification that used to arrive as an email somebody had to remember now arrives with an owner and a status.
Signup runs off an allowlist instead of open registration, added by a script.
A smoke test runs end to end against the live project, covering auth, row-level security, realtime and persistence. A second check drives a real browser through every route as a signed-in user and adds a task.