Architecture in Your Inbox: Introducing the Weekly Team Digest

The drift score on our Payment service has been trending up for six weeks. Two ADRs are open and waiting for review. A high-severity conformance violation appeared on Monday. The new Inventory service got owned by a team that doesn't exist yet.

I know all this because I logged into archyl this morning and clicked through five pages.

Most of the engineers on those teams don't know any of it.

That's the problem we set out to solve this week. Architecture insights — drift, conformance, ADRs, decisions, discussions — exist in archyl. They're indexed, computed, surfaced in dashboards. But the people who need them most are heads-down shipping code, not refreshing dashboards. So the insights stay where they are, and architecture decisions keep happening in vacuums.

Today we're shipping the Architecture Team Digest. A recurring email that brings the architecture status of each team to the inbox of the team that owns it. Weekly, biweekly, or monthly. The team picks.

Dashboards lose. Inboxes win.

There's a reason GitHub still emails you about pull requests in 2026 even though the website is right there. There's a reason Linear sends a daily digest. There's a reason every analytics tool has a "weekly summary" feature.

People don't pull. They scan what arrives. A dashboard you have to remember to open is a dashboard you forget to open.

For ten years we've been told that "Slack and dashboards killed email." But dashboards are great when you know what you're looking for, and Slack is great when you need to react. Neither is great at a weekly "here's everything that mattered, in two minutes" — which is exactly what an engineering team needs to stay aligned on architecture without making it a meeting.

Email, ironically, is the right surface. Quiet, dense, archivable, searchable, forwardable. And every team already has a mailing list.

What's in a digest

Each team's digest is scoped to the projects it owns. Nothing irrelevant, nothing from other teams' perimeter.

Inside, up to seven sections — the team picks which ones to keep:

• Architecture health — drift score with the delta vs the previous period, conformance pass rate, deployment count, lead time, MTTR. The DORA snapshot, in a single row.
• Architecture changes — which C4 elements were added, updated, or removed. Top items.
• Decisions (ADRs) — what got proposed and what got merged.
• Pull requests — Architecture Change Requests by status.
• Conformance — new violations, with severity.
• Discussions — new comment threads opened on architecture elements. The "what's being debated right now" view.
• Insights — architecture insights generated for the period.

Sections without activity are silently dropped. No half-empty emails.

The render is plain HTML. No tracking pixel, no marketing chrome. Black-on-white, monochrome, with the archyl wordmark at the top — because transactional emails should look like Linear or Vercel, not like a campaign. Dark mode flips automatically when your client supports prefers-color-scheme.

Setup takes fifteen seconds

Open your team settings, switch to the Digest tab. Type a team email. Pick a frequency, a day, an hour, and the timezone the team actually lives in. Check the sections. Save.

You can preview the email in-app without sending anything, and ship a single test email to verify deliverability and rendering before turning the schedule on.

The scheduler runs every hour and ships each team's digest at the configured local time. A weekly digest set for Monday 9am in Europe/Paris arrives at 9am Paris — even if Paris is on summer time, even if you're a self-hosted instance running in America/Los_Angeles. Each team's digest follows the team's own clock.

Why this matters

Architecture is a team property. It's owned collectively, and it evolves whenever any of its owners ship code. The hardest problem isn't capturing the architecture — diagrams, ADRs, drift detection, all of that we've been doing for years. The hardest problem is closing the loop between what the architecture says and what the team knows.

A weekly digest does something simple but rare: it gives the team a single five-minute moment, every week, to be on the same page about its own architecture. No standup. No tool to open. No habit to build. Just the email everyone already reads.

If you're an engineering manager, that moment is gold. If you're an engineer on the team, it's the first time architecture context actually came to you instead of you having to chase it.

Available now

Architecture Team Digests are live for every team. Open your team settings, hit the Digest tab, and your first recap goes out at the next scheduled tick.

Let us know what your team thinks. We're already prototyping Slack and Teams equivalents for organizations that prefer chat over inbox — but for the weekly cadence, we're convinced the inbox is the surface that delivers context without becoming noise.

Architecture, finally, where the people who own it actually live.

Want to dig deeper into how architecture context flows through engineering teams? Read about Architecture Change Requests for the pull request workflow on your C4 model, or Architecture Chat to ask any question about your stack and get an answer grounded in your own model.