JOE-OS
An agent-operated second brain that runs my projects, knowledge, and inbox.
Jul 2026 – present
JOE-OS is one Obsidian vault with every dev project checked out as a git submodule underneath it. AI agents — Claude Code and Codex — write and maintain all wiki content: project overviews, architecture, decisions, and work history, plus distilled tech-stack knowledge where every claim is provenance-tracked back to the source docs it was verified against. I read the wiki, ask it questions, and direct the work; the agents do the writing and keep it current.
What makes it an operating system rather than a note pile is the machinery around the content: naming and linking conventions that keep every page in one connected graph, append-only logs of every operation, staleness detection and lint passes that catch drift, persistent memory that carries context across sessions, and an email layer that turned my inbox into a system — a ~500-rule sender taxonomy that labeled 17,000+ Gmail threads into nine categories, an unsubscribe ledger, and a twice-daily maintenance routine.
Key features
Agent-maintained wiki
Overviews, architecture, decisions, and work history for every project — written by agents after each work session, never by hand.
One connected graph
A trait system with globally unique page names and bidirectional wikilinks, so projects, tech knowledge, and personal ops join a single navigable graph.
Provenance-tracked knowledge
Tech-stack pages distill how each tool actually works, verified against current docs — sources cited, with staleness dates that trigger re-verification.
Inbox as a system
A ~500-rule taxonomy labels 17k+ Gmail threads into nine categories, backed by record pages, an unsubscribe ledger, and a twice-daily routine.
Fleet operations
Every project is a git submodule with branch and shipping conventions; shared skills, session memory, and Claude/Codex parity keep multi-repo work consistent.
What's next
Task foundation
A unified task and goal layer across all projects — the substrate that scheduled agents will draw work from.
Daily briefing agent
A morning cloud agent that reads email, calendar, and project state, and files a briefing page before the day starts.
Autonomous project workers
Scheduled agents that pick up planned tasks, work on dedicated branches, and open pull requests for review.
New traits
Branding, business, and research divisions of the vault — same conventions, new domains, each with its own schema and MOC.
Built with
Source code for this project is private.