Helmsman

Teams managing deployments, CI/CD pipelines, cluster quotas — and increasingly AI agents and MCP tool servers — had no single place to see state and act on it. The critical question, “what needs my attention right now?”, took far too long to answer.

1. 01

   Designed a deployment orchestration catalog where Applications own Pipelines, Pipelines produce runs and Deployments, and each Application carries its own per-cluster quotas, permissions, and ownership.

2. 02

   Extended the same model from deployed applications to agentic workloads — agents, multi-agent processes, and MCP servers — under one framework-agnostic governance layer.

3. 03

   Made every resource governed by unix-style ugo×rwx permissions on top of an org-scoped RBAC model, with human-in-the-loop approval gates for sensitive actions.

4. 04

   Built cross-service sync with a sibling service catalog: registering agents, subscribing to webhooks, and mirroring a read-only shadow of the upstream catalog.

The product evolved through a clear lineage — an AI-config tool, forked into a deployment catalog codenamed “Coastguard,” then refined into Helmsman. The defining design pass moved it off a generic indigo admin look into a deliberate cyan “ops-console” identity: a grid-lit deeper-dark shell, glowing metric and chart cards, and calm cyan accents. The hard constraint was discipline — restyle through design tokens and layout only, never rewrite the design system, and keep dense data tables perfectly legible. Dark is the star.