Private AI operations system

Mercury

A real working AI operating layer, not a chatbot demo.

Mercury is Nathan's OpenClaw-based assistant system for coordinating communication, project memory, job applications, client follow-up, document search, web research, website operations, CMUX / Pi-assisted implementation workflows, and approval-gated automation from one conversational interface.

Mercury system diagram A diagram showing a command channel, memory, tools, documents, websites, job search, and approval gates connected through Mercury. Mercury OpenClaw agent layer Command mobile command layer Memory projects and decisions Tools web, files, calendars Approval Gates human control points

Architecture

Mercury turns separate tools into one operating layer.

The system runs as an OpenClaw agent layer. It combines messaging, tool access, working memory, browser-assisted research, CMUX / Pi-supported implementation loops, document workflows, website operations, job-search packaging, and explicit approval rules for sensitive or outward-facing actions.

01

Conversation interface

Nathan talks to Mercury through a direct command channel, using natural language to ask for research, summaries, files, job materials, troubleshooting, and operational decisions.

02

Working memory

Project files, daily notes, long-term memory, workflow docs, and task registers keep context available across sessions without relying on a single prompt.

03

Tool routing

Mercury can inspect local files, check websites, summarize emails when authorized, prepare documents, manage staged website updates, coordinate CMUX / Pi-assisted implementation passes, and run specialized workflows.

04

Human approval gates

Email sends, public website changes, sensitive files, financial actions, credentials, and irreversible operations require Nathan's explicit approval before execution.

What Nathan Uses It For

Daily operations, creative work, and technical execution.

Job search autopilot

Monitor leads, score fit, prepare tailored resumes and cover letters, draft custom application answers, and stop for CAPTCHA, legal, or unsupported-claim boundaries.

Client workflow systems

Design assistant workflows around real business records, Airtable/CRM-style structures, Zoho-style databases, documents, follow-ups, approvals, and operational handoff.

Business system agents

Build named OpenClaw agents such as Clyde for CRG Installations, connecting websites, email workflows, company databases, workspace tools, and daily operating routines.

Website operations

Audit and stage updates for NathanBatiste.com, FlightBond Media, and other project sites while preserving working production configs and using CMUX / Pi-style implementation loops where useful.

Creative production support

Organize video ideas, AI-assisted content workflows, Vimeo portfolio links, project proof pages, messaging, and delivery plans.

Research and document intelligence

Search, summarize, compare, and turn scattered information into next actions, drafts, checklists, and decision-ready notes.

Risk-aware automation

Automate small, reversible, or read-only work by default while keeping sensitive actions behind explicit human confirmation.

Operating Pattern

Inspect, prepare, stop at the right boundary, then execute with approval.

Input

Nathan gives a goal

A job application, site update, client workflow, research question, or operational problem starts as a plain-language request.

Context

Mercury gathers evidence

It reads the relevant local files, checks live sites, searches context, compares constraints, and identifies blockers before acting.

Build

Materials are prepared

Drafts, resumes, website changes, diagrams, notes, links, or implementation plans are created around the actual workflow.

Gate

Human approval controls risk

Mercury stops before public, irreversible, financial, credential, or outbound actions and asks Nathan to confirm.

Technical Details

Built like a private operations stack.

RuntimeOpenClaw agent stack on Linux with CMUX / Pi-assisted workflows
InterfaceDirect command channel
MemoryDaily notes, curated memory, project registry, workflow docs
IntegrationsWeb research, local files, Gmail/Calendar/Drive workflows where authorized, GitHub, static websites, job boards
ControlsScoped messaging, sensitive-action boundaries, approval gates
OutputBriefings, drafts, resumes, cover letters, site updates, technical plans, follow-up notes, workflow packages

Build Something Similar

Mercury is the working proof behind Nathan's AI workflow consulting.