SBX — Project Management Hub

01 Problem

A governed SDLC needs a human surface. CLI output is fine for agents but engineers need to browse decisions, walk SDLC tasks, audit traceability, and operate infrastructure without memorising flags.

02 Approach

Strict layered service exposure: SvelteKit `+page.server.ts` loaders call the Go API, never the browser. Brand tokens come from a single YAML compiled to CSS at build time. Components live in shared `@sbx/core-ui` packages and are previewed in a governed component catalogue rather than reinvented per-page.

03 Solution

Built a SvelteKit + Go web workspace that consumes the SBX protocol layer over a Chi-routed API. Renders the SDLC state machine, decision records, knowledge base, entity browser, type registry, component preview, and infrastructure operations (provisioning, migrations, deploys) as first-class views. Everything theme-driven from brand YAML — no hardcoded colours.

04 Outcomes

05 Trade-offs

SSR-only data loading adds a hop versus client fetches but keeps credentials and governance enforcement on the server side. Picked Svelte 5 runes + a single design-token pipeline over a heavier component framework to keep the workspace fast and themeable.

06 Constraints

• SSR-only data loading via +page.server.ts (no client-side data fetches)
• No hardcoded colors — brand YAML is the single source of truth
• Shared components only — no raw HTML primitives in pages
• PR workflow required — never push directly to main

07 Innovation

Visual control panel for an AI-governed SDLC: SDLC tasks with state progression, browsable decision records, knowledge artifact registry, entity/type browser, component preview, and infra operations — all driven by the same protocol layer the CLI uses. Anchored by decisions #0192 (MCP tool separation), #0193 (PR workflow), and #0209 (brand CSS pipeline).