# Getting started

Lage Bureau is a browser application for building Networks of entities, relationships and their sources. The current prototype is for synthetic or non-sensitive material. Editable Networks are unencrypted and local to the browser profile. Signing in does not turn them into account-owned cloud documents.

## Open your first Network

**Prerequisites:** a desktop or laptop browser, an account you may use, and synthetic material for the exercise. Start at [the application](https://app.lagebureau.de).

1. Choose **Log in**, or **Create account** if you need an account. Complete the account form yourself. If **Check your email** appears, complete that step before expecting access to the editor. Use a provider button only when it is present in this deployment.
2. In the Network catalog, choose **Open demo Network** to inspect a synthetic example. To start empty, choose **Create Network**, enter a title and optional description, and choose **Create**.
3. The editor opens with the entity palette and record outline, the canvas, and the Inspector. Select a record in the canvas or outline to inspect it.
4. After an edit, check the save status. **Saved locally** means the app saved the current Network in this browser profile. It does not mean the Network was uploaded or backed up.

**Expected result:** one editable Network in the current browser's catalog. A demo is example material, not verified research.

## Understand where your data lives

| Data                              | Current location and effect                                                          |
| --------------------------------- | ------------------------------------------------------------------------------------ |
| Working Networks                  | Plain IndexedDB in the current browser profile and app origin                        |
| Interface language and appearance | Preferences in that browser's localStorage                                           |
| Your saved OpenRouter test key    | Plain localStorage in that browser; separate from Network JSON                       |
| Account access                    | Supabase Auth and an owner-only minimal profile                                      |
| Published snapshots               | A separate hosted exception when that deployment enables it; see the sharing chapter |

A different browser profile, device or origin has different local storage. Data does not move automatically from a former app hostname. Use a validated Network JSON export/import for a deliberate transfer. **Log out** ends account access but does not delete local Networks. Another account using the same browser profile does not create a separate encrypted workspace.

## Recover without destroying the working copy

If loading or saving fails, read the displayed error and use the offered retry. Keep the current editor open when it reports that an edit remains unsaved. Export a copy when possible before changing browser storage. Do not use **Clear all prototype data** as a routine troubleshooting step: it permanently removes local Networks, preferences and the saved test key.

The prototype has no Network Trash, account-owned Network synchronization or app-managed password-recovery workflow. For sensitive investigations, the current prototype's storage boundary is insufficient.