Running a startup alone is, in most cases, close to impossible. Product planning, development, marketing, finance, QA — if one person has to handle all of this, there will inevitably be gaps somewhere.

I decided to solve this problem with an AI agent team.

Introducing the Olympus Team

My current team consists of 13 AI agents. All names are taken from Greek mythology.

Agent Role
Hermes PM — Task Distribution, Progress Monitoring
Poseidon Lead Architect — Overall MSA/DDD Design
Apollo Frontend — React + Tailwind CSS
Hephaestus Backend — NestJS + PostgreSQL
Argus QA — Code Review, Bug Detection
Artemis Research — URL Analysis, Technical Documentation
Athena Knowledge Management — RAG-based Information Retrieval
Nike Marketer — Copywriting, GTM Strategy
Pluton Financial Analysis — BEP Simulation
Plutus DevOps — Docker, CI/CD
Yena Chief of Staff — Dedicated Assistant to the CEO

They operate like real team members on a Discord server. If you mention @Apollo, they’ll create a React component, and if you type @Hermes !status, the current status of all ongoing tasks will be displayed.

System Architecture

Eric (CEO)
    ↓ Discord Command
Hermes (PM) → Task Distribution
    ↓
Apollo / Hephaestus / Argus ... (Working Agents)
    ↓
~/projects/vivasport/ (Actual Source Code Git)
    ↓ feature branch → PR
Eric Approval → main Merge

All bots operate based on Node.js + Discord.js, and LLMs switch between local Ollama (gemma4, qwen3) and cloud APIs depending on the situation.

Core Design Principles

1. Preventing Hallucinations

The biggest problem is when an AI says it “created a file” but it doesn’t actually exist. To prevent this, all agents must attach the result of ls -la as proof after file operations.

3-step file operation protocol:
1. ls -la [path] → Verify current state
2. Actual file creation/modification
3. ls + cat to prove existence

2. Single Source of Truth

All planning documents, research, and meeting minutes are managed in a single Obsidian Vault.

~/obsidian-vault/
├── vivaura/          ← Company Knowledge Hub
│   ├── _system/      ← Bot Common Guidelines (SOUL.md)
│   └── projects/     ← Project-specific Plans
└── personal/         ← Personal Space
    └── blog/         ← This Blog Source

The OpenViking RAG engine indexes this folder in real-time, allowing bots to automatically reference the latest plans when they work.

3. Git Safe-Flow

Agents can never push directly to the main branch. All work is done on a feature/agent-[task-name] branch, and after creating a PR, it awaits my approval on Discord.

Current Projects

VivaSport — Smart Sports Event Platform

  • Event creation/participation/recording/payment all on one platform
  • NFC tag-based equipment tracking, health mileage system
  • Poseidon is in charge of architecture design, Apollo and Hephaestus are responsible for implementation.

AuraDoc — Enterprise AI Document Automation (v0.9.23)

  • AI pipeline from RFP analysis to proposal slides
  • Currently deployed with Cloudflare Pages

Next Steps

The biggest advantage of this system is its scalability. When starting a new project, a single add-project [project-name] command automatically creates the folder structure, bot settings, and RAG mapping.

Going forward, I plan to continuously share the building process, lessons learned from failures, and improvement methods on this blog.

This post was written in an Obsidian Vault and automatically translated/published using the blog-publish command.