Rich notifications: review gates you can answer from a phone #26
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens today
What we want
A gate decided from a phone in a few minutes, because Braid shows what it checked instead of the files.
Try it: https://claude.ai/artifact/W6EpFqxmbDfGzWtgVHcMyp (opens for the owner only; the screens are run 195's own records).
Order of work
A push through the owner's ntfy server, beside emailYours to decide
Where the push goes.An ntfy server of the owner's own was tested on their iPhone on 2026-11-13 and dropped on 2026-11-14: see the comment on the phone test. The push will come from the phone app, #538.Done when
On a real run, from a phone: a push arrives for the proposal and for the merge, each is answered from its page without opening a file, and an agent's question is answered from its notification inside the hour. A look at that change's diff on the phone needs no sideways scroll.
From an audit on 2026-11-13 of the code, production's records and run 195. The audit and the design's detail are in the comments. The diff was added the same day, after the owner's review. ntfy was dropped on 2026-11-14, after a test on a phone.
The original request (2026-09-14)
Currently we have email notifications, although I haven't seen one in a while. Either way, this ticket is to take the next step and implement optional ntfy notifications, assuming they can fulfill the job of asking a user questions in a well-designed way, so the user doesn't need to also open the braid web app to answer to human gates.
Rich notifications that allow user to answer questions from mobileto Rich notifications: review gates you can answer from a phoneThe audit: every gate today
What the records say
git checkout.too_big,budget_stuck,new_project), and a gate's expiry has no code that acts on it.The design in detail
One record per gate. When a gate opens, a script reads the run's worktree and Braid's own records into one record: the summary, the checks, the proof. The page and the notification both read it, so they cannot disagree. Its check results are kept with the answer, so the log says what the person was shown.
The verdict. "Ready" when every check passes. Otherwise "N things to look at", listed first. Braid orders what you read. It does not decide for you.
Proposal review
Change review
Notifications
A review opens a page because a notification holds one picture, three buttons and 4,096 bytes (ntfy's limits, read in its documentation). A button answers with the gate's own reply token, which the API accepts already and nothing sends today. An answered gate's notification is cleared.
To settle in the proposal
The diff: checking that nothing extra came along
Added 2026-11-13, after the owner's review: the design had no place to read the code. The diff is not the main way to decide a gate. It is for the occasional look that confirms a change holds only what was asked for.
What happens today
What we want
websocketsorjsdomscripts/services.sh, from group 9, whose title names itRun 195's 16,116 lines: the app 6,981, its tests 4,680, lockfiles 2,740, the plan 1,266, Braid's own files 449.
The second table becomes one check on the merge gate, Scope. It asks for a look when a change reaches outside, holds a key, runs by itself, skips a test or removes existing code. A package the plan does not mention is listed, and does not ask for a look by itself.
On a phone
On a desktop
The same page in three columns: the map, the file, your notes. A rewritten file can be read side by side. Keys:
jkfor the next and previous file,xfor seen,sfor side by side.Drawing the lines: ours or a library
Tried on four of run 195's patches, at 390 px and at 1280 px.
@pierre/diffs1.6.4@git-diff-view/react0.1.8Recommended: Braid's own rows. The parser, the notes and the wrapping exist, the mock shows the rest is small, and the phone layout stays ours. Adding CSS and HTML to the colouring takes it to 95% of run 195's lines.
@pierre/diffsis the fallback if side by side or colour turns out costly. It goes in behind one component.To settle in the proposal
websockets, which the code explains in a comment. It informs and does not gate.The phone test, and why ntfy is dropped
What was tested (2026-11-13)
Five real notifications on the owner's iPhone, through their own ntfy server, one for each kind of review: a proposal, a merge with a screenshot, an app to try, a diff, and an archive with an answer button. All five arrived and opened their pages. The proposal was approved from its page on the phone.
What an iPhone shows
Decided (owner, 2026-11-14)
ntfy is not pursued. The notification becomes a phone app, #538. The pages are unaffected: the proposal summary (#537), the proof and the diff.
Slice 1 shipped: the proposal summary, #537, in pull request #539. The phone app that will open it is #538.
Closing: everything here has shipped or moved to another issue.