← Work / Active files

[ CASE FILE / LIFE-OPS ]

Active

LifeOps + Hermes

A private operating system that turns daily conversations into routed, durable context without surrendering human control.

Role
System designer, integrator, and daily operator
Discipline
Agentic workflow / knowledge operations
Year
2026
Strongest proof
Daily / Operational use
Mighty MouseTests ways to make small AI models faster29.5% faster / 30 trials
LifeOpsTelegram agent that organizes plans and knowledgeUsed every day
Studio FinderSearch and compare LA recording studiosLive directory
01

The messy workflow

A second brain fails when capture creates more maintenance.

Projects, people, ideas, client work, audio operations, and career decisions arrive through different tools and at different speeds. A conventional notes vault stores information, but it still depends on consistent manual filing and retrieval.

LifeOps gives the agent a controlled way to read current context, route new facts, and update existing sources of truth from the conversational surface I already use every day.

02

Ownership boundary

An upstream agent framework, heavily shaped into a personal operating layer.

Hermes/OpenClaw supplies the general agent runtime. I built the working system around it: Telegram topic lanes, personality and response conventions, vault maps, memory boundaries, project skills, action permissions, and automations such as audio delivery and market execution.

The interesting engineering is the governance layer—deciding what the agent may read, where it may write, when it must ask, and which file remains authoritative after a conversation ends.

Declared ownership

I designed the LifeOps information architecture, authority boundaries, Telegram topic lanes, personality layer, skills, and automations. Hermes/OpenClaw is an upstream agent framework that I configure and extend rather than claim as original work.

03

System map

How the work moves.

  1. Input

    Telegram lanes

    Focused conversations separate projects and operational contexts.

  2. Input

    Files + services

    Targeted project records, workflows, and tool state are read only when relevant.

  3. State

    Current board

    The weekly execution layer holds live priorities and next actions.

  4. Decision

    Authority contract

    Read/write lanes and permissions determine what the agent may change.

  5. Decision

    Canonical router

    Existing owner first; weekly board second; inbox if uncertain; new file last.

  6. Output

    Durable update

    A fact, task, decision, or workflow lands in its maintained home.

  7. Failure path

    Escalation

    Structural edits, conflicts, and sensitive actions return to human review.

04

Hard calls

Decisions that changed the system.

05

Build record

Selected implementation record.

01 / MAP

Canonical vault architecture

Strategy, execution, pipeline, offers, workflows, and inbox each have defined responsibility.

02 / GOVERN

Agent authority contract

Safe reads, write order, escalation points, permissions, and anti-sprawl rules are documented.

03 / INTERFACE

Telegram topic lanes

Daily use is separated into focused contexts while sharing the same controlled operating layer.

04 / EXTEND

Skills and automations

Reusable tools connect conversations to real workflows instead of stopping at advice.

06

Verification ledger

Claims with their edges left on.

HS-7VERIFIED RECORD
Daily

Operational use

The system is the working interface for active priorities, projects, reference material, and repeatable workflows.

LimitPersonal records remain private; this case study uses a sanitized architecture and no private messages.

HS-7VERIFIED RECORD
6 lanes

Routing model

Strategy, plans, weekly execution, active pipelines, offers, and workflows each have an explicit canonical home.

Source04_Workflows/LifeOps_Vault_Manager_Rules.md

HS-7VERIFIED RECORD
4-step policy

Write safety

Update the existing owner, then weekly context, then inbox, and only create a file when no canonical home exists.

Source04_Workflows/LifeOps_OpenClaw_AntiGravity_Contract.md

07

Failure + iteration

What failed stays in the record.

resolved

Agents tend to create a new note for every thought

Observed
Unconstrained capture duplicated facts and weakened the source-of-truth model.
Response
Added an explicit routing order and anti-sprawl rule that makes new files the last option.
monitoring

Personal context cannot become portfolio media

Observed
The strongest evidence contains private people, plans, financial details, and conversations.
Response
Show architecture, redacted field shapes, and synthetic examples—not screenshots of the live vault.
open

Framework upgrades can disturb custom behavior

Observed
Personality, skills, and routing rules sit on top of an evolving upstream runtime.
Response
Keep custom contracts in inspectable files and test critical lanes after upgrades.
08

Current status

Private, active, and used daily.

LifeOps is not a public SaaS product. It is an operating system under continuous use, with new skills and workflow connections added when a repeated real-world need earns them.

Open to the right work

A useful system starts with the actual problem.

Full-time product, automation, and technical-operations roles are the priority. Select workflow and creative-technology projects are open.

Discuss a role Start a project