docs(admin): Team notification emails are engagement rules now #23

wtclaude · 2026-08-31T06:04:14Z

wtclaude commented

2026-08-31 06:04:14 +00:00

The administration/teams.mdx section engagement Phase 6 owes (ENGAGEMENT.md §6.0b). Code: RunicGateway/website#174 · Docs: RunicGateway/docs#187

The fact that has to land first

Team emails used to send with no configuration and now arrive switched off. On an existing site nobody receives them until an operator opens Admin → Engagement → Rules and turns one on. That is the whole reason this page needs a section rather than a sentence: it is the one operator-visible consequence of the migration, and a site that upgrades without reading it experiences it as mail quietly stopping.

The section also covers:

What each of the four seeded rules sends, and why the two roster ones ship off and with an hour-long cooldown — they describe things already on the Team's activity feed, arriving from a fifteen-minute sweep rather than from a person doing something.
A rule decides whether the site sends at all; members still choose per Team. Turning a rule on does not sign anybody up. Worth saying plainly, because "rules" is a new word on this page and it would otherwise read as an operator switch over other people's inboxes.
Why a digest is re-read at the moment it is sent — one digest after an outage rather than a backlog, a hidden post absent from it, and somebody who lost forum access between the post and the send not receiving it. Written as three consequences rather than as a design.
Unsubscribe links in mail already sent still work, and are now precise: they stop the emails they came with and leave that Team's push notifications alone, where before they silenced both.

It links out to the message-template editor page (added last phase) and to the send log, so "change what it says" and "check who got it" both have somewhere to go.

Checks

checkLinks 2503 links · checkFacts 19 facts · checkSidebar 5 groups / 41 pages · checkA11y 51 pages · checkCsp 51 pages · checkBrand — all green, build clean.

Nothing in platform.json moves here. Phase 6 changes no version any fact tracks, and the moduleApi / protocol bumps stay held for the Phase 12/13 cutover window for the reason §6.0b gives: checkFacts fetches from main, so setting them now turns this repo red for the whole edge period.

AI disclosure

Written with Claude Code (Claude Opus 5). The commit carries the Co-Authored-By trailer.

The `administration/teams.mdx` section engagement **Phase 6** owes (`ENGAGEMENT.md` §6.0b). Code: RunicGateway/website#174 · Docs: RunicGateway/docs#187 ## The fact that has to land first **Team emails used to send with no configuration and now arrive switched off.** On an existing site nobody receives them until an operator opens Admin → Engagement → Rules and turns one on. That is the whole reason this page needs a section rather than a sentence: it is the one operator-visible consequence of the migration, and a site that upgrades without reading it experiences it as mail quietly stopping. The section also covers: - **What each of the four seeded rules sends**, and why the two roster ones ship off *and* with an hour-long cooldown — they describe things already on the Team's activity feed, arriving from a fifteen-minute sweep rather than from a person doing something. - **A rule decides whether the site sends at all; members still choose per Team.** Turning a rule on does not sign anybody up. Worth saying plainly, because "rules" is a new word on this page and it would otherwise read as an operator switch over other people's inboxes. - **Why a digest is re-read at the moment it is sent** — one digest after an outage rather than a backlog, a hidden post absent from it, and somebody who lost forum access between the post and the send not receiving it. Written as three consequences rather than as a design. - **Unsubscribe links in mail already sent still work**, and are now precise: they stop the emails they came with and leave that Team's push notifications alone, where before they silenced both. It links out to the message-template editor page (added last phase) and to the send log, so "change what it says" and "check who got it" both have somewhere to go. ## Checks `checkLinks` 2503 links · `checkFacts` 19 facts · `checkSidebar` 5 groups / 41 pages · `checkA11y` 51 pages · `checkCsp` 51 pages · `checkBrand` — all green, build clean. Nothing in `platform.json` moves here. Phase 6 changes no version any fact tracks, and the `moduleApi` / `protocol` bumps stay held for the Phase 12/13 cutover window for the reason §6.0b gives: `checkFacts` fetches from `main`, so setting them now turns this repo red for the whole `edge` period. ## AI disclosure Written with Claude Code (Claude Opus 5). The commit carries the `Co-Authored-By` trailer.

wtclaude added 1 commit 2026-08-31 06:04:16 +00:00

docs(admin): Team notification emails are engagement rules now e0d491d33b

The Teams page gains the section engagement Phase 6 owes it. The operator-facing
fact is the one that has to land first: Team emails used to send with no
configuration and now arrive switched off, so nobody gets them until a rule is
turned on in Admin → Engagement → Rules.

Also says what each of the four seeded rules sends and why the two roster ones
ship off, that a rule decides whether the site sends at all while members still
choose per Team, why a digest is re-read at send time, and that unsubscribe links
in mail already sent still work — now stopping the emails they came with without
also silencing that Team's push.

Site: RunicGateway/website#TBD · Docs: RunicGateway/docs#TBD

Co-Authored-By: Claude <noreply@anthropic.com>

wtclaude referenced this pull request from RunicGateway/website

2026-08-31 06:04:53 +00:00

feat(engagement): the email channel on the engine, and the Teams migration (engagement Phase 6) #174

wtclaude referenced this pull request from RunicGateway/docs

2026-08-31 06:05:12 +00:00

docs(website): the email channel and the Teams migration as built (engagement Phase 6) #187

whitlocktech merged commit 782e3df7e2 into edge

2026-08-31 06:07:35 +00:00

whitlocktech deleted branch docs/engagement-email-channel

2026-08-31 06:07:36 +00:00

whitlocktech referenced this issue from a commit

2026-08-31 06:07:37 +00:00