the task continues after the window closes
Google’s Agent Executor, Screenpipe recovery fixes, and ReAdapt’s relationship-state benchmark.
[!] OPERATING LAYER / PLAIN-TEXT SOVEREIGN OS
self.md maps the layer above the model: memory, tools, connectors, local runtimes, browser agents, coding workbenches, receipts, and boundaries.
Start with the operating problem. Pick the smallest stack that can act, remember, and prove what it did.
The map for tools, memory, receipts, workflows, registry entries, and stack recipes.
The concept before tool shopping begins.
Layers, loops, custody, boundaries, and receipts.
■ 02 / OPERATORS
Working patterns from people who built the tools, documented the loops, and kept humans in control.
OPERATOR / 01Digital gardens as working context, not content furniture.
OPERATOR / 02Research loops that turn pages into reusable working context.
OPERATOR / 03Vibe coding as an operator workflow with taste and review.
OPERATOR / 04Prompts compiled into programs that can be inspected and improved.
OPERATOR / 05Software in the AI era: vibe coding for prototypes, three-layer workflow for production.
OPERATOR / 06Breaking complex AI reasoning into verifiable subtasks with human oversight.
OPERATOR / 07Small tools, SQLite logs, and rapid experiments that keep the loop inspectable.
Agents that learn across virtual and physical worlds through reusable skills.
■ 03 / CURRENT SIGNALS
Short, source-backed readings from the edge of personal AI systems.
Showing 1–3 of 8 signals
■ 04 / LIBRARY
Every surface has explicit boundaries, code snippets, and evidence.
Mental models, architecture, context engineering, and failure modes.
Practical step-by-step implementations with tests and diffs.
Installable agent toolpacks, Claude Code plugins, and MCP bundles.
Control surfaces, local runtimes, memory engines, and coding workbenches.
Operators running AI as their daily OS with public recipes.
Weekly radar dispatches on agent protocols, memory, and tooling.