Watch · bus factor
The areas of your codebase that one resignation could break.
Watch maps code ownership over the last 90 days. Areas with one expert are flagged before a key engineer leaves.
2 critical2 high
Knowledge map
Sorted by risk. Critical first.
Paymentscritical
Bus factor 1 · 1 contributor in last 90d · last touched 18h ago
Owners
APAsha Patelprimary
Recommendation
Pair Asha Patel with a second engineer on the next Payments change. Schedule a knowledge-share session within 2 weeks.
API gatewaycritical
Bus factor 1 · 1 contributor in last 90d · last touched 14h ago
Owners
NSNoor Siddiquiprimary
Recommendation
Pair Noor Siddiqui with a second engineer on the next API gateway change. Schedule a knowledge-share session within 2 weeks.
Authhigh
Bus factor 2 · 2 contributors in last 90d · last touched 5h ago
Owners
MIMeera Iyerprimary
RVRahul Verma
Recommendation
Bring in a third reviewer to spread context. Document the architecture decision record.
Infra / deployhigh
Bus factor 2 · 2 contributors in last 90d · last touched 38h ago
Owners
APAsha Patelprimary
MIMeera Iyer
Recommendation
Bring in a third reviewer to spread context. Document the architecture decision record.
Dashboardmed
Bus factor 3 · 3 contributors in last 90d · last touched 2h ago
Owners
RVRahul Vermaprimary
NSNoor Siddiqui
KSKiran Shah
Recommendation
Healthy spread. Maintain by rotating reviews.
Why bus factor matters
The risk you don’t see until someone walks out the door
It’s invisible by default
Code ownership data exists but no one looks at it. Until they have to.
Resignations don’t pre-announce
By the time you know your payments expert is leaving, it's too late to ramp anyone.
Pairing is the cheap fix
Two engineers per area is the difference between a 1-day onboarding and a 1-month one.