Behavioural Process Intelligence · Public Mirror
tldraw
What we read from 299 public GitHub events across the last 4 days. Real attribution preserved — these events are already public.
FIG 1 · Lede
Mirror · tldraw · May 9, 2026
3 PRs merged with no independent review.
3 PRs merged with no independent review. Spans 1 repo. Either reviewers were anonymous to the events feed, or the PRs went in without a non-author approval.
51% of writing this window was automated. huppy-bot[bot] accounts for 28 of 40 bot events. The underlying human-engineering signal is sparse — interpret human-only stats with that in mind.
tldraw/tldraw shipped 1 release. Tagged release activity is the cleanest public signal of shipping rhythm.
tldraw/tldraw carried 95% of activity. 285 of 299 events in the last 4 days. Next: tldraw/obsidian-plugin (2).
FIG 2 · Activity stats
FIG 3 · Repos by activity
- tldraw/tldraw285 events · 46 commits · 8/15 PRs
- tldraw/obsidian-plugin2 events · 0 commits · 0/0 PRs
- tldraw/make-real1 event · 0 commits · 0/0 PRs
- tldraw/workflow-template1 event · 1 commit · 0/0 PRs
- tldraw/signia1 event · 0 commits · 0/0 PRs
- tldraw/vue-template1 event · 1 commit · 0/0 PRs
FIG 4 · Contributors by activity
- @MitjaBezensek35 events · 18% share
- @angrycaptain1930 events · 16% share
- @mimecuvalo22 events · 11% share
- @kaneel9 events · 5% share
- @AniKrisn3 events · 2% share
- @max-drake3 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.
[](https://www.assemblr.net/mirror/tldraw)