blindspot

Knowledge resilience report

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

Executive brief

Fragile Resilience 41/100 · F · team profile

Top 1 risk
  1. MEDIUM Add review depth requirement for Dapper/SqlMapper.cs — Dapper/SqlMapper.cs

Business implication AI-assisted onboarding cannot soften a departure here — 6 services lack the operational context (CLAUDE.md, specs, ADRs) a new contributor or agent would load first.

Executive summary

Establish a successor for Marc Gravell (marc.gravell@gmail.com)'s work — 10 files would orphan without them

Resilience is **Fragile** (41/100). Weakest dimension: review hygiene (F).

Risk inventory: 10 file(s) would become orphans if the top contributor leaves; 1 file(s) carry rubber-stamp review patterns; 6 service(s) lack AI-readable operational context.

Top recommended action: Establish a successor for Marc Gravell (marc.gravell@gmail.com)'s work — 10 files would orphan without them

Generated by rule-based · language: en · treat as advisory, verify against the data below.

💡 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
41/100 F
Fragile

Fragile resilience overall (score 41). Weakest dimension: review hygiene 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
No service rests on a single owner
Every service has at least two people who know it.
Single-engineer dependency
10 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 F
1 files are approved without scrutiny
Most approvals on these files land with no substantive comment — quality rests on the author alone.
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
Medium Low Review Hygiene Review without scrutiny Add review depth requirement for Dapper/SqlMapper.cs
100% of approvals on this file arrived without a substantive review comment (across 2 reviews). Introduce a review checklist or require at least one substantive comment before approval is allowed.
▸ 100% of approvals on this file arrived without a substantive review comment (2 reviews). 		Dapper/SqlMapper.cs rubber_stamp_ratio=100%, reviews=2