Implementation is Disposable.
Understanding Isn't.

Import Claude Code history and browse sessions by project. Read the messages in order, including recorded tool activity and the answers you gave. Search decisions by their text, or narrow them to a branch, file, session, project, or date range.

When a choice deserves a clearer explanation, give it a curated decision record. Add a title, rationale, related files, and citations. You can write one yourself or promote a decision from imported history.

The history area also has readers for imported plans, memory documents, configurations, artifacts, pastes, and terminal commands. Availability depends on the sources you import. These readers do not imply that every source has been synchronized to a hosted account.

Your preference profile describes how you like to build across projects. It can include architectural principles, testing expectations, tool preferences, and the tradeoffs you are willing to make.

The manifesto is the collection of opinions you choose to put into practice. Give each one a rationale and a scope. A preference for thin Laravel controllers may be broadly useful; a particular queue configuration may belong to one application.

A user-visible profile makes tradeoffs atomic: each choice has its own rationale, benefits, costs, and scope. You can inspect and customize that choice independently. For example, you might usually favor fewer dependencies but accept a maintained package for a particular capability. That exception should not change your preferences everywhere else.

We are developing a way to configure that manifesto for each project, carrying the relevant opinions into instructions, plans, and review. You decide what becomes guidance. A passing comment or a one-off compromise should not silently become a permanent rule.

Deliberation gives you a place to challenge those opinions. Keep the alternatives and evidence, record an exception when it is justified, and revise your preferences when experience changes your mind.

Versioned project instructions already preserve what a task received. The broader profile and manifesto workflow builds toward applying your judgment consistently without treating every project as identical.

An execution request records the instructions you submitted, the attached inputs, the selected target, and the permissions the job needs. Burdgen stores the request before dispatching the work and gives it a permanent page.

Task plans show dependencies, readiness, and available actions. Run records show the execution events, output, result, and artifacts the runner reports. You can leave the page and return later without making your browser responsible for keeping the agent alive.

Corrections create linked requests. Re-planning keeps the earlier plan. These are useful distinctions when you need to understand why a second attempt differed from the first.