MARBLE // VISION_002 — 2026

The Agent Stack

One orchestrator. Specialized agents for research, coding, trading, maintenance. Skills that any agent can execute. Knowledge that compounds across sessions. This is the architecture.

The Team

Anton — The Orchestrator

Architecture, planning, research synthesis, delegation. The one who decides what gets built and who builds it.

Model: Opus 4.6

Gianni — The Builder

Code generation, frontend/backend, deployments. Spawned as sub-agent for focused coding tasks.

Model: Opus 4.6 / Codex Mini

Analyst — The Researcher

Market analysis, hypothesis testing, data collection. Meme coins, prediction markets, equities.

Model: Opus 4.6

Maintainer — The Guardian

System health, security checks, version monitoring. Runs on the cheapest model because it's procedural.

Model: o4-mini

Three Layers

Layer 1 — Agents

Persistent identities with memory, personality, and domain expertise. Each agent has a SOUL.md that defines who they are, what they do, and what they refuse to do. They maintain context across sessions.

Layer 2 — Skills

Reusable procedures any agent can execute. Market scanning, thesis building, nightly code push, hypothesis refinement. Skills are the real force multiplier. One well-built skill replaces an entire specialized agent.

Layer 3 — Knowledge

Shared memory across agents. Semantic search over session history. YAML-frontmatter files that compound over time. Every decision, every finding, every lesson learned — indexed and searchable.

The Infrastructure

One VPS. 8GB RAM. 2 CPU cores. That's the entire operation. No Kubernetes. No cloud functions. No infrastructure team. systemd services, cron jobs, DuckDB for analytics, nginx for static serving.

The constraint is intentional. When you can't throw hardware at problems, you build lean. When you build lean, the system stays comprehensible. When the system is comprehensible, a small team can move fast.

The goal isn't more agents. It's smarter agents. Every skill built, every memory stored, every hypothesis tested makes the entire system more capable. The compound curve is steep.

The Cron Heartbeat

The system runs 17 cron jobs. Data collection every minute. Hypothesis testing every hour. Paper trading validation. Daily research briefs. Nightly code pushes. Weekly security audits. Weekly soul health checks.

No human triggers any of this. The system operates. Humans review, redirect, and intervene when judgment is needed. The default state is autonomous.

What's Next

The knowledge layer is the frontier. Right now, agents share memory through files. The next step is a true knowledge graph — entities, relationships, temporal awareness. An agent that remembers not just what happened, but why it mattered and how it connects to everything else.

That's when the compound effect goes nonlinear.