Reconstructing the History of an IT Project
How tickets, Git history, email headers, meeting records and technical logs are correlated into a traceable project chronology with explicit causal limits.
Read article
Requirements, Actual State and Technical Acceptance
How requirement baselines, implemented states, test evidence and acceptance records are reconstructed version by version and compared without mixing different project dates.
Read article
Reconstructing Change Requests and Change States
How change requests, tickets, Git history, pull requests, CI/CD records and releases are correlated to reconstruct which technical changes were actually implemented.
Read article
Reconstructing Architecture Decisions and Technical Risks
How intended architecture, actual system structure, decision rationale, quality goals, dependencies and technical risks are reconstructed from project evidence.
Read article
Reconstructing Test, QA and Release Evidence
How test cases, QA findings, CI/CD runs, approvals, build provenance and release artefacts are mapped to concrete source and deployment states.
Read article
Reconstructing Project Documentation and Decision History
How tickets, minutes, repositories, ADRs and project records are combined into a technical chronology of decisions without smoothing contradictions or documentation gaps.
Read article
Defining the Subject of Examination for Technical Due Diligence
How purpose, system boundaries, evidence classes, software supply chain, architecture, operations, security risks and residual uncertainty define a technical due-diligence examination.
Read article