RadOS

RadOS is a single-operator agentic OS. Chris Radicle runs 6 ventures through one Glide app, 21 slash commands, 21 data tables, and 4 external services -- all coordinated by 8 Claude agents, 2 skills, and 1 standalone command. The layers below show how data flows from external world to persistent memory.

                        RadOS System Architecture
                        ========================

  Gmail  Make.com  Claude API  Glide API  Cloudflare  EXTERNAL SERVICES
    |       |          |            |          |        (5 bridges to outside world)
    v       v          v            v
  +-------------------------------------------------+
  |            SLASH COMMANDS (18)                  |  OPERATIONS LAYER
  |   Daily: /briefing /email-monitor /session-*   |  (verbs of the system)
  |   Weekly: /task-review /follow-up /content-*   |
  |   Pipeline: /research > /ingest > /outreach    |
  |   Monthly: /lead-qualify /email-report         |
  +-------------------------------------------------+
          |         |         |         |
          v         v         v         v
  +-------------------------------------------------+
  |              GLIDE TABLES (21)                 |  DATA LAYER
  |   Core: Tasks  Leads  Contacts  Pipeline       |  (single source of truth)
  |   Output: Reports  Content  Invoices           |
  |   Ref: Choices  Connections  Users             |
  |   Life: Health  Learning  Habits  Goals        |
  +-------------------------------------------------+
          |                                 ^
          v                                 |
  +-------------------------------------------------+
  |   VENTURES (6)                                 |  BUSINESS LAYER
  |   RadQode  TaoWild  RadicleBotany              |  (what generates revenue)
  |   RadicleHerbal  RadicleTerra  TradePath       |
  +-------------------------------------------------+
          |
          v
  +-------------------------------------------------+
  |              OS LAYER (7 dirs)                 |  PERSISTENCE LAYER
  |   _Identity/  _Marketing/  _Briefings/         |  (Claude's memory)
  |   _Operations/  _Cache/  _Connections/  _Tasks/|
  +-------------------------------------------------+

Data Sources Map

RadOS Folder

Local file system. Claude reads and writes here every session. The persistent memory layer.

_Identity/ -- who Chris is, brand context

_Marketing/ -- per-venture ICPs, campaigns

_Briefings/ -- daily briefing archive

_Operations/ -- SOPs, runbooks

_Cache/ -- Glide table cache (1h TTL, ~80% API savings)

_Connections/ -- API configs, Glide column keys

_Tasks/ -- active task file

_Sessions/ -- session recap archive

_Visualizers/ -- this Hub + 5 interactive dashboards

MrNature/ -- client project files

.claude/ -- commands, memory, hooks

The persistence layer. Without these directories, every Claude session would start from zero. _Cache/ alone saves ~80% of API calls. _Marketing/ makes outreach personalized instead of generic. _Briefings/ creates an audit trail across all sessions.

System Graph: OS Layer Operations View

Glide App (21 Tables)

Single source of truth for structured data. Replaces CRM, invoicing, content calendar, habit tracking. Accessed via REST API (10K ops/month).

Core: Ventures, Projects, Tasks, Leads, Contacts

Output: Reports, Pipeline, Finance, Content

Comms: Subscribers, Invoices

Planning: Goals, Ideas, Decisions, Automations

Life: Health, Learning, Habits

Ref: Sessions, Connections, Choices, Users

App ID: 1CW7jf1VRWQgQi1lpgvg

21 tables replace 5+ SaaS products. Leads table is the most complex (25+ columns, cache-first protocol). Tasks table is the most actively written. Reports table holds all Claude-generated output. Finance replaces QuickBooks.

System Graph: Tables Funnel (Leads data) Revenue (Finance data)

Notion Workspace

Knowledge base and long-form documentation. Build guides, schemas, and reference material synced from RadOS .md files.

RadOS Hub page -- master index

Build guides -- synced from .md files

Schema docs -- Glide table specifications

Decision log -- architectural decisions

Long-form knowledge layer. Notion holds the documents too large or too structured for flat files. Every .md build guide in RadOS syncs to Notion. Schema documentation lives here alongside the Glide app reference.

System Graph

External Services (5)

Minimal external dependencies. Each service has exactly one job. Cloudflare is the infrastructure layer -- DNS, hosting, and email routing for all 7 domains.

Gmail (MCP) -- read threads, search, surface signals

Make.com -- thin scheduler, 4am email scan trigger

Claude API -- Glide Custom Actions, AI columns

Glide API -- queryTables + mutateTables, cache-first

Cloudflare -- Pages hosting, DNS for 7 domains, email routing

Total: ~$185/mo burn rate (Cloudflare free tier)

5 services, 5 jobs. Gmail is the communication layer. Make.com is a thin scheduler. Claude API powers AI features inside Glide. Glide API is the data bridge. Cloudflare is the infrastructure layer -- hosts the visualizers at rados.pages.dev, manages DNS for all 7 venture domains, and routes chris@[domain] + hello@[domain] email to Gmail. All domains migrated from GoDaddy as of 2026-03-18. Free tier covers everything.

System Graph: External Revenue: Cost Structure Cosmos View

Data Flow Chains

Lead Acquisition Pipeline

The growth engine. Raw prospects flow through research, enrichment, and ingestion into Glide.

/research-leads

command

_Marketing/

reads ICP

/lead-ingest

command

_Cache/

cache-first

Glide API

external

Leads Table

25+ cols

Research reads ICPs from _Marketing/ to target the right prospects. Lead-ingest checks _Cache/ before calling Glide API, saving ~4 API calls per batch.

Funnel View System Graph Cosmos

Outreach > Response > Task Creation

Converts leads into conversations. Monitors Gmail for replies and creates actionable Tasks in Glide.

Leads

table

/outreach-draft

command

/follow-up

command

Gmail

MCP

/email-monitor

4am auto

Tasks

table

Outreach reads lead data + ICP strategy. Follow-up catches stale contacts. Email-monitor watches Gmail at 4am and creates P1/P2 Tasks when responses arrive.

Funnel: Pipeline Ops: Weekly Rhythm

Lead Qualification > Contact > Pipeline

Scores leads, promotes winners to Contacts, creates deals in Pipeline, cleans dead leads.

/lead-qualify

command

Leads

score

Contacts

promote

Pipeline

create deal

Lead-qualify scores every lead based on engagement signals (replies, opens, meetings). Qualified leads promote to Contacts. A deal is created in Pipeline. Dead leads are cleaned.

Funnel: Conversion Revenue: Pipeline

Daily Session Lifecycle

How every work day begins and ends. The bookends that give Claude continuity across sessions.

/session-open

start

/briefing

context

[ WORK ]

session

/session-close

recap

_Briefings/