Change Cards

The change cards count change over the period the hub's period control sets. They show what shipped, the system's numbers across apps, who worked on what, and which services took the most work. Use them for the totals behind the diary, which tells the same weeks as pieces of work.

Most of them count change periods, which /changes records from each repo's git history. Shipped counts work items, and the aspect figures count /aspects pushes.

The diary is three cards on a hub. Diary leads the root hub and sits under the attention queue on an app hub. It sums up the weeks the period control reaches, over a row of bars. Select a week to list only that week; select it again, or change the period, to go back. On an app hub, Worked on under the bars names the nodes the listed weeks' commits landed on, busiest first, up to six. The Diary entries card, headed Entries on the hub, lists those weeks' diary entries, ranked.

Beside the entries, Architecture paints the change on the board's canvas: the root canvas on the root hub (The Architecture card), the app board's own on an app hub. Point at or select an entry to light where it landed. View detail opens the entry on the Changes screen, and Open in Changes opens the full diary.

Every card opens on what it lists, and a card with nothing in the period says why and how to fill it, such as running /changes.

The period control

The control in a hub's header sets the period every change card counts over. It offers the periods the workspace sets in Workspace settings → Reporting, shortest first. Each is a window back from now, so opening the hub changes nothing: what changed this week is still there when you come back to read it.

• Until you pick, the control opens on the workspace's Default period, 30 days unless the workspace sets another.
• Your pick is remembered in this browser, and holds while the workspace still offers it.

A period counts when any part of it falls in the window. Every tab on the Changes screen has the same control in the screen's header. A change card that is empty in a short period while a longer one has changes says how many and offers the longer period.

Shipped

Shipped lists the work items completed in the period, across the hub's boards. Each row names the work item, its epic and who completed it, and on the root hub its app, and links to its pull request when it has one.

A row reads Verified once a push finds its changes in the code, and Awaiting a sync until then. It reads Already true in code when a sync completed it because the change was already there. The last line counts how many a push verified.

System scorecard

System scorecard puts the root hub's numbers that span apps in one row. Five are about what passes between systems: Dependencies between systems, Loops between systems, Rules violated, Events that disagree and Calls nobody answers. Three count the period's change periods and open the Changes screen: Apps changed a contract, Periods with no work item and Commits naming an agent. The rest are Shipped, Apps live, Awaiting acceptance and Boards built.

A period had a work item when a commit in it cites one on the app's boards, such as #12, or a push in it completed or verified one. Work items behind a piece of work has the detail.

A cell with a warning mark has something to check, and most cells open the screen behind the number. A cell whose source hasn't answered yet is left out, never shown as zero.

People and agents

People and agents is a tab on the Changes screen. It shows, per app, how many of the period's commits name a coding agent, of all its commits, with a line of the share period by period. Below each app, the people involved and the agents their commits name.

Rows are sorted by app. People are listed, never counted or ranked. A commit names an agent when a known agent authored it or co-signed it with a trailer such as Co-Authored-By; any other commit names none.

Busy services

Busy services is a tab on the Changes screen. It lists the services the period's commits touched, most commits first, with how many periods touched each and how many things depend on each directly. Beside the list, a chart sets commits against dependents, so a service that is both busy and depended on stands out in its corner.

A commit that touches files in five services counts once in each. A period converted from an older sync record names its services without a count.

Aspect figures

On an app hub, each aspect card also says how many items its /aspects pushes added, changed and removed in the period, such as tables or endpoints. Edits made by hand on the board are not in them. An /aspects run that extracts the same items again counts every re-sent item as changed, so changed is an upper bound.

The root hub's aspect cards carry no figures: a root card counts the rows declared on the root, and summing every app's pushes under it would contradict that number.

FAQ

I synced, so why are the change figures still empty?

A sync records no period. Run /changes in the repo: it reads the git history back to the workspace's Read history back setting and records one period per week or month.

Why is a card empty when I know work happened?

Nothing landed in the period the control is set to. If a longer period has changes, the card says how many and offers to show it; the period control switches the whole hub.

Can I see which person made a change?

No. A diary entry and People and agents name the people and agents involved, and Shipped names who completed a work item. Nothing counts or ranks people.

What's next