# Local-First
Reality Gate operates primarily from local application state and existing Git repositories.

# Your Repository Remains Yours
The passive pilot workflow was verified not to mutate the tested source repository.
The pilot E2E verified that passive:
- Add Repository
- Dependency analysis
- Continuity
- Proof viewing

left the disposable repository unchanged in:
- HEAD
- git status
- working-tree diff
- cached diff
- representative file SHA-256

# Application Data
Reality Gate uses the following local application data roots:
- `%APPDATA%\Reality Gate`: Contains primary configuration, databases, and logs for the local platform.
- `%APPDATA%\offlineforge`: Contains legacy configuration from early architecture slices.

# Uninstall
The uninstaller performs the following verified actions:
- application binaries removed
- source repository remained
- Reality Gate AppData was retained

# Network
Provider dependency and configuration analysis should not be confused with provider availability checks. The passive pilot workflow is intended not to silently push, fetch, clone, or modify provider state.
