A single page that lists open, parentless work across organizations Wizard can reach on your behalf — Goals, Problems, Bugs, HR cards, and other issue types — in the team's shared priority order.
Open it at: https://wizard.holdex.io/notifications
[!NOTE] This board is still early. Rows and shared order are live; signal dots and thread details under each item are placeholders until real notifications land.
The board uses GitHub App authorization (not the same login as invoices or calendar).
/notifications.Use Sign out on the page to clear the App session.
Each row is an open parentless issue: nothing linked above it in GitHub's parent–child hierarchy. A quiet Goal with no activity still appears; it is on the board because the work is open, not because something is unread.
For each item the board shows:
Expanding a row currently shows placeholder thread content. That will be replaced by real attention signals later.
Use Coverage to see which organizations (and repositories) Wizard can look at for you. Compare that to what you use day to day — if something is missing, the board is not looking there (install or access gap), not necessarily that the work does not exist.
Refresh re-queries GitHub Search for every covered org and updates the cached item list. Day to day, the page also refreshes covered orgs in the background; Refresh is for when you want a full pass now.
The subtitle under Items shows when the item list was last fetched, and — when someone has set the shared order — when that order last changed and by whom.
There is one cross-organization ranked order for the whole team. Ranked items appear first, in that order. Everything else is unranked (newest updated first), under an unranked separator when both sides are present.
Nothing on the board reorders rows by urgency, assignee, or how late an ETA is. Position is importance; marks on a row are separate (and mostly still to come).
Managers (isManager: true in Holdex team-members config) see reorder controls
on each row:
| Control | Effect |
|---|---|
| Send to top | First among ranked items |
| Send to bottom | Last among ranked items |
| Set position | Place at a chosen 1-based slot in the ranked list |
| De-rank | Remove from the shared order (item joins unranked while it stays open) |
Promoting an unranked item with top / bottom / set position inserts it into the ranked list at that place. Non-managers see the same sorted list but cannot change the order.
Closing an issue removes it from the open Search results, so it leaves your board list. Its place in the shared order is kept until a manager de-ranks it (so a reopen can return to the same slot). Those ids are not listed separately on the board yet — if you need to clear a closed item from the order, reopening it (or using a later cleanup) and de-ranking may be required until a dedicated management surface exists.
The product intent and fuller behaviour are described in the Goal Spec
contextual GitHub notifications
(in the monorepo at docs/specs/contextual-github-notifications-presence-based.md).