Engineering
How I build
Quality engineering as the spine, AI as backstage leverage, and honesty about trust boundaries. Every claim below points at something you can check.
Quality architecture
Test suites built as systems: page objects that own their assertions, fixtures that own lifecycle, and typed API clients over raw calls. The scaffolding is meant to be reused, not rewritten per project.
Proof: AI Quality Toolkit →AI-assisted engineering
Treating an AI agent as one of the contributors, which means the rules it must follow have to be machine-runnable. Guardrails live in CI, not in a document nobody rereads.
Proof: Guardrails belong in code →Testing strategy and Playwright
Layered coverage: fast unit and component tests, then end-to-end journeys that exercise the real path a user takes. When CI goes red across shards, fan out one investigator per shard and synthesise before fixing.
Proof: One investigator per shard →Automation and governance
Claim-safety, consent, and shift-left checks as framework-agnostic packages that gate the build. Risk, data, and trust boundaries get named before code is written, not after a review.
Proof: Archetype Observer →Pragmatic architecture
Choosing the change that earns its cost. Prerendering over a framework rewrite, reuse over new infrastructure, proof before scale.
Proof: Wrapping a public site around a gated app →