The Root Hub

The root hub is the root board's landing screen. It opens on the Diary: the pieces of work across every app in the weeks the hub's period covers, flagged and breaking changes first, with who depends on each change. Below it, Fleet attention lists what waits on a person, app by app.

The root board opens on it once the layers under it include app boards. Its header holds the period control, which sets the period the Diary, Shipped and System scorecard cards cover.

Expand

1. 1

   The weeks

   Select a bar to list only that week in every diary card, and select it again to go back to the period.

2. 2

   Who worked

   Worked these weeks names each app that did work, with its commits, and Nothing recorded the apps with no period in those weeks.

3. 3

   Filters

   The filters narrow the list, each with its count.

4. 4

   Architecture

   Point at an entry to light it on Architecture, and select it to keep it lit.

Set up

The Diary reads the change periods your repos record. Run /changes in each app's repo; after that, a scheduled run keeps the current week up to date.

Who a change reaches comes from the calls and events adopted from each app and the edges drawn between systems on the root canvas. Who depends on a change covers what counts.

Read the diary

The root hub's diary is the Changes screen's diary across every app, told in three cards. The Diary card runs across the full width, then Diary entries (headed Entries on the hub) sits beside Architecture, the root canvas. They show the same weeks, so selecting a week or an entry in one moves the others. Customize moves, resizes or removes each on its own.

The Diary card

Its first line names whose weeks they are: the one app that worked, or how many did. Then come the weeks listed, marked still open when one week is selected and it hasn't ended, and their commits with the share that name a coding agent. Under it, one sentence says what leads: the top entry, why it leads, and how many more entries there are. A breaking change says and callers break, or names them, such as and callers in Portal break; a flag says a rule flagged it for review.

The row of bars is the weeks the period control reaches, the current week marked ·open: 7 days shows this week and last, 30 days about five weeks. A bar's height is its commits, and its lower part the commits that name a coding agent; the marks above it are its highest-ranked entries. Select a bar to list only that week in every diary card, and select it again to go back to the period.

Under the bars:

• How many of the listed commits are in smaller pieces of work no entry lists.
• Worked these weeks names each app that did work, with its commits. With one week selected, it reads Worked this week. Nothing recorded names the apps with no period in those weeks, with the date of their last one. An app there hasn't run /changes, which isn't the same as a quiet week.

The Diary entries card

The filters narrow the list, each with its count: All, Contracts, Breaking or flagged and Your rules. Entries rank Flag to review first, then Breaks callers, Contract changed, Hit a rule and Work, and then by commits. Each row names its app, its commits and who did the work, and a chip per rule with its impact. The card lists up to 30 and counts the rest as +N more in Changes.

Point at an entry to light it on Architecture. With the board map open, it also rings the parts of the app the entry landed on, such as its server or web layer. With the map closed, the Map button rings once instead. The board map shows each app's commits beside its row too. Select an entry to keep it lit, and again to let it go. View detail opens the entry on the Changes screen; Open in Changes opens the whole diary.

The Architecture card

The root canvas, read-only, painted with the listed weeks. The entry you point at or select lights its app's system and the systems that depend on it; the rest of the canvas dims. Up to three lenses paint it, each offered once there is data for it:

• Commits: a glow whose strength is each system's share of the commits, a ring where a contract changed, and a red mark where a boundary rule is broken.
• Autopilot: each system's share of commits that name a coding agent. A dashed ring marks one that is mostly agent-written and had a week with no work item behind it.
• Drawing vs code: how much of each app's drawn boards its code backs, from its latest coverage push. A dashed ring marks one under half built, or built from code that has changed since.

Expand

1. 1

   Lenses

   Up to three lenses paint the canvas, each offered once there is data for it.

2. 2

   The lit systems

   The entry you point at or select lights its app's system and the systems that depend on it; the rest of the canvas dims.

3. 3

   Who it reaches

   Under the canvas, a line names the systems that depend on the entry's app, and those one step further out.

Replay the weeks steps every diary card through the row, oldest first, a week at a time. Each step marks the week on the bars, lists its entries, paints it on the canvas, and with the board map open rings every board the week's work landed on. Glow is scaled to the busiest week, so a quiet week reads quiet. A week you select paints that week. Select the canvas to open it.

Under the canvas, a line names the systems that depend on the entry's app, and those one step further out. It reads like "Orders and Billing depend on Catalog today, and through them Storefront." It follows the entry you point at or select, or else the top contract change. For work that changed no contract, it says the work stays inside its app.

Use the cards

Below the Diary, the root hub shows:

• Fleet attention lists the rows of every app's attention queue, the most urgent first, each named with its app. A flag's row opens its diary entry with Open change.
• Insights and Work items across every app in the tree.
• Apps gives each app board a tile with its pulse, last activity, coverage and outstanding work.
• Context boards and System aspects.
• Recent activity: every push across the tree, newest first.

Add widget offers the System scorecard, Shipped, Playbooks, About, and a card per aspect kind declared across systems, such as Boundaries. On a wide screen, Customize in the header moves, resizes and removes cards. A layout saved before the diary arrived gets its three cards on top, with your arrangement moved down unchanged. App Boards & the Hub covers arranging cards, and Change Cards covers the ones that count over the period.

FAQ

Why does the Diary say nothing shows who depends on an app?

Neither the adopted calls and events nor the root canvas's edges show anything depending on that app. Adopt the app's API clients and event catalog, or draw the dependency on the root canvas.

Can the diary come to Slack?

Yes. An automation with Monday briefing ticked posts the week's entries that hit a change rule on a schedule; see Automations.

Does the Diary rank people?

No. An entry names who did the work with which agent, so you know who to ask. Nothing on the hub counts or ranks people.

What's next