| 1 | call-chain | Execution paths between functions, jobs, services, modules, and external calls | If this entry point runs or changes, which code paths and downstream calls follow? |
| 2 | business-journey | End-to-end user, customer, and operational journeys across the captured scope | Which steps, systems, hand-offs, and outcomes make up a business journey? |
| 3 | business-rules | Decision logic, calculations, validation, eligibility, routing, and policy constraints | Which rules control behaviour, and where are they implemented or contradicted? |
| 4 | ui-flow | Screens, states, navigation, user actions, validation, and interface journeys | How does a user move through the interface, and which backend behaviours support each step? |
| 5 | data-relation | Entities, records, keys, schemas, joins, and semantic relationships | Which data structures relate, and what integrity assumptions connect them? |
| 6 | data-lineage | Data origin, movement, transformation, persistence, and downstream use | Where does this data come from, how is it transformed, and where does it go? |
| 7 | domain-model | Domain concepts, vocabulary, entities, responsibilities, and bounded contexts | What concepts organise the system, and where are boundaries or meanings inconsistent? |
| 8 | capability-map | Business and technical capabilities and the components that realise them | Which system parts provide a capability, and where is ownership fragmented? |
| 9 | contract-surface | APIs, events, files, schemas, commands, and other declared integration contracts | Which consumers depend on a contract, and what could break if it changes? |
| 10 | interface-mappings | Interface boundaries to the outside world and across internal seams, including partner messaging, financial messaging, and file or batch feeds | Where does this estate talk to something else, and on whose terms? |
| 11 | integration-topology | Connected systems, routes, protocols, directionality, and integration hubs | How do systems connect, and which routes or hubs create coupling? |
| 12 | reliability-map | Failure modes, retries, timeouts, recovery, observability, resilience, and operational risk | How can the system fail, how is failure detected, and how does it recover? |
| 13 | ops-inventory | Batch jobs, schedules, runbooks, controls, operational utilities, and support procedures | What keeps the system operating, and which activities are manual or time-bound? |
| 14 | infra-inventory | Runtime, compute, network, storage, middleware, platform, and deployment components | What infrastructure must exist for the captured system to run? |
| 15 | security-posture | Authentication, authorisation, secrets, trust boundaries, exposure, and security controls | Where are the captured attack surfaces, privileges, trust boundaries, and control gaps? |
| 16 | compliance-footprint | Regulatory obligations, controls, audit evidence, and regulated-data handling | Which captured behaviours or data touch a compliance obligation or control? |
| 17 | dependency-blast-radius | Upstream and downstream dependencies that may transmit a change | What code, contracts, data, jobs, controls, or consumers could a proposed change affect? |
| 18 | migration-seams | Candidate boundaries for strangling, extraction, replacement, coexistence, or phased migration | Where can change be isolated with the least coupling and clearest evidence? |
| 19 | dead-code | Implementation that appears unused, unreachable, superseded, or orphaned | What may be removable, and what evidence is still missing before deletion is safe? |
| 20 | as-is-archaeology | Current structure, historical residue, inconsistencies, and undocumented implementation reality | What actually exists, and where does it conflict with the documented or intended design? |
| 21 | legacy-estate-map | Mainframe and legacy components behind a modern product, and the systems scheduled for or resisting modernisation | What older estate is still carrying the business, and what depends on it? |