Team Architecture Digest

The team digest delivers a recurring email recap of architecture activity to a team's mailing list. Every team configures its own schedule, timezone, recipient address and the sections it cares about — so the right people see the right information at the right time, without having to log in.

Only projects owned by the team are included in its digest, so each team's email is scoped to its own perimeter.

What's in a digest

A digest can include up to seven sections, each toggleable per team:

  • Architecture health — drift score with delta vs the previous period, conformance pass rate, deployment count, lead time and MTTR (DORA snapshot).
  • Architecture changes — C4 elements added, updated or removed (top items).
  • Decisions (ADRs) — ADRs opened or merged in the period.
  • Pull requests — Architecture Change Requests by status.
  • Conformance — new violations and pass rate.
  • Discussions — new comment threads opened on architecture elements (containers, components, ADRs, …).
  • Insights — generated architecture insights for the period.

Sections that have no new activity for the period are omitted automatically — your team won't get a half-empty email.

Enabling the digest

A team admin sets up the digest from the team settings:

  1. Open the team selector and click the team's settings.
  2. Switch to the Digest tab.
  3. Enter the team email (typically a shared mailing list like team-frontend@company.com).
  4. Pick a frequency: weekly, every two weeks, or monthly.
  5. Pick the day (Monday by default for weekly/biweekly, day 1 for monthly) and the hour of delivery.
  6. Pick the team's timezone so the digest arrives at the correct local time.
  7. Check the sections you want included.
  8. Click Save.

The digest stays disabled (Disabled frequency) until you save with a non-off frequency.

Preview and test

Before turning on the recurring schedule, validate the look and content:

  • Preview — opens an inline preview of the email rendered with the latest data. No email is sent.
  • Send test — ships a single email immediately to the team's configured digest address. Useful to verify deliverability and how the email looks in your real client.

The preview shows the same HTML the recipients will see, including dark/light mode adaptation when their email client supports prefers-color-scheme.

How scheduling works

A scheduler runs every hour. For each team that is not Disabled:

  • The current time is converted to the team's timezone.
  • If the local hour matches Send at, the day rule is checked:
    • Weekly matches the configured weekday.
    • Every two weeks matches the weekday on even ISO weeks.
    • Monthly matches the configured day-of-month, capped at the last day of the month (so day 31 sends on Feb 28).
  • If a digest was already sent within the safety window (6 days for weekly, 13 for biweekly, 27 for monthly), the run is skipped — protecting against duplicate sends if the cron retries.

You can change the schedule at any time. The next eligible tick will pick up the new configuration.

Recipient

Each team has a single digest_email address. Use a shared mailing list when you want every team member to receive the digest — the digest itself is not personalised, so a single recipient with team-wide forwarding is the simplest model.

If the address is empty when you switch the frequency away from Disabled, the save is rejected.

Permissions

  • Team members can read the digest configuration.
  • Team admins can update the configuration, run a preview, send a test email, and turn the digest on/off.
  • Organization admins are treated as team admins for every team in their org.

Stopping or pausing the digest

Set the frequency to Disabled in the team settings — the digest stops at the next tick. The configuration is preserved, so you can re-enable later without re-entering everything.

Related