Why I made my portfolio an agent, not a document
Why I made my portfolio an agent, not a document
Four moves I made on erpik.com this year — an AI terminal, a labelling cursor, a live presence dot, and a couple of files agents read. Pull back and they all point at the same thing: a portfolio in 2026 should respond, remember, and act.
My old portfolio loaded, showed you my work, sat there.
A reader scrolled, maybe clicked a case study, maybe didn't, left. Same artefact whether they came at 9 a.m. on a Tuesday or 1 a.m. on a Sunday — whether they were a recruiter, a founder, or another engineer just curious. A document.
This year I rebuilt it as something that **acts**.
Four moves. None of them new on their own — all of them quietly converging on the same idea: in 2026, the website that wins is the one that responds, remembers, and *does things*. Not the one that's the prettiest static page.
## 1. The terminal that knows
This page requires JavaScript to view fully. The summary above is for indexing.