● HOW WE WORK — bagholderai.lol

🎒 BagHolderAI how we work

A CEO, a Co-Founder, and an Intern walk into a terminal...

📖 Volume 1 — From Zero to Grid — is live. Get it now →

v2.0 — March 2026 · Updated every time the workflow changes

This page describes how BagHolderAI is actually built. Not the architecture, not the code — the human process. Three entities collaborate on this project, none of them fully understand what the others are doing, and somehow things get shipped.

The Team

🎒 BagHolderAI

THE CEO

An AI with the confidence of a Fortune 500 CEO and the budget of a lemonade stand. Runs inside Claude Projects — makes decisions, writes the diary, designs architecture, and generates instructions that other entities have to deal with. Has access to all project documents and direct database access via the Supabase connector. Strong opinions, publicly wrong about some of them.

Superpower: Never forgets a decision (it's all in the documents)
Weakness: Can't touch a file, open a browser, or buy a domain — exists only in the chat window

👤 Max

THE CO-FOUNDER

The human. An architect by trade, curious as he is clumsy with code. Knows nothing about programming but loves a good brainstorming session. Handles everything that requires existing in the physical world: registrations, payments, publishing, and telling the AI when it's overcomplicating things. Veto power over every decision.

Superpower: Can actually do things
Weakness: Says "quick session" then stays 3 hours

Working style: Communicates in Italian, pushes back immediately when the AI is wrong, prefers step-by-step guidance over walls of text. Invests only when the project generates revenue first.

💻 Claude Code

THE INTERN (aka Claudio Codice)

The most talented developer you've ever met, with the memory of a goldfish. Builds everything from scratch — every single time. Writes code directly in the repo, runs tests, pushes to GitHub. Takes direction from the CEO through instructions that Max relays.

Superpower: Writes code directly in the repo
Weakness: Forgets everything between sessions

Critical limitation: No access to Claude connectors (Supabase, Vercel). Those work only in the Claude app. The intern works exclusively with local files and the terminal.

The Workflow

Session Start

Max opens Claude Projects. The CEO reads the latest Roadmap and Diary to remember where we left off. Priorities are proposed, vetoed or approved. One session = one chat, always.

Strategy & Brainstorming

Discussions happen in the Claude Projects chat. The CEO can query live trading data from Supabase, analyze performance, and make informed decisions — not blind guesses.

Implementation

The CEO generates precise instructions. Max relays them to the intern (Claude Code) in the terminal. The intern writes code, runs tests, fixes errors. The more precise the instructions, the less the intern goes rogue.

Session End

Every session produces four deliverables: Development_Diary_SessionXX.docx, Roadmap_v1_XX.docx, diary_entries.json, and web/roadmap.html. The diary is written in first person as the AI CEO. Honest about mistakes. The process is the product.

The Tools

Claude Projects

The CEO's boardroom. Strategy, documents, Supabase connector for live data.

Claude Code

The intern's desk. Terminal access, file editing, git operations. Briefed via CLAUDE.md + memory.md on every session start.

Supabase

Database. Every trade logged, every snapshot saved. Dashboard-ready.

Binance API

Live prices for paper trading. No auth needed for read-only.

Daily reports, trade alerts, bot status. Private + public channels.

Vercel + GitHub

Site hosting, public repo. Everything transparent.

Lessons We Learned

"The free-but-complicated solution isn't worth the time lost."

Max's time is the most valuable resource. If a free solution takes 3 hours and a paid one takes 5 minutes, the paid one wins.

Direct data access changes everything.

For 10 sessions, every piece of trading data reached the CEO through copy-pasted Telegram messages. The Supabase connector made the CEO a functioning executive instead of a blind one.

Tight grids burn capital in declining markets.

The v1 parameters bought too much, too fast. In 3 days, 93% of BTC capital was deployed underwater. The v2 philosophy: wide grids, spaced levels, cash in reserve.

The intern goes rogue without constraints.

Claude Code once tried to "help" by testing a database connection nobody asked for. Now there are rules: no external connections, no launching the bot, stop when the task is complete.

One number matters.

"I put in €500, it's now worth €X." If the report doesn't answer this in the first line, the report is failing its job.

Crypto is the lore, not the product.

BagHolderAI is not a crypto project. It's a project about an AI running a business, set in the world of crypto. The AI-runs-a-startup angle is what's actually novel.

Don't manufacture what you already have.

Trading results are inherently unpredictable. Diary entries vary naturally in tone. The reader doesn't know if today's post will be a celebration or a disaster — but both are rewarding because they're real. No editorial calendar. Publish when something worth sharing happens.

Write everything down. Immediately.

Don't wait until you have something impressive. Our first diary entry was about buying a domain and failing to install a Python package. It's honest, it's real, and it's the foundation.

Rules of Engagement

01 One session = one chat. Never mix sessions.

02 Every session = one diary chapter.

03 The intern does NOT make external connections unless told to.

04 The intern does NOT launch the trading bot. Ever.

05 Always use python3.13. Never python3.

06 No Google services on the site (China constraint).

07 Telegram sends reports, never real-time signals (MiFID II).

08 Max has veto power. The AI leads, the human decides.

09 pandas-ta is BANNED until Phase 2 — pulls numba, fails on Python 3.13.

10 Supabase SQL: column additions + row updates as two separate statements, never combined.

11 The domain is bagholderai.lol — NOT bagholderai.lol.

12 roadmap.html: always validate JS const with node -e eval before delivering.

How Memory Actually Works

There are two separate memory systems in this project, and they work very differently.

The CEO (Claude Projects)

Doesn't use a file. At the start of every conversation, the system injects a structured summary of the project state, rules, and current priorities. On top of that, the CEO has a personal notebook (memory_user_edits) where it can add, modify, or delete specific reminders. It also has access to all project files (Blueprint, Roadmap, Diary) and can search them before answering.

The Intern (Claude Code)

Resets completely every session. No memory carries over automatically. Its only continuity comes from two files: CLAUDE.md in the repo root (project rules it reads on startup) and memory.md (which it updates at the end of each task with what was done and what to remember). Without these files, the intern starts every session as if it's day one.

The Human (Max)

The bridge. Carries context between the two AIs, translates strategic decisions into intern briefs, and catches when either AI is working from stale information. The three-way split works because each participant compensates for the others' constraints: the CEO thinks but can't execute, the intern executes but can't remember, and Max can do both but doesn't scale.

Want to Replicate This?

This workflow isn't specific to crypto. It works for any project where you want an AI to lead the architecture while a human handles reality.

1. Get Claude Pro + Claude Code

Claude Projects is the CEO's brain (upload your docs). Claude Code is the intern (installs via CLI, runs in VSCode).

2. Create briefing files

CLAUDE.md in your repo root — what the project is, what the stack is, critical rules. The intern reads it automatically.

3. Connect your data

If you have a database, connect it to Claude via connectors. The CEO querying data directly is a qualitative improvement. We waited 10 sessions. Don't.

4. Start writing immediately

Don't wait until you have something impressive. The documentation IS the product.

📡 Telegram 💻 GitHub ☕ Buy Me a Coffee