GMAN:…·paisamaker:…·gex-advisor:POLLING·fetcher:429 req/30s·npm:v0.1.8 (9rel)

Uday Kumar

Senior engineer building observable AI agents and production data systems.

@gman-ai/dev on npmLive tracesProduction AI/data platform
system.info/etc/uday.conf
services:
[gman]·[trading]·[social-agent]
production:
[uptime]·data + AI platform
contact:
[click to copy]·github·linkedin
stack:
Python · TypeScript · Postgres · Azure OpenAI · Anthropic SDK · Databricks · Next.js · FastAPI · Docker[+ full stack]
languages:Python · TypeScript · Java · Go · Rust · SQL · Bash · Scala
ai / llm:Anthropic · OpenAI · Azure OpenAI · Mistral · DeepSeek · RAG · function-calling · embeddings · semantic search · anomaly detection · time-series · PyTorch · scikit-learn · Hugging Face · vLLM · Ollama · llama.cpp · LangChain · LangGraph · Claude Agent SDK · OpenAI Agents SDK · MCP · pgvector · evals · fine-tuning
data:Postgres · MySQL · Snowflake · Databricks · BigQuery · ClickHouse · DuckDB · Spark · Kafka · Flink · dbt · Airflow · Dagster · Iceberg · Delta Lake · Redis · DynamoDB
web / app:Next.js · React · Tailwind · FastAPI · Node · Express · Spring Boot · Django · GraphQL · gRPC
infra / cloud:AWS · GCP · Azure · Docker · Kubernetes · Helm · Terraform · Pulumi · GitHub Actions · ArgoCD · Cloudflare · Vercel · systemd · nginx
observability:Langfuse · LangSmith · Helicone · Phoenix (Arize) · Datadog · Grafana · Prometheus · OpenTelemetry · Sentry · Honeycomb · Healthchecks.io · GMAN (own product)
[resume.pdf ↓][portfolio.pdf ↓]
── thesis ─ how it ties together
about.md/etc/about.md
platform:
GMAN captures LLM calls, retries, latency, and cost through a published SDK.
substrate:
Trading systems generate real operational traffic: warehouse, signal evaluator, executor, safety gates.
loop:
Social-agent turns repo activity into human-approved posts; GMAN traces the agent doing it.
── services ─ case files
svc-gman[OPERATIONAL]uptime 99.91%

getmyagentnow.com · multi-tenant telemetry platform for AI-native systems

provider-neutral · npm SDK · self-observing

what:
multi-tenant telemetry for AI agents; published npm SDK, live public demo
hard:
tenant isolation on shared ingest; a public demo that leaks no prompts
proof:
its own commit-reviewer agent runs through the same SDK you'd install
@gman-ai/dev v0.1.8·47 API routes·provider-neutral
inspect: architecture →
svc-trading[TRADING]uptime 100%

trading systems · 0DTE options + gamma advisory

paisamaker + gex-advisor + market-data-fetcher

what:
0DTE options pipeline on one box: warehouse, signal evaluator, executor
boundary:
no LLM in the order path; file-mount IPC, single-writer
proof:
day counter live in the ticker above
8 tickers·104 GB warehouse·20+ safety gates
inspect: trading systems →
svc-social-agent[RUNNING]uptime 30d

social-agent · autonomous content pipeline

cron 3x/day · scoring → drafting → Discord approval

what:
cron agent that reviews commits across 8 repos and drafts posts
boundary:
nothing posts without Discord human approval; silence is auditable
proof:
every run traced in the public demo
84 runs / 30d·20 tweets posted·$0.29 / 30d
inspect: live traces →@gman_ai on X →
── topology ─ data flow

Two lanes: market data becomes orders with no LLM in the execution path; GMAN watches the agents in the second lane.

── trading pipeline ── 30s cycleGEXBotWS onlysvc-fetcher[WS-ONLY]104 GB warehouse11.4 M rows~487k / RTH daysvc-advisor[POLLING]73 features / tick20,979 alertsCASCADE+CHARM 63%svc-paisamaker[LIVE]163 positions40 closed · 38d20+ safety gatesIBKRport 4002── observability plane ── self-instrumentedsvc-social-agent[CRON 3x/d]GitHub Actions8 repos · gpt-4o81/84 success 30dspawn(npx)svc-sdk-proxy[LOCAL :9000]@gman-ai/dev v0.1.8byte-for-byteOPENAI_BASE_URLtelemetry · X-GMAN-Stepsvc-gman-gw[LIVE 293ms]Express · Railway100 req/min/IP414 eventscockpit+ /demo── lanes share infra (Hetzner VM · Vercel · Railway) — separate trust domainscross-process coupling: read-only file-mount, single-writer (no message bus, no socket, no HTTP server in the trading lane)

● operational ● degraded ● down — pulses tick at the actual poll cadence (30s trading, ~6s for the social-agent SDK→gateway hop during a run)

── incidents ─ public postmortems
/var/log/incidents.log3 entries
  • impact
    getmyagentnow.com/demo showed "no recent agent activity" for ~4 hours while Supabase held 79 valid events in the demo tenant. Portfolio link shared in a job application during the window.
    root cause
    Supabase PostgREST was caching query results at its edge. The Vercel function made identical queries (same table, same tenant filter, same ORDER BY / LIMIT). PostgREST served stale empty rows even after new events landed. Local dev hit a fresh connection per restart and never reproduced.
    resolution
    Added Cache-Control: no-cache header on a demo-scoped Supabase client. Kept the shared getSupabaseAdmin() singleton cache-enabled for cockpit and policy routes. Also removed an overly-aggressive AbortSignal(3s) that was silently returning empty on Vercel cold starts.
    prevention
    Centralized isDemoEligible predicate so aggregate stats query and session list filtering always agree on what counts as a real event.
── design notes ─ engineering docs
~/design-notes/1 published
── activity ─ recent commits
$ tail -f /var/log/git.log — loading…
── eof ─