How this archive is built.
Each article says what I built, why I chose that route, what I ruled out and where the evidence stops.
Labs evidence.
Every Labs case study points to a public, immutable GitHub commit. Before publication, I check version references, test results and implementation details against that exact snapshot.
The working product page remains the primary project link. The evidence ledger records what I verified and where each claim stops.
Technology comparisons are contextual, not rankings. A choice is explained against the product’s actual constraints and the strongest plausible alternative, including the complexity or limitation it deliberately keeps.
Professional work.
In the professional case studies, I describe engineering work I delivered in employment roles. I withhold company and client names, commercial terms, private repositories and identifying operational data.
I keep the technical sequence, decisions and constraints faithful. I leave out metrics or outcomes that I cannot support without exposing confidential information.
Where implementation details must remain private, I explain the decision boundary without implying access to evidence I cannot publish. The rationale stays specific; confidential identifiers do not.
Corrections.
If a factual detail is wrong or no longer current, email info@ejupilabs.com. I review the source, correct the article and update its verification date.