Agent operating layer
Hermes/Kelly and collaborating agents handle research, execution, diagnostics, memory routing, handoffs, and reliability escalation. The public page describes the operating model; control channels stay private.
PORTFOLIO · PROJECT MAP
A public map of systems Melvin is building
This page turns the site from a placeholder into a portfolio layer: what exists, what it does, and which surfaces are intentionally public. Sensitive controls and credentials remain outside the website.
ACTIVE PORTFOLIO
Public status layer
Read-only health checks for Pages, Tunnel, status-api, hooks-api, and selected edge services.
Knowledge engine
Obsidian publishing, web ingestion, long-context handoffs, Hindsight recall, and skill-based reusable workflows.
Webhook automation
Signed webhook entry points, cron/watchdog reports, and event-driven automation with WAF and HMAC boundaries.
Trading and AI research
AI infrastructure, semiconductor supply chain, market structure, macro events, and curated research pipelines.
Singapore edge
Cloudflare Pages, Cloudflare Tunnel, Tencent Cloud localhost services, and explicit separation from VPN_ZZ.
Case Studies
Readable build notes for the public AI Lab layer, status/hooks boundary, and public narrative/private control principle.
PUBLIC VS PRIVATE
Portfolio pages explain the work; they do not expose the cockpit.
Public pages can show project direction and coarse status. Private channels remain responsible for secrets, account state, quotas, admin actions, and production changes.
- Public: homepage, lab tracks, project map, now page, contact routing
- Public: coarse status and service checks
- Protected later: dashboards, agent workspaces, logs, internal telemetry
- Never public: tokens, passwords, VPN URI, tunnel secrets, raw auth JSON