← ALL WORK

AI + DATA

Agent Private Credit.

Conversational analytics workspace

MY ROLEArchitecture and implementation of the proof of concept
STATUSProof of concept
STACKReact · ACP · K3s · Helm · DuckDB · Rill
FIELD NOTE / 01

See the system in motion.

Architecture walkthrough · 00:10

SBV / AGENT PRIVATE CREDITARCHITECTURE WALKTHROUGH
WHAT THIS SHOWS

The workspace crosses the ACP bridge to agent tools, inspectable analytics and a tenant deployment boundary.

SOURCE / LIMIT

Illustrative sequence based on the proof-of-concept documentation; it is not production footage.

Open video ↗
SYSTEM MODELSELECT A COMPONENT TO EXPLORE →
SELECTED COMPONENTReact workspace

Conversation, chart board, and tool context.

01 / THE PROBLEM

Analysts lose the thread between tools.

Analysts move between conversations, datasets, charts and operational tools, and lose context at every switch.

02 / THE APPROACH

A conversation that brings back its own charts.

A React workspace connects to a Hermes assistant through ACP and brings back the charts and dashboards linked to each conversation. Rill and DuckDB serve the analytical views, and Helm deploys an isolated K3s environment for each client.

03 / THE DECISION

The agent explains. The data answers.

The assistant explains and navigates the analysis, but the numbers come from structured chart outputs and data services that anyone can inspect. Language helps people find the answer. It doesn't produce the figures.

04 / THE OUTCOME

A working proof of concept, and nothing more claimed.

The repository documents a working proof of concept and its deployment design. It hasn't been adopted in production, and no financial impact is claimed.

SOURCES

The proof-of-concept README and its K3s and Helm migration notes. Code and internal links stay private. This page summarizes what those documents show.

NEXT CASE STUDYCloud data systems ↗