The Due-Diligence Analyst

For a CTO inheriting or acquiring a codebase.

One signal · 9 specialists · one result

Speaks to people1
Challenges decisions2
Keeps knowledge3
Audits and guards3

How the work moves

Six steps, each done by one specialist

Starts with

A codebase being inherited or acquired

First

1Takes the repository in and makes it searchableCodebase Intake Engineer 2Maps how the parts of the code fit togetherCode Map Builder 3Compares the documentation with what the code doesDocumentation Drift Auditor

Then

4Lists capabilities and the parts costly to changeTechnical Due-diligence Researcher 5Flags code that nothing appears to callDead Code Finder 6Presents the findings as a briefing in a meetingBoard Briefing Presenter

Ends with

A written report and a meeting briefing on the codebase

the signalthe resultEach step is done by one specialist on the crew

The story

The agent takes the repository in, maps how it fits together and compares the documentation with what the code does. It lists what the system can do, what is dead and what would be expensive to change. The findings come as a written report and a briefing the agent presents in a meeting.

The crew

The specialists behind this role, grouped by the kind of work they do.

Speaks to people

Board Briefing PresenterIt turns an agreed plan into a briefing deck, joins the video meeting as a named digital colleague, presents the deck slide by slide, and drops the plan link into the meeting chat.Also serves The Advisory Board, The Presenter

Keeps knowledge

Codebase Intake EngineerBrings a codebase in from a local folder or straight from GitHub or GitLab, recommends which file types to include, splits the code along function and type boundaries for eight languages, and makes it searchable by meaning and by name.Also serves The Search Keeper
Code Map BuilderBuilds and maintains the dependency map: calls, imports, implementations, references, definitions and re-exports.Also serves The Search Keeper
Technical Due-diligence ResearcherIt surveys a large codebase without changing it and writes structured findings, a source list, open questions and an area report for each part of the estate.Also serves The Research Desk

Challenges decisions

Platform Capability ReviewerThis agent compares what the platform's control layer and GPU servers can actually do with what the plans say, and closes each build stage with a written review.Also serves The Migration Planner
Architecture ReviewerReads a proposed change for how it fits the existing design and writes its findings on the ticket.Also serves The Review Panel

Audits and guards

Documentation Drift AuditorCompares what internal documents say with what the code actually does and lists each mismatch with the document section and the file and line.Also serves The Handbook Keeper
Dead Code FinderLists functions and types that nothing appears to call, as candidates for a person to review.Also serves The Second Opinion
Independent Code AuditorAudits a running system read-only in parallel tracks (interfaces, storage, runtime and deployment, test honesty) and reports every finding with file, line and severity against what the documentation claims.Also serves The Second Opinion

Where this crew also works

Each bar counts the specialists this role shares with another.

Routes

Routes this role works in. Its place in each one is filled in.

An acquisition becomes a working team

The engineering behind this role

Memory and code intelligence for agentsCapability All capabilitiesThe engineering, by what it does