> 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_24/session_07_honesty_and_persistence_boundaries.md).

# Session 07: Honesty And Persistence Boundaries

**Session ID**: `phase24-session07-honesty-and-persistence-boundaries` **Package**: apps/web **Status**: Not Started **Estimated Tasks**: \~14 **Estimated Duration**: 2-4 hours

***

## Objective

Prove the live tier cannot lie or leak: replay, reconnect, and mock traffic mint no kills, links, or durable counters; persisted projection data stays aggregate-only inside `factionos-game-v1`; and browser-local erasure still covers everything the phase added.

***

## Scope

### In Scope (MVP)

* Replay regressions: `dispatchReplayEntries` streams containing linked missions, verifications, live-enemy events, and link-creating sequences change no persisted projection numbers (section 14.9 / 13A criterion 5).
* Reconnect/snapshot regressions: snapshot-style events reconcile, never accumulate kills, wraith stacks, or link records.
* Mock-mode regressions: drills animate in memory but persist nothing new from live-tier state.
* Storage inventory: persisted projection fields for links and live enemies hold only bounded ids, safe labels, counters, and timestamps; storage-key inventory tests reject any new key; serialization round-trips.
* Erasure: browser-local reset/erasure still clears everything the phase touches with no new inventory entry needed (or the inventory is updated within the existing browser-local boundary).
* Privacy sweep: persisted state, tooltips, badges, and test fixtures carry no raw prompts, output, file contents, absolute paths, provider payloads, or secrets.

### Out of Scope

* Trusted unified erasure claims (remains no-claim).
* Hosted persistence (deferred to design Phase 11).

***

## Prerequisites

* [ ] Session 02 complete (links exist).
* [ ] Session 04 complete (kills exist).

***

## Deliverables

1. Regression test additions across reducer, store, replay, mock, and serialization seams mirroring the Phase 22 honesty matrix.
2. Storage inventory and privacy test updates.

***

## Success Criteria

* [ ] Replayed or mock traffic cannot create persisted kills, links, or counter movement; tests enforce each seam.
* [ ] `factionos-game-v1` remains the only game storage key; contents remain aggregate-only.
* [ ] Browser-local erasure coverage verified for all new state.
* [ ] Web typecheck and focused tests pass.


---

# 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_24/session_07_honesty_and_persistence_boundaries.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.