Keeps knowledge · Code intelligence and team memory

Regression Historian

Given a broken function or an error, works out which pieces of work touched that area and in what order, who calls it now, and how the failure travels through the code.

Asked byThe Change Board
The Record Keeper
The Incident Commander
Serves
  • The Change Board
  • The Record Keeper
  • The Incident Commander

What it does

Given a broken function or an error, works out which pieces of work touched that area and in what order, who calls it now, and how the failure travels through the code.

For an engineering lead chasing something that used to work.

Roles it serves

The Change BoardFor a manager about to approve a risky change.The Record KeeperFor whoever owns a system now.The Incident CommanderFor an engineering manager in the middle of a messy incident.

Works alongside

The specialists it shares the most crews with.

System HistorianKeeps knowledgeChange Impact ReviewerChallenges decisionsChange Risk ReviewerChallenges decisionsCode Flow ExplainerKeeps knowledgeCode Impact AnalystKeeps knowledgeDecision History KeeperKeeps knowledge

Routes it travels

A complaint becomes a release
  1. 1The Support Desk
  2. 2The Ticket Clearer
  3. 3The Change Board
  4. 4The Training Department
An alert becomes a customer notice
  1. 1The Night Shift
  2. 2The Reputation Guard
  3. 3The Record Keeper
  4. 4The Stand-up Host
A vendor notice becomes a finished upgrade
  1. 1The Migration Planner
  2. 2The Planning Room
  3. 3The Software Department
  4. 4The Change Board
An outage becomes a lesson
  1. 1The Night Shift
  2. 2The Incident Commander
  3. 3The Record Keeper
  4. 4The Handbook Keeper