Lee & Sumit: Claude Code Deep-Dive, Credential Vault Architecture & HC Protocol Vision

Feb 13, 2026 128 min Jason, Lee Gunderson, Sumit
Jason demos Claude Code folder-based workflows to Lee. Team dev sprint updates. Three architecture decisions: credential vault goes universal/multi-tenant, HC Protocol is "Web 4.5" (pages as AI knowledge base, registries as routers), voice agent needs embeddable standalone widget. Also covers N8N → microservice conversion, Forge VPS architecture, and MasteryMade auth layer.
Lee Deep-Dive
8
Decisions
7
Action Items
3
Blockers

Team Dev Sprint Updates

Rahul — Generic Questions Feature

Working on generic question handling. Jason asked for demo next session.

Rohit — WebRTC Voice Agent Bugs

WebRTC implementation has connection bugs. Investigating intermittent drops.

  • WebRTC is primary transport, WebSocket is fallback
  • Need production-ready voice agent by next sprint

Mukesh — Google + Notion MCP Integration

Building MCP connectors for Google services and Notion. Next up: MetaMCP (unified MCP gateway).

  • Google Drive connector for shared company folders
  • Notion workspace integration via MCP
  • MetaMCP will unify multiple MCPs behind a single endpoint

Ashwani — Knowledge File Extension

Expanding supported file types for the knowledge base upload system. Currently text-focused, adding document and image support.

Vinay — QA

Continuing QA across existing features. Regression testing after recent voice agent changes.

Key Discussions

Claude Code Demo for Lee

Jason walked Lee through the complete Claude Code folder-based workflow system:

  • Folder structure as project context — CLAUDE.md files, golden templates, processed/ folders
  • Meeting transcript processing: drop .txt → Claude detects type → generates HC page → publishes
  • Ralph Wiggum loops: spin up Claude sessions, write to memory/log files, grab PRDs, auto-continue
  • Slash commands for common operations (publish, update, etc.)
  • Self-improving system: "When it doesn't publish right, I tell it to fix its own publisher"
"The stuff builds itself. Now I just tell Claude Code to use what you built to publish. And when it doesn't do it right, I say go fix your publisher." — Jason

Credential Vault — Universal Architecture

Critical architecture decision: the credential vault cannot be per-app silos. Must be multi-tenant with API/MCP exposure.

  • Current state: each app manages its own credentials separately
  • Target: one vault (Supabase + AWS KMS), all microservices consume via MCP/API
  • MasteryMade authentication layer gates access — authenticate through "us" not Google/GitHub
  • Every new microservice (voice agent, knowledge base, etc.) plugs into the same vault
  • Lee acknowledged the multi-tenant architecture approach
┌─────────────────┐ │ MasteryMade │ │ Auth Layer │ ← JWT/token gating ├─────────────────┤ │ Credential │ │ Vault (Supabase │ ← Universal, multi-tenant │ + AWS KMS) │ ├─────────────────┤ │ MCP / API │ ← Exposed to all services ├──┬──┬──┬──┬─────┤ │VA│KB│N8N│HC│... │ ← Microservices consume

HC Protocol Vision — "Web 4.5"

Jason explained the full HC Protocol concept to Sumit and Lee for the first time:

  • Pages as AI knowledge base — use the internet instead of RAG/Supabase
  • Hidden instructions block tells AI agents how to consume the page
  • Hidden structured data (hc-context-public) provides machine-readable facts
  • Neural registry = dynamic router for AI agents to discover all context
  • Meta-dashboard will unify EODs, meetings, and project intelligence
  • Embedded agents on pages will use the page + registry as knowledge base
  • Private pages gated behind JWTs for internal/sensitive content
"Instead of having to go to the Supabase, it uses the HTML. The web pages are the knowledge base." — Jason

Voice Agent UX — Embedded vs Chat-Adjacent

  • ChatGPT-style: voice integrated into existing chat window
  • 11 Labs-style: standalone embeddable widget on any webpage
  • Decision: need both — chat-adjacent for platform, standalone for HC pages
  • Resource library pages should have voice/chat agents, but gated behind plan tiers (expensive tokens)
  • Sumit confirmed: chat window slides up on click, voice agent embedded alongside

N8N → Standalone Microservice Conversion

Concept: take working N8N workflow JSONs and convert them to standalone apps.

  • Working N8N JSON = proven logic, just needs a runtime wrapper
  • Feed JSON to Claude Code: "build this as a standalone service, but also do X, Y, Z"
  • QR code generator example: took someone else's working code, extended with custom features
  • Goal: productize this pattern with guardrails (not "loosey-goosey")

Executive Assistant Concept

Jason's vision for personal AI productivity stack:

  • Obsidian as the note-taking / thought-capture layer
  • Claude Code as the execution engine (folder-based memory, PRDs, slash commands)
  • Forge on VPS as the 24/7 autonomous agent (Telegram interface, heartbeat, voice)
  • Intelligence dashboards aggregate EODs, meetings, and project data
  • Meta-dashboard synthesizes everything into "what's going on in my whole life"
  • Obsidian MCP will bridge note-taking with agentic execution

Jason's Dev Workflow Pattern

Shared process for going from idea to shipped feature:

  • Step 1: Gemini Deep Research — "find me how people are doing X"
  • Step 2: GSD (Getting Stuff Done) session — negotiate scope back and forth
  • Step 3: Build PRD in Claude chat with research context
  • Step 4: Share PRD with Claude Code CLI — execute and iterate
  • Step 5: Claude Code fixes its own tools as you use them

Decisions

Credential vault must be universal/multi-tenant — not per-app silos

Credential vault needs MCP/API exposure for all microservices

HC Protocol pages replace traditional RAG — use the internet as the knowledge base

Voice agent should be embeddable as standalone widget, not just chat-adjacent

N8N workflows can be converted to standalone microservices via JSON extraction

MasteryMade auth will gate internal/sensitive HC pages behind JWTs

MetaMCP is Mukesh's next priority after Google/Notion MCP

Obsidian MCP is priority after credential vault + MetaMCP

Action Items

Build production-ready voice agent (WebRTC + WebSocket fallback)Sumit Team
Complete knowledge file support for more file typesAshwani
Build MetaMCP integration (Google + Notion MCPs unified)Mukesh
Make credential vault universal/multi-tenant with API exposureLee
Get OpenClaw clone working on local machineJason
Build Intelligence Dashboard (dirty version) for Lee/SumitJason
Research Obsidian MCP for executive assistant workflowMukesh

Blockers

WebRTC bugs in voice agent — Rohit investigating connection drops

Credential vault currently per-app — needs universal architecture redesign before new services can integrate

Claude Code token gates — $200/mo plan has 5-hour rolling windows + weekly caps, limiting 24/7 autonomous operation

Claude Code Pricing Analysis

Plan Comparison (shared with Sumit)

  • $20/mo: Basic, runs out of tokens quickly with agentic use
  • $100/mo: Sweet spot — 5x tokens vs basic, good for active development
  • $200/mo: 20x tokens — "a deal" for 24/7 programming, "too much" for casual chat
  • Consideration: two $100 accounts may beat one $200 due to independent rate limits
  • Jason: "Think of it as hiring one more guy for $200/month"