Corey JamesThe story
"Why is it built this way?" has an answer. The agent keeps a searchable record of what each working session did, what was decided and why. When something that used to work stops, it finds the change that broke it.
The crew
The specialists behind this role, grouped by the kind of work they do.
Keeps knowledge
- Meeting Decision RecorderAfter the meeting it takes the transcript, has a panel reconcile what was decided and what is still open, records each decision in the project's memory, and posts the minutes as a document.Also serves The Meeting Concierge
- System HistorianReconstructs a system's story, covering the decisions that shaped it, the changes made, the problems hit and how each was fixed, and the trade-offs accepted, in time order.Also serves The Onboarding Buddy, The Change Board
- Regression HistorianGiven 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.Also serves The Change Board, The Incident Commander
- Session RecorderOpens a record when a session starts, captures the questions asked and the answers given, tracks which model was used, and writes a summary when the session ends.Also serves The Institutional Memory
- Decision RecorderWatches the team's decisions log and working notes folder.Also serves The Software Department, The Institutional Memory
- Decision History KeeperIt turns notable actions into entries in the searchable decision history.Also serves The Control Room
- Engineering NotetakerTurns the team's working sessions into typed notes.Also serves The Institutional Memory
- Team Memory Search DeskSearches past notes by keyword, by meaning or by both, filtered by project and date.Also serves The Institutional Memory
Where this crew also works
Routes
Routes this role works in. Its place in each one is filled in.