> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_08/session_03_local_erasure_runtime_and_controls.md).

# Session 03: Local Erasure Runtime and Controls

**Session ID**: `phase08-session03-local-erasure-runtime-and-controls` **Status**: Not Started **Estimated Tasks**: \~16-24 **Estimated Duration**: 2-4 hours

***

## Objective

Implement a user-initiated local trusted-erasure workflow for release-scoped local and browser state with dry-run, confirmation, audit, and verification behavior.

***

## Scope

### In Scope (MVP)

* Add local dry-run and confirmed erasure flows for archives, memory, exports, replay buffers, settings, diagnostics, logs, backups, lifecycle files, valid spool state, and browser state that are in release scope.
* Add CLI and web controls that clearly separate preview, confirmation, progress, partial failure, completed, and unsupported states.
* Preserve local-first operation and require explicit user action before destructive changes.
* Add tests for idempotency, partial failure, sensitive-path redaction, unsupported paths, and browser storage cleanup.
* Update package READMEs and stable docs for local erasure behavior and limitations.

### Out of Scope

* War Room Durable Object erasure.
* Hosted account, hosted storage, analytics, public replay, push, or remote-access deletion.
* Deleting workspace source files unless Session 01 explicitly routes a release-scoped cleanup item to this workflow.

***

## Prerequisites

* [ ] Session 02 erasure contracts and inventory exist.
* [ ] Local backup, archive, lifecycle, browser, replay, and diagnostics storage paths are documented.
* [ ] Destructive operations have a dry-run mode and confirmation copy.

***

## Deliverables

1. Local erasure runtime and CLI/web controls.
2. Tests for local erasure success, dry-run, idempotency, partial failure, and redaction.
3. Updated docs for local trusted erasure and remaining non-local boundaries.

***

## Success Criteria

* [ ] A user can preview and confirm local erasure without exposing raw prompts, paths, commands, tokens, logs, exports, or backups.
* [ ] Verification proves release-scoped local and browser state was deleted or reported as unavailable.
* [ ] Remaining Worker or hosted boundaries are not overclaimed as erased.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/phases/phase_08/session_03_local_erasure_runtime_and_controls.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.