A personal operating system

A portfolio is usually a snapshot. I am more interested in building an instrument: a public layer for finished work and an authenticated layer for the unfinished systems that support it.

That private layer can become a small command centre—bringing together notes, project health, experiments, reading queues, and whatever APIs become useful next. The public site and the private portal share a visual language, but they serve different tempos.

The architecture should invite new rooms without demanding a renovation each time. Writing is data today and may become a CMS tomorrow. Small integrations can begin as server-side functions before earning their own service boundaries.

The useful version is not the one with every feature imagined in advance. It is the one with enough structure to absorb the next curiosity.