18 claims · sorted by how you can check them
Don't take my word for it.
A portfolio is a list of claims. This page takes the main ones and says where each comes from: something you can check from your browser right now, something on public record, or work in a private repository that I cannot show you. The third kind is labelled as such.
- Check it nowThis site answers for itself. Press the button or run the command.
- 3
- Public recordA pull request, workflow run or file that anyone can open.
- 10
- PrivateIn a private repository. No link, and I will not pretend there is one. Ask me and I will walk you through it.
- 5
This site
8 claims
The site is the one system here that I can open up completely, so most of what it says about itself can be checked from where you are sitting.
- Check it nowclaimed in: Status
Availability is measured from outside against a 99.9% objective.
The API reads Google Cloud's uptime checks, which request the site every minute from three regions, and returns what they recorded.
curl -s https://portfolio-emsghin2iq-as.a.run.app/api/slo - Check it nowclaimed in: Live status
The commit shown on the page is the commit that is running.
The server reports the commit it was built from. Compare it with the head of the main branch on GitHub.
curl -s https://portfolio-emsghin2iq-as.a.run.app/api/status - Check it nowclaimed in: For agents
The site is an MCP server that an AI agent can call.
Ask the server for its tools. The page for agents has a console that calls each one.
- Public recordclaimed in: How this site ships
52 deploys in the 30 days to 2026-11-12, with a change failure rate of 0%.
Computed by the pipeline from its own run history. Every run is public, and the changelog lists each release with the commits it shipped.
- Public recordclaimed in: How this site ships
A rollback drill in production had traffic back on the previous revision 17 seconds after the switch.
The drill is a workflow run that fails its own live check on purpose and passes only if the rollback then works. Its log has the timestamps.
- Public recordclaimed in: Decisions, ADR 3
Every release is one image, built once, with an SBOM and signed build provenance.
Each GitHub release carries the SBOM and the signature bundles, and the repository lists its attestations.
- Public recordclaimed in: The footer of every page
Accessibility and SEO score 100 on every release.
CI runs Lighthouse on a page of every kind, and on the home and status pages in dark as well, and fails the build if either score drops. The reports are attached to each run.
- Public recordclaimed in: Postmortems
Three things went wrong while building it, and each has a postmortem.
The write-ups cite the commits that caused and fixed each problem. The commits are in the repository's history.
Research and open source
6 claims
Code I wrote in other people's public repositories. The pull requests are the record: what changed, who reviewed it, when it merged.
- Public recordclaimed in: Research
I wrote the Toolathlon adapter for ARIES, the lab's agent-serving framework.
Merged upstream in October 2026.
- Public recordclaimed in: Running an agent benchmark without root
An Apptainer backend runs the whole stack on a supercomputer without root: 6,678 lines across 46 files.
Merged upstream on 10 Nov 2026. The diff has the line and file counts.
- Public recordclaimed in: Research
Portable plugins (skills and MCP servers) that work in both of ARIES's agent harnesses.
Open and in review, not merged. Listed here so the site does not imply otherwise.
- Public recordclaimed in: Research
Co-author of a paper at ICCV 2025.
PVChat: Personalized Video Chat with One-Shot Learning. The code is public and the paper lists its authors.
- Public recordclaimed in: Experience
21 merged pull requests on a robot car's Android controller.
A team repository for NTU's Multidisciplinary Design Project. The pull requests are public.
320 agent runs: MCP tool calls were 2.7% of agent time, 96% of input tokens came from the prefix cache, and four tasks at once gave 3.02x the throughput.
From my final-year project's report and result files, which are in a private repository while the project is still in progress. The write-up gives the method, the models and the hardware.
Work at Primustech
4 claims
This is an employer's production system. Its repository, bills and documents are private, and nothing here links to them. I am saying that plainly rather than dressing it up.
169 of my pull requests merged into a production IoT platform's repository.
Counted from the private repository's pull request history under my GitHub account.
Cloud spend cut by about 15%, including 914 orphaned Kafka topics removed and 40% fewer monitoring samples.
The cost review I wrote for the platform records each cut and its trade-off: 914 orphaned topics removed, 40% fewer samples per scrape, the database and pods resized. The case study gives each move with its before and after.
Three remote-control lanes are measured against one written safety pattern of ten principles, and the bridge that drives them has 431 tests.
The pattern, the tests and the commissioning records are in the private repository. The case study has a working model of the guards.
A network-policy rehearsal found that the obvious rollout closed 28 of the 46 paths meant to close only at cutover, and could not be undone cleanly.
From the rehearsal's own record of each path checked, kept with the change in the private repository.
If something here is wrong
Tell me and I will fix it, and say so in the changelog. The site keeps postmortems for its own mistakes for the same reason. Get in touch.