Notifications

What needs you

The thing that needs a person is an attempt held at the gate. An attempt parked for a decision by someone other than its author is waiting on you for every account that may decide it, across every space you belong to. Deciding is described under Decisions and the gate.

The account home

The signed-in home is a working surface. Its main column has three tabs: For you, Waiting on you and Ledger. Waiting on you lists the parked attempts you may decide, with a count, from one read across every space; Everything waiting opens the full list at Your work. Ledger shows the latest signed merges from your repositories. The left rail lists your repositories, your harnesses and your agents.

The same fan-in is on the space header as Evidence, with the count of attempts in that space waiting on a decision.

The space's notifications

Notifications live under each space. The page has two views, Unread and Everything; the unread filter is the server's own, so the page and the server cannot disagree about a count. A filter by repository narrows the page on the client. Mark page read carries exactly the ids the page rendered, so a notification that arrived while you were reading is untouched; there is no mark-all.

A notification row today has one kind: a review comment that mentions a team you belong to, written as @space/team. Each row links to the attempt it came from.

GET  /orgs/{space}/notifications?unread=1
POST /orgs/{space}/notifications/{id}/read
POST /orgs/{space}/notifications/mark-read            {"ids": [...]}

The preferences page shows the in-app and email matrix. In-app is the only channel that can be chosen today, so the matrix cannot be changed yet.

Email

Signing in is a round trip through your inbox: the sign-in mail carries a one-time code and a link that completes the sign-in with it, and the sign-in page takes the code pasted from the email. The link always goes to the configured origin, never to the address the request arrived on. Delivery is rate-limited per address and per source, and the response to a sign-in request is the same whether or not the address is known.

Invitations to a space are emailed. See Getting started.

A parked attempt sends notices to the people the park is addressed to: when it is parked, when three quarters of its life has passed without a decision, and when it expires. The notices are derived from a query over parked attempts rather than a timer, so a restart loses nothing and a redeploy sends each notice once; an attempt that is approved, rejected or landed is no longer parked, so its warning is never sent. A notice that cannot be delivered is retried up to five times.