Behavioural Process Intelligence · Public Mirror

Google

What we read from 300 public GitHub events across the last 10 weeks. Real attribution preserved — these events are already public.

FIG 1 · Lede

Mirror · Google · May 9, 2026

9 PRs merged with no independent review.

9 PRs merged with no independent review. Spans 8 repos. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.

google/ink#630·google/device-infra#5349·google/ChromeBrowserEnterprise#36·google/nearby#4315·google/crubit#986

14 issues opened, only 2 closed. Net +12 this window. Triage backlog is growing — maintainer queue lengthening.

google/gemma.cpp#909·google/xls#4231·google/quiche#125·google/quiche#124·google/quiche#123

nsamarakkody authored 9/10 commits in google/ChromeBrowserEnterprise. 90% concentration in this window. If nsamarakkody stops, google/ChromeBrowserEnterprise stalls.

google/ChromeBrowserEnterprise·@nsamarakkody

66% of writing this window was automated. copybara-service[bot] accounts for 39 of 51 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.

@copybara-service[bot]

12 PRs merged between 22:00 and 06:00 UTC. Spans 9 repos. Either an always-on global org or a deploy-late-night habit.

google/ink#630·google/xrblocks#262·google/device-infra#5349·google/budoux#1223

12 PRs merged on a weekend. Across 9 repos. Could be on-call work, could be habit drift.

google/ink#630·google/xrblocks#262·google/device-infra#5349·google/budoux#1223

google/xrblocks carried 11% of activity. 34 of 300 events in the last 10 weeks. Next: google/adk-go (31).

google/xrblocks

FIG 2 · Activity stats

Repos79

Contributors140

PRs opened13

PRs merged12

Commits52

Releases0

Reviews10

Issues opened14

FIG 3 · Repos by activity

google/xrblocks34 events · 6 commits · 3/2 PRs
google/adk-go31 events · 0 commits · 0/0 PRs
google/ChromeBrowserEnterprise19 events · 10 commits · 1/1 PRs
google/skills15 events · 0 commits · 0/0 PRs
google/crubit15 events · 11 commits · 2/0 PRs
google/adk-samples12 events · 0 commits · 0/1 PRs

FIG 4 · Contributors by activity

@salmanmkc12 events · 6% share
@nuthalapativarun11 events · 5% share
@LiD020911 events · 5% share
@nsamarakkody10 events · 5% share
@ruofeidu10 events · 5% share
@z3moon4 events · 2% 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.

[![Behavioural Mirror](https://www.assemblr.net/mirror/google/badge.svg)](https://www.assemblr.net/mirror/google)