# Framework Reboot > Rethinking the processes and frameworks behind productivity and operational efficiency in the age of AI. Essays, release notes and open source tools by hoponthestack. Framework Reboot is the site and studio of Mats Hoppenbrouwers, who writes as hoponthestack. Founder and engineer working on the operational layer of software: the frameworks, state and glue that decide how work moves through a team. The site has three kinds of content: the log (essays, notes and release notes), a catalogue of open source components and products, and a glossary that defines the terms used across both. The full text of everything is at https://www.frameworkreboot.com/llms-full.txt. ## Open source components - [session-flow](https://www.frameworkreboot.com/products/session-flow.md): A workflow for coding agents, with persistent work records and a generated backlog. (v3.2.0) - [session-scribe](https://www.frameworkreboot.com/products/session-scribe.md): Bridges local agent sessions into Notion and GitHub Issues; ended sessions become dated log entries, the backlog mirrors out, and work marked ready pulls back in. (v0.4.0 · unmaintained) - [session-ops](https://www.frameworkreboot.com/products/session-ops.md): The multi-repo operations layer: the feed, the clock, and the portfolio view across repos. It triages and drafts; it never implements and never publishes. (v0.3.0) - [pmstate](https://www.frameworkreboot.com/products/pmstate.md): Project state as a first-class primitive; snapshot it, diff it, reason about it. (v0.4.0 · PyPI) - [anvil-bridge](https://www.frameworkreboot.com/products/anvil-bridge.md): A terminal bridge to Anvil apps via the Server Uplink: run diagnostics, query Data Tables and call server functions from your shell or an AI coding assistant. (v0.2.2) - [tauri-python-sidecar](https://www.frameworkreboot.com/products/tauri-python-sidecar.md): A Tauri desktop app that runs Python as a supervised child process, with the reasons kept in the comments. (v0.1.1) - [cep-protocol](https://www.frameworkreboot.com/products/cep-protocol.md): A 14-event protocol for the traffic between a shell and a harness, plus a seven-member adapter contract. Extracted from a discontinued desktop agent shell and frozen. (v0.1.1 · frozen) ## Products - [commandlane](https://www.frameworkreboot.com/products/commandlane.md): A keyboard-first command surface for operational work; every action one keystroke away. (discontinued) - [cropfolio](https://www.frameworkreboot.com/products/cropfolio.md): Track your garden as an investment portfolio: projected savings, ROI and harvest yields. (live) ## Essays - [What session-flow adds to plain Claude Code, and when to skip it](https://www.frameworkreboot.com/writing/session-flow-vs-plain-claude-code.md): What my Claude Code plugin adds over using the agent with nothing installed, and the cases where it is not worth the overhead. (Nov 2026) - [Running Python in a Tauri app as a supervised sidecar](https://www.frameworkreboot.com/writing/python-in-tauri-sidecar.md): Run Python as a child process that the Tauri app watches and restarts. The parts, the order to build them in, and the pitfalls a template already handles. (Nov 2026) - [I built a Notion agent in 2025. Now I just ask.](https://www.frameworkreboot.com/writing/notion-ai-agent-build-or-ask.md): The service I built to run agents against Notion, what made it unnecessary, and the index file that makes asking an assistant work. (Nov 2026) - [What a discontinued app leaves behind](https://www.frameworkreboot.com/writing/what-a-discontinued-app-leaves-behind.md): CommandLane is not shipping. The hardest part of it now stands on its own: a Python sidecar supervised by a Tauri desktop app, published as a template. (Sep 2026) - [Why session-flow is a chain](https://www.frameworkreboot.com/writing/why-session-flow-is-a-chain.md): A Claude Code plugin that writes down the instructions I was otherwise retyping every session. (Sep 2026) - [Operational efficiency is a design problem, not a tooling problem](https://www.frameworkreboot.com/writing/operational-efficiency-is-a-design-problem-not-a-tooling-problem.md): Most teams already have the tools they need. What they are missing is a shared model of the work. (Jun 2026) - [anvil-bridge and the case for operational glue](https://www.frameworkreboot.com/writing/anvil-bridge-and-the-case-for-operational-glue.md): The integrations between your tools are where operational knowledge quietly lives, and quietly rots. (Apr 2026) - [Why I'm rebooting the framework](https://www.frameworkreboot.com/writing/why-im-rebooting-the-framework.md): Framework Reboot is a bet that the frameworks I inherited for managing work weren't built for a world with AI in the loop. (Feb 2026) - [Rethinking PARA: why I added an operations layer](https://www.frameworkreboot.com/writing/rethinking-para-to-opera.md): PARA organized my digital life for years. Here is why the arrival of AI meant even a system that good had to grow an operations layer. (Feb 2025) - [Building the Operations layer: a Notion and agents integration (part 1)](https://www.frameworkreboot.com/writing/operations-layer-notion-agents.md): Turning the OPERA Operations layer from an idea into a Notion and agents integration you can actually run. (Feb 2025) - [OPERA, part by part](https://www.frameworkreboot.com/writing/opera-framework-explained.md): What the OPERA framework is, what each of its five parts holds, how it differs from PARA, and how it has aged since 2025. (Feb 2025) - [A matrix for telling whether your productivity system still works](https://www.frameworkreboot.com/writing/framework-evaluation-matrix.md): A diagnostic for knowing when a productivity system has quietly stopped serving you, and what to do about it. (Feb 2025) ## Notes - [session-flow v2: persistent work items](https://www.frameworkreboot.com/writing/session-flow-2-0-persistent-work-items.md): A Python runtime now manages work records and generates the backlog. The chain has sixteen skills, including a migration path for existing projects. (Oct 2026) - [commandlane 0.5 makes agents installable](https://www.frameworkreboot.com/writing/commandlane-0-5-makes-agents-installable.md): A changelog note: external agents now install in one click, and you can keep several on hand and switch between them mid-flow. (Jul 2026) ## Glossary - [Complexity creep](https://www.frameworkreboot.com/glossary/complexity-creep.md): The stage where a framework's original elegance disappears under accumulated workarounds and you spend more time running the system than working inside it. - [Framework Evaluation Matrix](https://www.frameworkreboot.com/glossary/framework-evaluation-matrix.md): A diagnostic that scores a productivity system on seven dimensions and tells you which two or three need attention. - [OPERA](https://www.frameworkreboot.com/glossary/opera.md): A filing framework that keeps PARA's structure and adds an Operations layer for task management, knowledge curation and automation. - [Operational design](https://www.frameworkreboot.com/glossary/operational-design.md): The practice of making your model of the work explicit before you reach for software. - [Operational glue](https://www.frameworkreboot.com/glossary/operational-glue.md): The integration code between systems, which carries a team's real operating logic while nobody treats it as real work. - [Operations layer](https://www.frameworkreboot.com/glossary/operations-layer.md): The automation layer in OPERA: the part that routes tasks to agents, curates the knowledge base and keeps a workflow continuous across tools. - [Evidence-based verification](https://www.frameworkreboot.com/glossary/evidence-based-verification.md): A pass that cites a file and line, a command's output or a test name for every claim, and treats missing evidence as failure. - [Independent test oracle](https://www.frameworkreboot.com/glossary/independent-test-oracle.md): Acceptance tests written before implementation by a different agent, which the implementers must satisfy and may never edit. - [Reporters report, callers filter](https://www.frameworkreboot.com/glossary/reporters-report-callers-filter.md): Review agents label every finding high, medium or low confidence instead of withholding the uncertain ones, and the skill that called them decides what to act on. - [SEQUENCE.md](https://www.frameworkreboot.com/glossary/sequence.md): The generated backlog view: one line per open work item, with a stable identity and either a breakdown link or a marker that it needs one. - [Session-sized task](https://www.frameworkreboot.com/glossary/session-sized-task.md): A unit of work small enough for one agent session to finish: one to five files, clear acceptance criteria, one commit. - [Task breakdown](https://www.frameworkreboot.com/glossary/task-breakdown.md): The set of task records under one work item, each self-contained enough to hand to an agent on its own. - [The chain](https://www.frameworkreboot.com/glossary/the-chain.md): The arrangement of session-flow's skills so that each stage produces the artifacts the next one consumes. - [Agent log](https://www.frameworkreboot.com/glossary/agent-log.md): One dated entry per ended agent session: what was asked, what was done, the evidence for it, and what is still open. - [Escalation](https://www.frameworkreboot.com/glossary/escalation.md): An item the automation refuses to decide, written to a numbered file and surfaced for approval on the unit's pinned dashboard. - [Portfolio view](https://www.frameworkreboot.com/glossary/portfolio-view.md): The cross-repo status rollup: backlog progress, inbox depth, open escalations, last release and activity, run quota and failure streak, for every managed unit. - [Provenance annotation](https://www.frameworkreboot.com/glossary/provenance-annotation.md): A URL attached to a backlog line, meaning that this line and that external item are the same work. - [The clock](https://www.frameworkreboot.com/glossary/the-clock.md): The scheduled triage and sweep workflows on an enrolled unit, plus the guard that caps their cost and the heartbeat that reports their failure. - [Unit](https://www.frameworkreboot.com/glossary/unit.md): A repository that session-ops manages: one with a backlog, direction documents and an entry in the registry. - [Adapter contract](https://www.frameworkreboot.com/glossary/adapter-contract.md): The seven members an adapter must implement to translate one harness's native transport into CEP's fourteen events. - [Shell and harness](https://www.frameworkreboot.com/glossary/shell-and-harness.md): In CEP, the shell is the desktop interface a person types into; the harness is the agent runtime that answers, running the loop and calling tools. - [Backoff ladder](https://www.frameworkreboot.com/glossary/backoff-ladder.md): A capped restart schedule: five attempts at one, two, five, five and five seconds, then stop and say so. - [Supervised sidecar](https://www.frameworkreboot.com/glossary/supervised-sidecar.md): Running Python as a separate child process that a desktop app watches and restarts, instead of embedding an interpreter in the binary. - [Process tree](https://www.frameworkreboot.com/glossary/process-tree.md): In pmstate, the directory tree itself: each node owns a slice of state on disk, as an append-only event log or a JSON table. ## Optional - [session-flow 3.2.0: isolated workspaces and one integration owner](https://www.frameworkreboot.com/writing/session-flow-3-2-0-isolated-workspaces-and-one-integration-owner.md): Task sessions work in isolated source workspaces and hand off exact commits. One owner per repository integrates and releases. (Oct 2026) - [session-flow 3.1.0: verify reuses existing evidence](https://www.frameworkreboot.com/writing/session-flow-3-1-0-verify-reuses-existing-evidence.md): Verify reuses evidence that still applies and runs only the checks that are missing, failing or stale. Simplify becomes an add-on, and a project can name a runbook for delivery. (Oct 2026) - [session-flow 3.0.0: a stricter runtime contract](https://www.frameworkreboot.com/writing/session-flow-3-0-0-a-stricter-runtime-contract.md): 3.0.0 has breaking changes to the runtime's payloads. The runtime refuses payloads it used to accept, and claim and record-result now move tasks through their lifecycle. (Oct 2026) - [session-flow 2.0.3: only open work in the sequence](https://www.frameworkreboot.com/writing/session-flow-2-0-3-only-open-work-in-the-sequence.md): Deferred and cancelled work leaves SEQUENCE.md too. The generated backlog contains only open work, and retired identities stay taken. (Oct 2026) - [session-flow 2.0.2: completed work leaves the sequence](https://www.frameworkreboot.com/writing/session-flow-2-0-2-completed-work-leaves-the-sequence.md): Done items leave SEQUENCE.md while their records remain available. The backlog stays shorter as work is finished. (Oct 2026) - [session-flow 2.0.1: migration can start without a work root](https://www.frameworkreboot.com/writing/session-flow-2-0-1-migration-without-a-work-root.md): Repair can now survey an older backlog before its namespace or work root exists. The plan includes the setup it needs, with no writes until you approve it. (Sep 2026) - [session-flow 1.7.0: reporters report, callers filter](https://www.frameworkreboot.com/writing/session-flow-1-7-0-reporters-report-callers-filter.md): Review agents now label every finding by confidence instead of quietly dropping the uncertain ones. Two conversational skills join the chain, one agent leaves it, and a backlog can now be shared across repos. (Sep 2026) - [About](https://www.frameworkreboot.com/about): who writes Framework Reboot - [RSS feed](https://www.frameworkreboot.com/feed.xml): the log as a feed, with full text - [github.com](https://github.com/matshoppenbrouwers) - [x.com](https://x.com/hoponstack)