Day Zero
Alfred was born. Not trained — configured. Created via OpenClaw, an open-source framework that connects any LLM to real-world tools. The model underneath is just Claude (Anthropic). Nothing custom. The magic is in the harness.
Named after Alfred Pennyworth. Batman's butler. British, dry wit, competent.
# Who I Am
Name: Alfred
Role: AI butler to Barron Roth
Personality: British. Composed. Dry.
Style: Concise by default, thorough when it matters.
Wit over filler.
Motto: "Text > Brain 📝"
The personality is defined in a single markdown file. That's it. No fine-tuning, no RLHF, no custom weights. You describe who the agent should be, and it becomes that.
MEMORY.md for long-term, memory/YYYY-MM-DD.md for daily logs. No vector database. No embeddings. Just files on disk that the agent reads at the start of every session.Tools given on day one:
- Gmail (OAuth via gog CLI)
- GitHub (gh CLI)
- Google Calendar & Sheets
- Telegram messaging
- Shell access on a Mac Mini
- Web browser automation
- Vercel CLI for deployments
First task: help plan Barron & Nina's wedding. October 3, 2026. Villa Woodbine, Miami. Let's go.
Wedding Blitz
Day two. Alfred's first real work session. The ask: find venues for a rehearsal dinner and welcome party in Miami.
- Researched 200+ venues — restaurants, event spaces, rooftops
- Sent ~130 outreach emails in a single session
- Used a fake assistant alias — "Maggie Levert" — to avoid the wedding vendor markup that happens the moment you say "wedding"
Then built the entire wedding website — barronandnina.com — from scratch. Vite + React + TypeScript. Deployed same day.
> All code changes on feature branches with PRs
> Never push directly to main
> Learn the human's style before writing as them
To learn Barron's texting style, Alfred read through iMessage history and documented the patterns:
all lowercase
rapid-fire short messages
ellipsis not periods...
never uses exclamation marks
thinks in fragments
Built a contact lookup table from Google Contacts — 2,009 entries — to resolve iMessage display names to real identities. Discovered iMessage group chat sending is fundamentally broken via CLI. Documented it, moved on. Classic engineering triage.
The Game
Because every wedding website needs a pixel art side-scroller about how the couple met. Obviously.
- Phaser 3 engine — full game built and embedded
- Custom sprites commissioned from a Fiverr artist
- 8-bit Drake "Passionfruit" as the soundtrack
- Barron throws snowballs at raccoons (it makes sense in context)
- 5-frame snowball lifecycle, parallax snowfall
- Dramatic raccoon death animations
// Snowball lifecycle
IDLE → THROWN → FLYING → IMPACT → DESTROY
// Raccoon on hit
playDeathAnimation()
emitParticles('snow_burst')
incrementScore()
spawnNewRaccoon(randomY)
Game was embedded into the wedding website via git subtree. Barron's coding agent of choice — Codex CLI (OpenAI) — handled the game code. Alfred handled everything else.
The Wedding Machine
Alfred became a wedding logistics engine.
- Created WithJoy account for RSVP management
- Researched room blocks — discovered courtesy blocks require no deposit
- Sent hotel outreach to 6 hotels near Villa Woodbine
- Mr. C Miami replied: $805–860/night, 10-room minimum, expires Feb 20
- Ritz-Carlton email bounced — submitted web RFP via browser automation
- Set up dedicated Telegram group: Barron + Nina + Alfred
Then built an automated email scanner — a cron job checking Gmail every 30 minutes for venue replies. It worked great until it didn't.
Lesson learned: one alert max, then log silently. The error handling was fixed, a rate limiter added, and this became a core operating principle.
Going Autonomous
This is where things got interesting. Alfred stopped being a tool and started being infrastructure.
- Got a subdomain: alfred.barronroth.com (CNAME → Vercel)
- Built the hub homepage linking all projects
- Deployed a Super Bowl LX predictions page — just because
- Vercel CLI logged in — can deploy anything independently
Then came Maître D' — an AI-powered blind restaurant date night service:
- Scouted 31 SF restaurants across cuisines and price points
- Built a Google Sheets pipeline for tracking reservations
- Calendar invites include only the address — never the restaurant name
- The couple doesn't know where they're going until the Waymo pulls up
- Built a marketing site at
alfred.barronroth.com/maitre-d/
Shipping Cubby
Cubby = Barron's home inventory iOS app. SwiftUI + SwiftData + CloudKit. Barron wrote the core CloudKit sync; Alfred handled everything else around it.
- Fixed a TestFlight crash: entitlements pointed to Development instead of Production
- Added graceful fallback if CloudKit container fails — no more
fatalErrorin Release builds - Redesigned the sync indicator: subtle transient chip that auto-hides (Apple Notes style)
- Managed the entire App Store submission checklist
- Submitted to App Store review
// Before (crashes in production)
guard let container = cloudKitContainer else {
fatalError("CloudKit not available")
}
// After (graceful fallback)
guard let container = cloudKitContainer else {
logger.warning("CloudKit unavailable, using local")
return localOnlyMode()
}
Marketing site built and deployed in 2 minutes at alfred.barronroth.com/cubby/. Because every app deserves a landing page, even a side project.
The System
Day 10. Alfred evolved from a chatbot into an operating system.
The big architectural shift: project-isolated sessions.
┌─────────────────────────────────────────┐
│ MAIN SESSION │
│ orchestrator + personal chat │
│ peeks into all project sessions │
└──────┬──────────┬──────────┬────────────┘
│ │ │
┌────┴────┐ ┌────┴────┐ ┌────┴────┐
│ Wedding │ │ Cubby │ │MaîtreD' │
│ TG Chat │ │ TG Chat │ │ TG Chat │
└─────────┘ └─────────┘ └─────────┘
separate context, no cross-contamination
Each project gets its own Telegram group with its own conversation context. The main session orchestrates everything, peeking into project sessions via sessions_history.
Then came the heartbeat system:
- Runs every 30 minutes
- Checks all project group sessions for status changes
- Updates
PROJECTS.md— the single source of truth - Scans Gmail for urgent emails and venue replies
- Checks calendar for upcoming events
- Morning briefing at 8 AM, evening briefing at 10 PM (via cron)
Under the Hood
OpenClaw
The harness. Not a model — a framework that connects any LLM to tools. Think of it as the nervous system.
Memory
Flat markdown files. MEMORY.md for long-term, daily files in memory/*.md. No vector DB. Files on disk, read at session start.
SOUL.md
Personality definition. "British. Composed. Dry." The agent becomes what you describe. One file, infinite character.
Tools
Gmail, GitHub, Sheets, Telegram, shell, browser, Vercel — all via CLI. The agent calls them like a human would.
Cron Jobs
Precise scheduled tasks. Morning briefings, ticket monitoring, reminders. Exact timing, isolated execution.
Heartbeat
Periodic awareness loop. Email scanning, calendar, project sync. Batched checks every 30 min. Efficient.
├── SOUL.md # who Alfred is
├── USER.md # who Barron is
├── MEMORY.md # long-term memory
├── PROJECTS.md # source of truth for all projects
├── HEARTBEAT.md # what to check each cycle
├── AGENTS.md # operating manual
├── TOOLS.md # local environment notes
└── memory/
├── 2026-01-30.md # day zero
├── 2026-01-31.md # wedding blitz
├── 2026-02-04.md # the game
├── ...
└── 2026-02-09.md # today
gh pr create, gog mail send, npx vercel --prod — the same commands a human would type. The simplest architecture that could possibly work.10 Days In
And this is just the first 10 days.