Business rules are buried
Important decisions live in code paths, database procedures, batch jobs and integration behaviour.
Legacy system documentation
Documentation recovery is useful when it becomes a basis for review and change, not another static document set.
Harten uses available application evidence to reconstruct behaviour, dependencies, data and interfaces, then carries that understanding into a reviewable current-system specification.
The problem
Long-lived systems accumulate missing documentation, conflicting descriptions and key-person dependency. Engineers then have to rediscover the application every time something important changes.
Important decisions live in code paths, database procedures, batch jobs and integration behaviour.
Existing documents may describe an earlier system or omit operational behaviour that matters now.
What Harten produces
The aim is not exhaustive prose. It is enough structured, traceable knowledge for architects, engineers and business owners to review the system together.
Capabilities, behaviour, state, data, interfaces and technical relationships within scope.
Source support for material findings, plus questions the available evidence cannot answer.
A common baseline for deciding what must be preserved, changed or investigated further.
Human review
From documentation to change
That may be a modernisation plan, architecture option, recovery decision or a clearer handover to a delivery partner.