
Selected work / Product Designer & Full-Stack Engineer
PortfolioControlRoom
- Role
- Product Designer & Full-Stack Engineer
- Client
- Personal Platform
- Year
- 2026
The main challenge was turning a portfolio CMS into a safe operational control plane without allowing public clients—or connected AI agents—to inherit administrator trust. Public content, private credentials, operator settings, assistant behavior, and agent permissions therefore…
A private AI-native CMS and secure MCP control plane for operating a living portfolio—content, projects, media, runtime settings, visitor-assistant behavior, scoped agent access, and security operations from one authenticated workspace.




Three decisions shaped the final experience.
03Single-Portfolio CMS
Authenticated editors manage page copy, projects, case studies, media, runtime settings, and publication state while the public portfolio consumes a narrow, presentation-safe content…
OAuth MCP Control Plane
Compatible AI clients can receive carefully scoped read or write capabilities through OAuth. Credentials can be reviewed and revoked, and every supported operation remains constrained by…
Assistant Operations
The dashboard manages the public portfolio assistant without exposing provider credentials to the browser. Published-only context, immutable identity rules, response limits, and safe…
The finished Control Room gives the portfolio one operational center for content, publishing, media, runtime behavior, assistant configuration, security controls, and authenticated agent access. The public site remains presentation-focused, while private operations stay behind authenticated boundaries. AI clients can perform approved work through scoped tools instead of receiving broad database access, and the operator can inspect activity or revoke access from the same interface. This turns the portfolio from a…