x:0 y:0 Overview / 01
Project · Personal operating rooms

PersekOS

The useful part is not the AI stack. It is the rooms the stack keeps alive.

I use PersekOS as a local home for work that normally disappears into chats, notes, reminders, browser tabs, and half-finished ideas.

This page used to spend too much time explaining layers. That is less interesting than the thing itself: a set of small rooms that catch real life, turn some of it into tasks or plans, and keep a readable trail behind.

Room mapEach room has a narrow job instead of one giant inbox.
Generated viewsLocal HTML pages make the records readable.
Piper front doorI can talk into the system without hand-sorting everything.
Private by defaultThe public version shows shape and value, not the private ledgers.
x:0 y:980 Why / 02
Why bother?

Because chat is a terrible filing cabinet.

AI is great at helping in the moment. The problem is the moment ends. The decision, the task, the useful clip, the personal note, the maintenance reminder, the plan, the thing I said I cared about, all of that needs somewhere to land.

PersekOS is my answer to that. Not a product. Not a grand theory. Just rooms, ledgers, generated pages, and a chief-of-staff layer that helps put things in the right place.

x:980 y:0 Home / 03
The front door

PersekOS Home starts with the rooms.

Home is a local dashboard with a set of rooms. Open one and you get the generated view, the latest artifacts, and the supporting files that matter for that room.

PERSEKOS HOME / ROOM ATLAS HOME Guide LLM Wiki GBrain Dump Daybook Tasks Life Ops Habits Media Intel Planning Curio ROOMS + GENERATED VIEWS + SUPPORT FILES
A build-plate view: small labeled rooms, not one giant inbox.
x:980 y:900 Tasks / 04
Do

Tasks is where commitments stop floating around.

The Tasks room gives Piper one canonical place for personal work: Inbox, Today, Upcoming, Done, reminders, and review state.

Demo today84 sample items, with 19 pulled into "do first"
Demo inbox160 sample unsorted or waiting items
Useful bitPiper can narrow, defer, clarify, or archive without turning the browser into a write surface.

That sounds plain because it is plain. It is also the difference between "I mentioned that somewhere" and "there is a place to look in the morning."

x:1840 y:900 Life Ops / 05
Maintain

Life Ops is the room for real-world drag.

Home admin, records, repairs, maintenance, and follow-ups. This is the stuff that does not feel like "productivity" until it quietly eats a week.

Demo assets900+ sample things
Demo records1,800+ sample files
Demo decisions74 surfaced instead of buried

The value is not that AI knows the private details. The value is that records, decisions, and maintenance work are not scattered across screenshots and memory.

x:-780 y:0 Capture + Reflect / 06
Brain Dump and Daybook

Some rooms are intentionally messy.

Brain Dump is where raw thoughts go before I know what they are. Daybook is where the day gets closed out before the details fade.

Brain Dump capture

A quick, private place for half-formed ideas. Some become plans, tasks, or research. Most should not.

Daybook reflection

A dated memory ledger for wins, gratitude, events, and what actually happened.

I like this because it keeps low-pressure capture separate from polished planning. Not every thought deserves a project.

x:1840 y:0 Signal / 07
Intel and Media Library

The signal rooms keep the firehose from winning.

Intel Daily Briefs turns AI/operator news into a morning magazine with lanes. Media Library keeps podcasts and videos only when they earn a spot.

Demo intel120 sample issues, 24 lanes, 4,800+ sample captures
Demo media260 sample sources and 1,400 sample episodes
Filtersave the useful parts; do not make every feed an emergency
x:0 y:1740 Planning + Learning / 08
Shape

Plans get their own room too.

The Planning room is where brainstorms, specs, implementation plans, proposals, and decision records land. It keeps serious thinking out of chat scrollback.

Curio does the same thing for learning. Instead of asking for a one-off explanation and losing it, lessons turn into small atlases with progress and a next step.

Recent artifact

A feature-map and Hermes-native build plan landed as a rendered Planning artifact, not a loose markdown file.

Learning artifact

Curio keeps topic atlases, lesson posters, source status, and progress in one place.

x:920 y:1740 Memory + Research / 09
Know

Memory and research are different rooms.

GBrain is for lived context and entities: projects, places, systems, decisions, and other private context. LLM Wiki is for external research: source-backed topics that agents can read before pretending to know things.

Keeping those separate matters. My private context should not be treated like web research, and web research should not become a vague memory claim.

x:1780 y:1740 Loop / 10
How a thing moves

The loop is simple.

01CaptureA thought, record, source, task, or decision lands in the closest room.
02RenderThe room produces a readable local view so I can review it without spelunking files.
03ActPiper can surface the next move, but risky actions still stop for approval.

The constraint is the whole trick. AI can help move things along, but the system has to show me what it did and where the source lives.

next dragpan 0fit all Eschome
Want to reach out? X is best.
x / @dpersek linkedin github / syntaxsawdust