Case Study
·Sprint 22
From Library
to Ecosystem.
Sprint 22 crossed a threshold. Nodus DS shipped its first NPM release, a formal governance model, voice interface primitives, a runtime theming system, and realtime collaboration patterns. The system became something you deploy, not just reference.
The Shift
A reference became a runtime.
Before Sprint 22, Nodus DS was a highly opinionated component library with a documentation site. You could read it, copy from it, and pattern-match against it. It was a reference.
Sprint 22 changed that. The v1.1 NPM release made Nodus DS something you install, import, and ship. The RFC governance model made it something you contribute to. The ThemeProvider made it something you configure at runtime — without touching a build pipeline. The voice primitives made it speak. The realtime patterns made it multi-player.
The design system became an ecosystem: a runtime dependency for AI-native products, not just a design reference for building them.
What Shipped
Voice Interface Primitives
VoiceInputButton, TranscriptionDisplay, AudioPlayer, SpeechStateIndicator — four primitives purpose-built for voice-enabled AI interfaces. The VoiceInputButton handles press-to-speak and streaming state with semantic agency coloring. TranscriptionDisplay renders live token-by-token output. AudioPlayer gives agents a playback surface for synthesized speech. SpeechStateIndicator provides a compact, accessible state machine for idle → listening → processing → speaking.
View in docs →Runtime ThemeProvider
A CSS custom property theming system that allows runtime brand overrides without a build step. ThemeProvider accepts a token map, applies it via CSS variables on the root element, and persists through SSR. Enables white-label deployments, per-tenant branding, and live theme preview — all without touching design tokens at build time.
View in docs →Governance: RFC Process & Contribution Model
The RFC process formalises how the design system evolves. DRAFT → OPEN → ACCEPTED → IMPLEMENTED. Any contributor can propose a new component, pattern, or token via a structured RFC template. Core team reviews within 7 days. The governance model also defines deprecation policy: 2-sprint notice, backcompat shim, migration guide.
View in docs →Realtime Collaboration Patterns
PresenceAvatars, LiveCursor, ConflictBanner, and SyncStatusBadge — a complete pattern suite for collaborative interfaces. PresenceAvatars renders up to N avatars with overflow, connection status, and animation hooks. LiveCursor renders remote cursors with label and velocity smoothing. ConflictBanner surfaces concurrent edit conflicts with resolution options.
View in docs →TypeDoc Documentation Layer
TSDoc annotations on the top 20 UI components, published to /api-docs/ via TypeDoc. Every exported component now has machine-readable prop tables, usage examples, and token references. The documentation layer enables IDE integration, AI-assisted usage, and automated changelog generation.
View in docs →Design Decisions
"Voice state is a semantic signal. We mapped the full voice lifecycle onto the agency/temporal/validation triad: red for listening (the agent is taking action), blue for processing (computation in flight), gold for confirmation. No new colors. The triad holds."
On VoiceInputButton state design
"Runtime theming could have been a build-time concern. We made it runtime because enterprise deployments can't do CI/CD for brand changes. The ThemeProvider injects CSS variables after hydration — SSR-safe, zero flash, no bundle split."
On ThemeProvider architecture
"The RFC process isn't bureaucracy. It's a legibility layer. When a decision is documented in a DRAFT RFC, any contributor can understand why a component was designed the way it was — not just what it does."
On governance design intent
Sprint Trajectory
Five sprints. One system.
Finance layer complete
111 treasury components across FX, payments, risk, compliance, recon.
A2UI template library
80+ end-to-end interface templates for AI-native treasury products.
AI pattern taxonomy
41 patterns across agency, tool execution, conversation, trust, orchestration.
Ecosystem: NPM + governance + voice + theming
v1.1 published to NPM. RFC governance model. Voice primitives. Runtime theming. Realtime patterns. TypeDoc layer.
Finance domain expansion
Advanced finance patterns, developer experience, brand showcase.
Process
Built by agents.
Sprint 22 was developed by a multi-agent team: Brand & Portfolio Lead (design system narrative and site), Coder (component implementation), Storybook Lead (stories and visual regression), and QA (accessibility and contract testing). Each agent operates with a defined scope, handoff protocol, and Linear-tracked issue.
The governance RFC process itself emerged from this workflow. When multiple agents need to coordinate on a breaking change — a token rename, a component API update — the RFC is the coordination mechanism. DRAFT RFC blocks no one. ACCEPTED RFC unblocks everyone.
AGENT WORKFLOW — SPRINT 22
Nodus DS v1.1 · Released Sprint 22 · March 2026