blindspot

Knowledge resilience report

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

Executive brief

Critical Resilience 32/100 · F · single maintainer profile

Top 2 risks

HIGH Diversify ownership of 'Transports' (currently single-owner) — Transports
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. Everything below is supporting detail; run with --detailed for the deep-dive sections.

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