blindspot

Knowledge resilience report

Repository: /private/tmp/cohort10/MassTransit
Generated 2026-05-20 15:39 UTC · window: last 90 days · blindspot v0.2.1

Executive brief

Critical Resilience 32/100 · F · single maintainer profile

Top 2 risks
  1. HIGH Diversify ownership of 'Transports' (currently single-owner) Transports
  2. HIGH Diversify ownership of 'doc' (currently single-owner) doc

Business implication An unexpected departure of the dominant contributor would orphan 162 critical files — this is structural for a single-maintainer project, but it is what successor planning must address first.

Executive summary

Pair Chris Patterson (chris@phatboyg.com) on 'doc' — bus factor 1 across 149 files

Resilience is **Critical** (32/100). Weakest dimension: ownership concentration (F). Repo profile: single-maintainer. Concentration is structural and expected.

Risk inventory: 2 service(s) rest on a single contributor; 162 file(s) would become orphans if the top contributor leaves; 5 service(s) lack AI-readable operational context.

Top recommended action: Pair Chris Patterson (chris@phatboyg.com) on 'doc' — bus factor 1 across 149 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
32/100 F
Critical

Critical resilience overall (score 32). Weakest dimension: AI operational readiness at 0.

Single-maintainer Concentration is structural and expected.

Key signals — the six questions

Six concrete questions, each with a one-number answer. This is the report. Each signal opens up below into the files, services and people behind its number — run with --detailed for the architecture deep-dive.

Ownership concentration F
2 services rest on a single owner
If that person is unavailable, no one else can confidently change these areas.
Single-engineer dependency
162 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
Features land without a bugfix tail
Code ships and stays shipped — low rework pressure.
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 Low Ownership Diversification Single-owner concentration Diversify ownership of 'Transports' (currently single-owner)
Service 'Transports' has bus factor 1 across 7 files; Chris Patterson (chris@phatboyg.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 7 files — Chris Patterson (chris@phatboyg.com) holds 100% of effective ownership.
Transports bus_factor=1, top_owner_coverage=100%, files=7
High Low Ownership Diversification Single-owner concentration Diversify ownership of 'doc' (currently single-owner)
Service 'doc' has bus factor 1 across 149 files; Chris Patterson (chris@phatboyg.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. Cadence: one file per sprint to keep the load reviewable.
▸ Bus factor 1 over 149 files — Chris Patterson (chris@phatboyg.com) holds 100% of effective ownership.
doc bus_factor=1, top_owner_coverage=100%, files=149

Signal details

Each signal above, opened up — the files, services and people behind the headline number. Risk signals are expanded by default; healthy ones stay collapsed.

Ownership concentration — service risk map risk

Bus factor measures how many people would need to leave before knowledge of a service is critically lost. A bus factor of 1 means a single person carries the service.

ServiceFilesBus factor RiskTop ownerTheir coverage
doc 149 1 critical Chris Patterson (chris@phatboyg.com) 100%
Transports 7 1 critical Chris Patterson (chris@phatboyg.com) 100%
(root) 1 1 critical Chris Patterson (chris@phatboyg.com) 100%
.github 1 1 critical Chris Patterson (chris@phatboyg.com) 100%
Persistence 4 2 high WhereIsW4ldo (whereisw4ldo@github) 50%
tests 3 2 high Chris Patterson (chris@phatboyg.com) 67%
Single-engineer dependency — departure scenarios risk

For each of the top contributors by aggregate ownership coverage, this is what would happen if they left tomorrow: how many files lose their primary expert, how many become unowned (orphan, top remaining coverage < 30%), and which services take the largest hit. Use this to prioritise pair-work and knowledge transfer.

CRITICAL If Chris Patterson (chris@phatboyg.com) leaves
Files affected
162 / 165
Orphan files
162 (98%)
Avg coverage loss
98%
Most-affected services
  • doc 149/149 files, 149 orphan, 100% avg loss
  • Transports 7/7 files, 7 orphan, 100% avg loss
  • tests 2/3 files, 2 orphan, 67% avg loss
CRITICAL If WhereIsW4ldo (whereisw4ldo@github) leaves
Files affected
3 / 165
Orphan files
3 (2%)
Avg coverage loss
2%
Most-affected services
  • Persistence 2/4 files, 2 orphan, 50% avg loss
  • tests 1/3 files, 1 orphan, 33% avg loss
  • (root) 0/1 files, 0% avg loss
Knowledge decay — top concerns healthy

Decay rises when an owner stops touching a file and others have been changing it. The 90-day projection shows the trajectory if nothing changes.

No file is critically decayed.
Review depth — review lineage healthy

Review data fetched from GitHub (6 PRs analyzed). A rubber-stamp ratio is the share of approvals on a file that arrived without a single review comment. Reviewer diversity measures whether several people share the review load.

Files with highest rubber-stamp ratio

No rubber-stamp patterns detected.

Files with lowest reviewer diversity

No low-diversity files detected.
Correction load — files with a bugfix tail healthy
No correction-load data for this window.
AI-readable context — operational docs coverage risk

Coverage of AI-readable organizational memory — agent rules, specs, prompts, architecture decisions, skills. The repo-root row is what the signal grades; per-service rows are shown for context. This is not an AI-generated-code detector.

Surface Agent rules Specs Prompts Architecture Skills Coverage
(repo) 0%
.github 0%
Persistence 0%
Transports 0%
doc 0%
tests 0%