{RF}BUILD_ARCHIVE / 010
PRIVATE / LIVE · Tools

// The vault grew an operations layer

Obsidian Command Cockpit

A mobile-first command center for steering Obsidian vault projects, writing tasks back to the source and launching guarded local AI runs without losing the paper trail.

ObsidianVault automationLocal AI
SOURCE_VISIBILITYPRIVATE

This is a private operational system. The repository and live instance are intentionally not public.

01 // THE_PROBLEM

WHY THIS
EXISTS.

An Obsidian vault can hold the source of truth for dozens of projects, but Markdown alone does not provide a fast operational view, safe mobile controls or a clear lane for controlled AI execution.

02 // THE_APPROACH

THE USEFUL
LOOP.

The cockpit reads project and task state from the vault, presents it as an operations dashboard and writes every change back to the underlying notes. AI actions stay bounded to selected context and leave a visible trail.

SANITIZED_PRODUCT_PREVIEW.JPGPUBLIC SAFE ✓
Sanitized preview of Obsidian Command Cockpit with private operational details removed
Names, tasks, keys and infrastructure references intentionally removed from the public build file.
03 // WHAT_SHIPPED

WHAT'S
INSIDE.

01

VAULT PROJECTS

Folders and notes become a navigable project view without replacing the Markdown source of truth.

02

TASK WRITEBACK

Status changes and operational updates land back in the exact notes people and agents already use.

03

GUARDED AI LANES

Local automation runs against deliberately selected context instead of receiving the whole vault by default.

04 // SOURCE_AND_STATUS

READ THE
RECEIPTS.

PRIVATE REPOSITORYNOT EVERYTHING USEFUL NEEDS A PUBLIC ORIGIN.

This is a private operational system. The repository and live instance are intentionally not public.

BROWSE MY PUBLIC GITHUB ↗