A live deployment of the BNB architecture managing four coordinated agents — financial, marketing, content, and orchestration — across 22 scheduled jobs. Originally built as the founder's personal system, it's now the reference implementation we deploy variations of for every client engagement.
Below: the architecture, piece by piece, and what it actually looks like running.
It runs on a VPS — a small virtual server in a data center. Always powered. Always online. Nothing fancy; the same kind of machine people use to host a blog.
For deployments with sensitive data or strict residency requirements, the same architecture runs on local servers, on-premise hardware, or air-gapped environments. The agent doesn't care where the computer lives — only that it's always on.
This is the environment where everything else happens. Think of it as the body the agent inhabits.
Not a chatbot. Not always listening (but always available). A scheduled program that starts when it's supposed to, reads its context, makes decisions using an AI model, and writes results to files.
The whole runtime is one command:
A markdown file called CLAUDE.md. The agent reads it at the start of every session — before acting on anything. It contains identity, values, rules, ways of thinking.
This particular agent is 731 lines of investment reasoning encoded as identity. The same pattern applies to any domain — operations, sales, compliance, content. The architecture is the asset; the identity file is what makes it yours.
Agents don't remember yesterday by default. So every run writes its work to shared markdown files — active state, open items, decisions, the last briefing.
Tomorrow's wake-up reads those same files and knows what the world looked like the last time it ran. Memory, simulated.
Five scripts run at 4:30 AM every weekday. They pull from specific sources — internal CRM data, regulatory feeds, public APIs, industry reports, partner integrations. Each writes a markdown file the agent reads during its morning wake-up.
The agent doesn't browse the web in real time. It reads a pre-digested snapshot. Fast. Predictable. Cheap.
When the agent has something worth saying — a briefing, an alert, a question — it sends a Telegram message. The operator reads it on their phone like any other text.
No dashboard to check. No app to open. The agent comes to operators when it matters; otherwise, it's silent.
Cron is a standard feature of every Linux system — it runs programs on a schedule. This system has 22 scheduled jobs across a week: a morning briefing at 6 AM, a market open alert at 6:35 AM, a close review at 1 PM, weekly deep dives on Thursday afternoons.
Predictable. Auditable. Cheap. If something misfires, we know exactly when and why.
At the start of every session, the agent reads these files in order. They define who the agent is, what it knows, and what it's allowed to do. Change the files, change the agent.
The files below are from the live deployment we run for our own operations — configured for financial intelligence. We're showing them as-is because real production files are more credible than abstract examples. Read them at the architecture level: identity, memory, decisions, audit trails, schedule. The financial detail is what proves the system works in production. The pattern is what's portable to logistics, sales, compliance, content, or any domain where a process repeats and decisions follow rules.
Values, judgment, ways of thinking. The first file read at every wake-up. If the agent had a soul, this would be it.
Live positions. Rewritten at every close review so tomorrow's agent knows where it stands.
Thesis for every position. Entry rationale, kill-conditions, what would invalidate it. Read every morning so the agent can grade theses A through F.
Pulled fresh at 4:34 AM daily. Cross-referenced against the watchlist for signal. Refreshed from House Clerk + Senate disclosures.
Quarterly holdings of tracked managers. New positions, increased stakes, full exits. Signals with fiduciary-grade conviction.
Append-only log of every decision. When the agent explored X and chose Y over Z, it's here. Prevents the agent from re-litigating settled questions.
Every tick is a scheduled job firing. Tap any dot to see what happened.
Deterministic shell scripts — not AI. Each pulls from a defined source (CRM, internal database, regulatory feed, public API) and writes a markdown snapshot the agents read later. Pre-digested input means agents make decisions on consistent, version-controlled data.
Tail of the agent status log — real format, unedited.
This system runs autonomously, 24/7, on infrastructure the operator owns. The same pattern adapts to operations agents (logistics, inventory), sales intelligence (pipeline management, lead research), compliance (document processing, regulatory monitoring), and any domain where a process repeats and decisions follow rules.
If you want a system like this for your business, book a discovery call. No pitch. No pressure. We'll look at your operations and tell you honestly whether agents will move the needle.
Book a Discovery Call →