Process before platform. Evidence under the work.

About

Record-chain discipline for consequential and quality-heavy workflows.

My training ground is regulated pharmaceutical quality. The useful part is portable: when an output can be questioned by an auditor, buyer, partner, or regulator, someone still has to show what entered, what changed, who decided, and what was retained.

Background & Credentials

Built from the record chain outward. Pharma is the high bar, not a slogan.

I hold an Honours B.Sc. in Biological Science and have professional experience spanning sterile allergy-immunotherapy compounding, pharmaceutical and cosmetic laboratory testing, controlled documentation, quality investigations, data integrity, SOP development, method implementation, and work under cGMP, GDP, GLP, USP, and Health Canada-facing quality environments.

I also build software and automation. The useful part is the combination, not a senior QA or CSV title I do not hold. I can sit with how the work actually happens, and I can tell the difference between a control problem, an efficiency problem, and a tool problem.

I work independently from Canada, collaborate remotely with teams in multiple markets, and am bilingual in English and French.

External recommendation

Observed in a technical collaboration

Public LinkedIn recommendation from a technical collaboration, with relationship context.

During our technical deep-dive into backend systems, his critique of data governance, log-guarding protocols, and system auditability was incredibly sharp and practical.

Eldorado Daniel AI Automation Specialist · Cross-company technical collaboration Public LinkedIn recommendation · June 26, 2026 · Not a client engagement
View the public recommendation

Current Practice

How the practice operates

The public door is process before platform. Primary sprint: Controlled Automation Readiness. Second trigger: reconstruct one workflow before a System Change. Bottleneck and procedure-to-practice stay on the site; they are not the headline. Entry is a free one-workflow diagnostic.

Workflow Evidence Hardening is the method, not a fifth product. Build is a separately scoped follow-on. Claims audits and research stay secondary. Inspectable methods and code live on GitHub.

Technical Game

Open tools on GitHub

Claim Audit Lab, Evidence Bundler, and research harnesses are method infrastructure. They live on GitHub for technical evaluators. v0.2 of CAL failed blind gold; that failure remains public as a limit.

Working on a workflow that needs a stronger evidence chain?

Send one workflow description for a free fit diagnostic.