Behavioural Process Intelligence · Public Mirror
Meta
What we read from 293 public GitHub events across the last 2 weeks. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · Meta · May 9, 2026
14 PRs opened, zero merged.
14 PRs opened, zero merged. Reviewers are looking (22 reviews submitted) but nothing's landing. Either window too short for normal lifecycle, or merge pipeline stalled.
facebook/sapling#1300·facebook/dotslash#133·facebook/content-review-filters#19·facebook/infer#2043·facebook/create-react-app#17235
flow-bot authored 8/8 commits in facebook/flow. 100% concentration in this window. If flow-bot stops, facebook/flow stalls.
85% of writing this window was automated. meta-codesync[bot] accounts for 35 of 50 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.
facebook/lexical carried 17% of activity. 50 of 293 events in the last 2 weeks. Next: facebook/pyrefly (34).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- facebook/lexical50 events · 0 commits · 0/0 PRs
- facebook/pyrefly34 events · 2 commits · 0/0 PRs
- facebook/flow21 events · 16 commits · 0/0 PRs
- facebook/dotslash21 events · 3 commits · 0/1 PRs
- facebook/docusaurus19 events · 0 commits · 0/1 PRs
- facebook/react11 events · 0 commits · 0/0 PRs
FIG 4 · Contributors by activity
- @mayrang30 events · 25% share
- @etrepum16 events · 13% share
- @flow-bot8 events · 7% share
- @yangdanny975 events · 4% share
- @react-native-bot3 events · 3% share
- @levensta3 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/facebook)