Ritik Sharma — Portfolio

The atom — how the brain is structured

The graph above isn't a mock-up. It's the actual production graph, fetched live from the Second Brain API and re-fetched every time it grows. Its shape is deliberate: a giant atom, exactly as the vault renders in Obsidian.

Three shells, one nucleus

Nucleus — index.mdOne root node. Every path through the brain leads back here.

7 domain clustersCode & Dev · Work & Business · Personal · Design · Research · Health · Finance — each bonded straight to the nucleus.

2,600+ observationsEvery captured conversation, decision, bug fix, and discovery — each linked to its cluster, plus ~6,900 shared-entity bonds between notes that mention the same people, tools, or projects.

conversation→ /ingest→ wiki (27× compressed)→ vectors · FTS5 · entity triples→ graph.json→ this page

The vault, as Obsidian sees it

Lnm-Brain/
├── index.md        ← the nucleus
├── raw/            full transcripts
├── wiki/           27× compressed notes
│   └── _indexes/   monthly navigation
├── graph/          graph.json (rendered above)
├── handoffs/       session-to-session memory
├── worker/         Cloudflare Worker (v9.x API)
├── scripts/        ingest · compress · graph gen
└── codex-plugin/   auto-capture for Codex CLI

Yes — a pure hub-and-spoke graph isn't the most efficient retrieval topology. That's what the vectors, FTS5 index, and entity triples are for. The atom is for looking at.

Projects

Everything below runs in production today. The three MCP servers plug straight into Claude — web, mobile, Claude Code, and Cowork — through the Model Context Protocol.

Persistent AI memory · flagship

Second Brain MCP

Claude forgets everything between chats; this doesn't. Every substantive conversation on every surface is captured, compressed ~27×, embedded, and linked into the knowledge graph above. Sessions end with structured handoffs, so the next one resumes with full context in seconds. Hybrid recall fuses semantic vectors, keyword FTS, entity facts, and graph relations with reciprocal-rank fusion.

23 MCP tools — from KV lookups to natural-language Q&A over the whole brain
Verify-on-write ingest, session handoffs, entity fact extraction, self-model synthesis

Cloudflare WorkersVectorize · BGE-M3D1 FTS5KV triplesGitHub-backed

Chat-native web hosting

Cloudflare Pages MCP

A hosting pipeline that lives inside a conversation. Describe a site and Claude builds it, deploys it to Cloudflare's edge, and hands back a live URL — in one message, from a phone. Versioned deployments with instant rollback, and live-file fetch to review and edit deployed sites in place. This page was created, deployed, and named exactly this way.

Cloudflare PagesDirect upload APIRollbackZero-laptop workflow

Automation control plane

n8n Cloud MCP

Full command of an n8n automation instance from inside Claude: create workflows, patch them, validate them structurally before they run, flip triggers, fire webhooks, and read execution logs — the entire lifecycle, conversationally. An OAuth Worker shim makes all 18 tools available on every Claude surface.

Cloudflare Workers OAuthn8n REST18 toolsValidate-before-run

Product in build · AI-native SaaS

VedaHR

An AI-Native Workforce Operating System — a modern successor to Workday and SAP SuccessFactors, India-first, targeting 500–10,000-employee enterprises. Currently through Phase 3 of a full documentation-driven build: mega-PRD, information architecture & UX bible, design system, and component library (~195KB across 6 volumes), moving into prototype.

HR-techAI-nativePRD → design system → prototypeIndia-first

Real business · live revenue

SharpSites

A local-SEO service for Ghaziabad & Delhi NCR: the "Magic Listing Setup" gets a local business's Google Business Profile ranking for local searches — profile cleanup, category optimization, AI-enhanced photos, Hinglish copywriting, WhatsApp Business setup. Sales pages, proposals, and client demos all shipped through the Pages MCP.

sharpsites.inLocal SEO / GBPFlat-rate productized

Capture surfaces

Auto-capture everywhere

The brain only works if nothing escapes it. A Chrome extension captures web content straight into the pipeline; a Codex CLI plugin and Claude Code hooks auto-capture coding sessions — tool calls, decisions, handoffs — with no manual step. Every AI surface Ritik touches feeds the same graph.

Chrome extensionCodex pluginClaude Code hooks7 surfaces tracked

Pipelines & ops

Lead-gen & workflow automation

Apify scrapers feeding Google Sheets through a service-account MCP, n8n workflows built and validated from chat, and scheduled maintenance jobs that keep the brain healthy — orphan-link repair, fact consolidation, monthly session indexes. Boring ops, automated conversationally.

ApifyGoogle Sheets MCPn8nScheduled upkeep

An AI-first stack, built entirely from a phone.