Knowledge resilience report
Critical Resilience 32/100 · F · single maintainer profile
Transports
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.
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
--api-key sk-ant-... --provider anthropic --model claude-sonnet-4-6or set
narrative.api_key in .blindspot.yaml.
Without a key, this rule-based narrator is used — deterministic,
in-process, no network.
Critical resilience overall (score 32). Weakest dimension: AI operational readiness at 0.
Single-maintainer Concentration is structural and expected.
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.
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 |
Each signal above, opened up — the files, services and people behind the headline number. Risk signals are expanded by default; healthy ones stay collapsed.
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.
| Service | Files | Bus factor | Risk | Top owner | Their 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% |
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.
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
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
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.
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.
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% |