// verbosai · public showcase · v1.2
A knowledge operating system built for people who work at the edge of complex systems.
VerbosAI is a personal professional platform — part knowledge base, part portfolio, part tooling library. It captures what practitioners actually know, surfaces connections across domains, and makes accumulated expertise legible to clients, collaborators, and investors.
// the_problem
Technical expertise doesn't compound — it leaks.
A decade of operational depth lives in Slack threads, stale wikis, half-finished runbooks, and the practitioner's own head. When they leave, the expertise leaves with them. When they stay, they re-solve the same problems every quarter.
Generic PKM tools — Notion, Obsidian, Confluence — treat knowledge as storage. They have no model of how a healthcare integration pipeline failure, a homelab network topology, and a career architecture decision share the same underlying pattern.
VerbosAI is built on the premise that cross-domain insight is the product — and that surfacing it automatically is an engineering problem, not a discipline problem.
// the_system
Architecture that enforces good knowledge hygiene.
Every structural choice in VerbosAI is an Architecture Decision Record — reasoned, versioned, and stored in the system it describes. The design favors structural inevitability over discipline.
Every note is tagged with one or more of 12 controlled primitives — a domain-neutral vocabulary that links a healthcare HL7 routing decision to a homelab MQTT pipeline to a career architecture choice. The taxonomy is the cross-domain connection engine.
// live_evidence
This isn't a prototype. It's running production.
VerbosAI has been built, deployed, and iterated in public. Every feature described here is live at verbos.ai — not mocked, not staged.
Notes reference each other with [[wikilink]] syntax — Obsidian-compatible, resolved at build time.
Every note declares its relationships structurally. The graph already exists; the D3 visualization is next.
Plugin: remark-wiki-link · Aliases in frontmatter · Build-time resolution · Zero client JS required
// roadmap
From personal system to distributable product.
Phase 1 proves the architecture works at real scale. Phase 2 adds the graph layer. Phase 3 extends the platform into managed web services for local businesses.
- › Astro 6 content collections with Zod schema validation
- › HMAC-SHA256 password-gated private KB
- › Obsidian-compatible wikilink system with build-time resolution
- › Full CRUD script library with Monaco editor and version history
- › Dark mode with WCAG AAA contrast compliance
- › Copy-to-Obsidian export on all KB notes
- › Private session changelog at /kb/changelog
- › 33 scripts · 59 knowledge base notes · 7 sections · 19 ADRs
- › D3.js force-directed knowledge graph visualization
- › Cross-domain connection surfacing via 12-primitive taxonomy
- › BrainDB wikilink traversal and backlink index
- › KB Homunculus: simultaneous multi-domain tracking
- › Supabase multi-tenant database with RLS isolation
- › Client admin portals for scoped content editing
- › PostGIS-powered local commerce intelligence
- › Vercel cron automation for scheduled operations
Built by someone who traces failures for a living.
The architecture of VerbosAI reflects a decade of operational work in healthcare IT — distributed system diagnosis, HL7 v2 message analysis, Datadog observability, Kafka pipeline debugging, custom Python and Bash tooling. Every design decision is informed by what actually breaks in production.
// get_in_touch
If you're building at the edge of clinical data, let's talk.
VerbosAI is a working system, not a pitch deck. If you want to see the private KB, the full architecture log, or discuss where this goes next — the contact form is live and monitored.