The tools, layer by layer — every line backed by a public repo you can open.
AI / MLDeep-learning agent with a daily retraining loop (trading pipeline) · RAG over PostgreSQL + pgvector embeddings with source citations · multi-stage document ingest with extractor → verifier agent chains · tool-using agents on the Vercel AI SDK (knowledge search, calendar, human escalation) → MORDOMO, trading agent
ML RigorPurged & embargoed walk-forward cross-validation for overlapping-label time series — look-ahead bias and label-leakage control, uniqueness weighting; NumPy-only, scikit-learn-compatible API → purged-walkforward
LanguagesPython for ML and systems tooling · TypeScript end-to-end for product code
Backend / DataPostgreSQL (+ pgvector) · Drizzle ORM · Next.js server routes · Zod-validated typed configs → MORDOMO, ChurchChatBox, landing-page-cav
FrontendNext.js 16 · React 19 · SEO & WCAG accessibility · dependency-free motion design in vanilla JS/CSS → landing-page-cav, this site
Agentic Eng.Claude Code as engineering partner — spec → persistent .md context files → plan-first build → headless-browser visual QA on every iteration → every repo above
Ops / SRECross-platform service monitoring with self-healing restarts and a dead-man's switch — a dead machine still raises an alarm → service-watchdog
rafael@pipeline: ~ $ cat METHOD.md
01 SPEC — define the mission like an operator: scope, constraints, definition of done
02 CONTEXT — engineer persistent .md knowledge files so every session starts fully briefed
03 BUILD — pair with Claude Code: plan first, generate, review every change
04 VERIFY — tests, screenshots, metrics — ship only what survives inspection
▸ edge: 10+ years inside administration, operations & financial operations.
▸ I don't build AI for demos — I build it for domains I've actually run.
$