Key steps
Evidence-led technical assessment
- 1
Mandate
Scope and access
- 2
Evidence
Preserved materials
- 3
Tests
Reproducible findings
- 4
Report
Facts and uncertainty
Simplified teaching diagram. Steps and technical choices depend on the context; this is not a delivered client architecture.
When disagreement becomes a technical question
A company and its vendor can oppose each other over delivery of an application, the quality of a development, data recovery or respect for an announced scope. Exchanges often become accusatory when the first need is to know which technical elements are accessible and what they can actually establish.
A factual method before any qualification
The analysis starts with the assignment scope and the material made available: proposals, specifications, code repositories, tickets, environments, backups, logs and acceptance exchanges. Originals should be preserved, access traced, and received documents distinguished from reproducible observations and unverified statements.
Targeted tests can clarify the state of an API, an application, a hosting environment or a migration. Absence of a file in a given environment does not by itself prove that no work was done elsewhere; conversely, a screenshot does not automatically establish that a system is ready for production.
What a usable note should contain
A useful technical note separates chronology, material examined, access limits, findings, uncertainties and remaining questions. It states what can be reproduced and what remains impossible to verify. Conclusions should be proportionate to the quality of the evidence.
An intervention that does not replace the courts
A privately commissioned technical review can inform a company or its lawyer, but it is not automatically a court-appointed expertise. Mahthildis does not issue a legal conclusion on liabilities, nor a guarantee on the outcome of a dispute.
How Mahthildis can help
Paulo Castro can analyse architecture, the application, deliveries, documentation and accessible technical material; run reproducible checks and produce a synthesis of findings with limits and reservations. Access and confidentiality are defined in advance with the authorised parties.
When conflict rises, the priority is to make facts verifiable, not to formulate an accusation more quickly.
About these field situations
These situations combine lessons from Paulo Castro's professional experience. Organisations and operational details are not identified. They illustrate issues and possible approaches, not a claim that all suggested solutions were delivered together or that they are Mahthildis client references.
