blindspot

Knowledge resilience report

Repository: /private/tmp/cohort10/ollama
Generated 2026-05-20 13:16 UTC · window: last 90 days · blindspot v0.2.0

Executive brief

Fragile Resilience 54/100 · F · team profile

Top 3 risks
  1. HIGH Diversify ownership of 'integration' (currently single-owner) integration
  2. HIGH Diversify ownership of 'llama' (currently single-owner) llama
  3. HIGH Diversify ownership of 'ml' (currently single-owner) ml

Patterns detected Fragile Velocity

Business implication An unexpected departure of the top contributor would orphan 262 critical files and likely slow feature delivery by 3–5 weeks while the team learns the surface.

Executive summary

Pair Daniel Hiltgen (dhiltgen@github) on 'ml' — bus factor 1 across 25 files

Resilience is **Fragile** (54/100). Weakest dimension: ownership concentration (F). This is a structural property — typical for founder-led or single-maintainer projects — not a verdict on project health.

Risk inventory: 7 service(s) rest on a single contributor; 262 file(s) would become orphans if the top contributor leaves; 10 file(s) carry high correction load (≥35% fix/revert); 32 service(s) lack AI-readable operational context.

Top recommended action: Pair Daniel Hiltgen (dhiltgen@github) on 'ml' — bus factor 1 across 25 files

💡 Want a richer, prose-style executive summary? Add a cloud LLM key (Anthropic or OpenAI) to your scan:
--api-key sk-ant-... --provider anthropic --model claude-sonnet-4-6
or set narrative.api_key in .blindspot.yaml. Without a key, this rule-based narrator is used — deterministic, in-process, no network.

Overview

Engineering Resilience Score

Overall
54/100 F
Fragile

Fragile resilience overall (score 54). Weakest dimension: AI operational readiness at 0.

Team-based Multiple maintainers without a single dominant contributor.

Key signals — the six questions

Six concrete questions, each with a one-number answer. This is the report. Everything below is supporting detail; run with --detailed for the deep-dive sections.

Ownership concentration F
8 services rest on a single owner
If that person is unavailable, no one else can confidently change these areas.
Single-engineer dependency
262 files orphan if the top contributor leaves
These files would have no confident owner the day that person walks out.
Knowledge decay
No file is critically decayed
Owners are still close to the code they own.
Review depth
Reviews carry substantive comments
Approvals reflect real scrutiny, not rubber-stamping.
Correction load A
10 files carry a heavy bugfix tail
After each feature these files get a stream of fix/revert commits — stability is paying for delivery pace.
AI-readable context F
Repo lacks AI-readable operational context (0/5)
No agent rules (CLAUDE.md), specs, architecture notes / ADRs at the repo root — a new human or AI agent must reverse-engineer the codebase.

Recommended actions

Concrete next steps derived from the signals in this report. Each action is tied to a specific finding — treat them as conversation starters with the team, not directives.

Priority Confidence Category Title Target Evidence
High Medium Ownership Diversification Single-owner concentration Diversify ownership of 'integration' (currently single-owner)
Service 'integration' has bus factor 1 across 23 files; Daniel Hiltgen (dhiltgen@github) holds 98% of effective ownership. Pair them with at least two additional engineers and rotate code reviews for this area over the next 60 days. Cadence: aim to cover the top files this quarter.
▸ Bus factor 1 over 23 files — Daniel Hiltgen (dhiltgen@github) holds 98% of effective ownership.
integration bus_factor=1, top_owner_coverage=98%, files=23
High Medium Ownership Diversification Single-owner concentration Diversify ownership of 'llama' (currently single-owner)
Service 'llama' has bus factor 1 across 10 files; Daniel Hiltgen (dhiltgen@github) holds 89% of effective ownership. Pair them with at least two additional engineers and rotate code reviews for this area over the next 60 days.
▸ Bus factor 1 over 10 files — Daniel Hiltgen (dhiltgen@github) holds 89% of effective ownership.
llama bus_factor=1, top_owner_coverage=89%, files=10
High Medium Ownership Diversification Single-owner concentration Diversify ownership of 'ml' (currently single-owner)
Service 'ml' has bus factor 1 across 25 files; Daniel Hiltgen (dhiltgen@github) holds 83% of effective ownership. Pair them with at least two additional engineers and rotate code reviews for this area over the next 60 days. Cadence: aim to cover the top files this quarter.
▸ Bus factor 1 over 25 files — Daniel Hiltgen (dhiltgen@github) holds 83% of effective ownership.
ml bus_factor=1, top_owner_coverage=83%, files=25
High Medium Ownership Diversification Single-owner concentration Diversify ownership of 'sample' (currently single-owner)
Service 'sample' has bus factor 1 across 5 files; Jeffrey Morgan (jmorganca@gmail.com) holds 100% of effective ownership. Pair them with at least two additional engineers and rotate code reviews for this area over the next 60 days.
▸ Bus factor 1 over 5 files — Jeffrey Morgan (jmorganca@gmail.com) holds 100% of effective ownership.
sample bus_factor=1, top_owner_coverage=100%, files=5
High Medium Ownership Diversification Single-owner concentration Diversify ownership of 'updater' (currently single-owner)
Service 'updater' has bus factor 1 across 7 files; Daniel Hiltgen (dhiltgen@github) holds 87% of effective ownership. Pair them with at least two additional engineers and rotate code reviews for this area over the next 60 days. Start with these 2 files: app/updater/updater_darwin.go, app/updater/updater_windows.go.
▸ Bus factor 1 over 7 files — Daniel Hiltgen (dhiltgen@github) holds 87% of effective ownership.
updater bus_factor=1, top_owner_coverage=87%, files=7, top_files=app/updater/updater_darwin.go+1