How do the Daily Brief and the reminders keep you current?

What is in the Daily Brief?

Three things, in the order you need them.

What shipped, with the Receipt from the source: the pull request merged, the check passed, the ticket closed in your tracker. YAGNI does not call something done on its own say-so.

What is in flight, so you can see where the work actually is: a plan waiting on approval, a draft pull request in its second review round, a browser walk with video attached.

What needs a person, counted and linked. Each line points at the case file where that decision is answered. The Brief never mints a second copy of an ask, so answering it on the case file clears it everywhere it appears.

Where does it go, and when?

To the Slack channel the Team names, on the rhythm set on Harper’s line, weekday mornings by default. It reads like a standup a good engineer would write: what landed, what is stuck and why, and what someone needs to answer today, with links back to the case file and the pull request. The people who never open a new tool still see what their Team did. If your team already runs a written standup, this arrives before it, so the meeting starts from a shared account rather than from six people reconstructing one.

The Brief is not a page. Between mornings, Work holds the live record, and Latest is the log.

What happens on a quiet morning?

Nothing arrives. That is deliberate.

A Team that reviewed fourteen pull requests and needed nothing from you files one short note saying so, and it supersedes the last one rather than stacking. Calm should be cheap to read. A report that posts every morning whether or not there is news trains people to skip it, and the one morning it matters they skip that too.

How do the reminders work?

Every decision open for more than a day, a proposal waiting to be accepted, a plan waiting for approval, a build stopped to ask, reminds the person it is addressed to once a day at 9 in the workspace’s timezone. The reminders land in the tray under Waiting on you, one digest per person, and by email when that person has no Slack link. The tray never asks you to decide anything there: each reminder opens its ticket, and the decision resolves on the case file.

Two clocks close what nobody answers. A proposal untouched for three weeks closes on its own. A build stopped to ask, with no answer for two weeks, returns to planning.

What else is in the tray?

Three bands. Waiting on you, the reminders, oldest first. Needs attention, the things that need a person but are not decisions: a connector whose sync has stalled, a repository environment whose setup stopped, each with the action. Earlier, what you have seen. When anything needs attention, the bottom of the sidebar says so, and that line opens the tray on it.

How do you tune Harper’s lines?

On the Team page, under Any time, the same way you tune any line. The Daily Brief line holds the channel, the rhythm, and what it covers: which repositories, whether to include spend, how much to say about a routine merge. A deploy notes line posts to a channel on every deploy of an environment you name. Harper is on the Team through its own lines, so the Checkout Team can post into its own channel on its own clock without changing what the Platform Team sees. Everything a reader sees still obeys that Team’s audience.

What should you do with the Brief?

Read it, then answer what is yours.

The decisions it lists are the raw material of everything else. A proposal you accept, a plan you send back, a pull request you merge: each goes on the line’s track record, and each correction is a candidate Playbook rule. Ten minutes with the Brief each morning is the whole management loop. If it takes longer than that, tell Harper to say less.