Products & agents
Each row is a shipping capability—what customers or partners touch—with how it runs underneath (Linux services, process supervisor, or serverless). Naming matches the internal resilience matrix without exposing infrastructure coordinates.
| # | Agent | Role (business + ops) | Runtime | Status |
|---|---|---|---|---|
| 01 | EspaLuz WhatsApp | Channel: Spanish tutoring on WhatsApp—conversation, drills, corrections. Runs as a managed Linux service ( espaluz-whatsapp) with automated health checks. |
systemd | ● Live |
| 02 | EspaLuz Telegram | Channel: Same tutoring product on Telegram. Two-layer memory: retrieval + pgvector RAG ( espaluz_rag.py). Service espaluz-familybot. |
systemd | ● Live |
| 03 | EspaLuz Influencer | Brand: Instagram publishing on a disciplined schedule; can spotlight real shipping milestones in consumer-friendly copy. Groq captions + Make.com media handoff. Unit espaluz-influencer. |
systemd | ● Live |
| 04 | Algom Alpha (@reviceva) | Growth: Always-on X presence (education + narrative); folds major releases into the timeline without sounding like raw developer logs. Stream sampling, engagement runner, and account-activity hooks coordinated with the CTO bot for alerts / follow-back. PM2 workers include dragontrade-main and satellite processes. |
PM2 | ● Live |
| 05 | VibeJob Hunter | Product: Autonomous job hunt pipeline—evaluation harness, routing, ATS integrations. Shares codebase with the marketing co-founder agent. Worker vibejobhunter. |
systemd | ● Live |
| 06 | AI Marketing Co-Founder (CMO AIPA) | Revenue narrative: LinkedIn cadence, long-form syndication, CRM hygiene—turns engineering momentum into market-facing proof. Claude + connectors for social; Hunter.io enrichment → HubSpot. Paired FastAPI bridge vibejobhunter-web exposes an internal health route. |
systemd | ● Live |
| 07 | OpenClaw Vibejob Shortlist | UX: Curated job shortlists delivered inside Telegram. Standalone gateway service openclaw-gateway; probed via private health URL on the app host. |
systemd | ● Live |
| 08 | Tech Co-Founder (CTO AIPA) | Control tower: Watches repositories, scores riskier changes, broadcasts milestones to marketing, runs outreach/board workflows. Express orchestrator under PM2 ( cto-aipa), Oracle Autonomous DB via wallet-based TLS—credentials never live in this HTML. |
PM2 | ● Live |
| 08.1 | Sprint Briefing (Sprinter) | Founder ritual: Daily audio briefing synthesized from tasks, notes, and captures. AWS Lambda on a schedule; pulls context through the CTO service over HTTPS with shared-secret auth—no database wallet inside Lambda. |
Lambda | ● Live |
| 09 | Creative Co-Founder (Atuona CCF) | Creative partner: Separate bot persona + public studio site—same reliability envelope as the CTO stack. Single PM2 orchestrator binary; site ships via static edge hosting. |
PM2 | ● Live |
| 10 | Atlas Shifted (Marketing Strategist) | Marketing intelligence: Watches the public ad market daily, detects which creative angle is opening before it saturates (ENTER / WATCH / AVOID), then generates the evidence-grounded creative—image + video via the Atuona pipeline. Feeds the marketing engine (dogfooded on the EspaLuz expat vertical). Capture-first immutable JSONL log + OpenAI-embedding angle classifier + SQLite projection; off-VM daily backup. PM2 ( whitespace:8095) + Panama-time cron. Public ad-transparency data only—no spend/CTR claimed. |
PM2 | ● Live |
| 11 | AILA | Roadmap: Long-horizon personal orchestration—documented architecture, not yet a standalone production process. Interim coordination fields live in Oracle until AILA ships. |
— | In design |
Reliability & uptime practice
For founders: scheduled probes ask each product whether it still responds. For engineers: one bash driver on the primary Oracle VM runs roughly every five minutes; keep-alive traffic avoids idle reclamation; systemd caps restart storms.
pm2 jlist status onlineGo-to-market automation
When engineering ships something worth talking about, the stack fans it out across LinkedIn, blogs, X, and Instagram—without a human retyping the same story five times.
feat:, launch:, or release: notify the marketing agent. Housekeeping commits (fix:, docs:, chore:, …) stay invisible to customers.Commit detected → CTO AIPA
Push events hit the secured webhook. Groq/Claude review diffs, classify milestones, enqueue pending updates for downstream marketers.
CMO generates + posts
Claude Sonnet copy → Make.com delivery. Zero manual paste.
Bilingual blog publish (EN/ES)
The daily blog publisher ships articles to aideazz.xyz/blog with dev.to crosspost (“Also on Dev.to”). Sliding-window mutex, title dedup, and always-notify Telegram guard against silent double publishes.
Algom Alpha tweet
x-tech-updater.js merges milestones in plain language (Haiku / Groq), guarded against duplicate queue states.
EspaLuz Influencer
Milestone-aware caption + Make.com media pipeline; falls back to standard queue when nothing pending.
Release discipline
Board-friendly translation: we ship like a product company—predictable processes, isolated secrets, verifiable rollouts—even though agents move faster than most teams.
One live checkout per codebase
Eliminates “which folder is prod?” debates; paired bots share code intentionally but never duplicate repos.
Green build, then swap
Pull latest → compile/tests succeed → only then restart supervised processes. Broken artifacts never replace what customers already rely on.
Secrets isolation
Each bot owns its environment file; crypto wallets never touch GitHub; TypeScript strict mode catches sloppy typings before prod.
Crash-proof process registry
Every agent process is registered to auto-start on server boot and auto-restart on failure—no manual babysitting after a power cycle or kernel update.
No silent failures
Crash handlers log before exit so supervisors show why something died; watchdog cadence targets ~5 minute detection.
Verify after deploy
Health signal green, database connectivity logs clean, one real Telegram interaction—all pass before the incident is closed.
Incident response template
For stakeholders: regressions are handled like financial reconciliations—symptoms, compounded causes, fix, proof—so the same automation trap rarely strikes twice.
HubSpot duplicate posting loop
May 10, 2026 — same milestone tweet emitted twice ~6 minutes apart
x-tech-updater.js cycle.posted vs filter on posted_x; mark endpoint keyed on timestamp while older rows used received_at; backlog needed posted_x backfill.
{"ok": true, "pending": [], "total": 0, "held": true} + two full automation cycles without duplication.The engagement loop that never ran
May 25, 2026 — config said “32 engagements/day”; logs said zero cycles had ever completed
grep never matched PM2’s box-drawing table output—so it judged a healthy process dead, forever.pm2 jlist | jq on the process status field instead of grepping rendered text. Process stayed up; the first engagement cycle in the bot’s history fired the same day, with real replies and follows verified from logs.Stack reference
Boring reliability primitives where uptime matters; sharp AI + CRM + social APIs where differentiation matters.