Behavioural Process Intelligence · Public Mirror

Ollama

What we read from 299 public GitHub events across the last day. Real attribution preserved — these events are already public.

FIG 1  ·  Lede

Mirror · Ollama · May 9, 2026

dhiltgen is carrying 58% of the human writing work.

dhiltgen is carrying 58% of the human writing work. 14 of 24 commit + PR-open + PR-merge events from a single human contributor.

@dhiltgen

ollama/ollama carried 97% of activity. 289 of 299 events in the last day. Next: ollama/ollama-js (5).

ollama/ollama

13 issues opened, 69 issue comments. Issue traffic is 3.4× the code traffic this window — consumer-facing org or triage burst.

FIG 2  ·  Activity stats

Repos3
Contributors203
PRs opened5
PRs merged2
Commits17
Releases0
Reviews4
Issues opened13

FIG 3  ·  Repos by activity

FIG 4  ·  Contributors by activity

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/ollama/badge.svg)](https://www.assemblr.net/mirror/ollama)
Ollama Behavioural Mirror badge