Behavioural Process Intelligence · Public Mirror
Microsoft
What we read from 284 public GitHub events across the last day. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Microsoft · May 9, 2026
microsoft/winget-pkgs carried 56% of activity.
50% of writing this window was automated. microsoft-github-policy-service[bot] accounts for 14 of 21 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.
13 PRs merged between 22:00 and 06:00 UTC. Spans 2 repos. Either an always-on global org or a deploy-late-night habit.
microsoft/aspire-samples#1582·microsoft/winget-pkgs#372164·microsoft/winget-pkgs#372072·microsoft/winget-pkgs#372055
13 PRs merged on a weekend. Across 2 repos. Could be on-call work, could be habit drift.
microsoft/aspire-samples#1582·microsoft/winget-pkgs#372164·microsoft/winget-pkgs#372072·microsoft/winget-pkgs#372055
microsoft/winget-pkgs carried 56% of activity. 160 of 284 events in the last day. Next: microsoft/aspire-samples (11).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- microsoft/winget-pkgs160 events · 13 commits · 12/3 PRs
- microsoft/aspire-samples11 events · 1 commit · 1/1 PRs
- microsoft/sciLaMA9 events · 0 commits · 0/1 PRs
- microsoft/smc-clustering9 events · 0 commits · 0/1 PRs
- microsoft/vscode8 events · 0 commits · 0/1 PRs
- microsoft/ai-agents-for-beginners7 events · 0 commits · 0/0 PRs
FIG 4 · Contributors by activity
- @wingetbot51 events · 29% share
- @stephengillie31 events · 18% share
- @JamesNK5 events · 3% share
- @spectopo5 events · 3% share
- @andrewzbl5 events · 3% share
- @danielmeppiel5 events · 3% share
FIG 5 · Rituals we can't see from GitHub alone
Public-GitHub data shows code behaviour. The rituals below need the rest of the toolchain. With Slack, Linear, Notion and Google connected, Assemblr would also surface:
Silent merge · PR merged with no Slack/release-notes followup within 30 min.
Needs: Slack #releases channel
Orphan ticket · Linear issue closed without a corresponding code merge in 7 days.
Needs: Linear (or Jira) to see ticket transitions
Ladder break · Cross-toolkit ritual fires N-1 of N expected steps for ≥3 occurrences.
Needs: Linear + Slack to stitch the cross-tool ladder
Stale-design code · Code shipped where the linked design doc hasn't been touched in 30+ days.
Needs: Notion or Google Docs for design-doc edit history
Postmortem skip · Incident channel created, no postmortem doc within 7 days of resolution.
Needs: Slack incident channels + Notion postmortem template
Phantom standup · Standup channel post pattern that ran ≥4 weeks then stopped ≥7 days ago.
Needs: Slack standup-channel message stream
This is what we'd see for your team.
Connect GitHub, Slack, Linear, Notion, and Google. We mine the actual behavioural patterns and ship a weekly briefing your VPE will actually read.
Book a demo →FIG 6 · Embed in your README
Paste this in your README. The badge updates daily and links back to this Mirror.
[](https://www.assemblr.net/mirror/microsoft)