# Separate Hermes Shared folder — setup and verification

Use this when Rob wants a synced working/drop folder that is not indexed by Obsidian.

## Default topology

| Setting | Value |
|---|---|
| Folder ID | `hermes-shared` |
| Label | `Hermes Shared` |
| VPS path | `/root/.hermes/shared` |
| Connie path | `C:\Users\Rob\Hermes Shared` |
| Type | `sendreceive` |
| Devices | VPS + Connie only by default |
| Versioning | Simple, keep 10 versions on the VPS side |

Do not include the Surface unless Rob explicitly asks. Device scope is a real design choice because every added device receives all files and participates in deletions.

## Create from the VPS

1. Read `/root/.local/state/syncthing/config.xml` to obtain the local REST API key and existing device IDs. Never print the API key to chat.
2. Verify `syncthing@root` is active and enabled.
3. GET `/rest/config/devices` and identify Connie by name rather than guessing an ID.
4. GET `/rest/config/folders`; if `hermes-shared` already exists, inspect rather than overwrite.
5. Create `/root/.hermes/shared`.
6. POST `/rest/config/folders` with:

```json
{
  "id": "hermes-shared",
  "label": "Hermes Shared",
  "path": "/root/.hermes/shared",
  "type": "sendreceive",
  "devices": [
    {"deviceID": "<VPS_ID>"},
    {"deviceID": "<CONNIE_ID>"}
  ],
  "rescanIntervalS": 3600,
  "fsWatcherEnabled": true,
  "versioning": {
    "type": "simple",
    "params": {"keep": "10"}
  },
  "paused": false
}
```

7. Put a short `README.txt` in the folder stating the two paths and warning against secrets.
8. Rob accepts the new folder share on Connie and chooses `C:\Users\Rob\Hermes Shared`.

## Verify before declaring success

Verify the configuration and real state, not merely the POST response:

- GET `/rest/config/folders` and confirm ID, label, path, type, device scope, and versioning.
- GET `/rest/system/connections` and confirm Connie is connected.
- GET `/rest/db/status?folder=hermes-shared` and require:
  - `errors = 0`
  - `pullErrors = 0`
  - `needTotalItems = 0`
  - `needBytes = 0`
  - `state = idle`
- Confirm at least one known test/readme file exists locally with a reasonable byte size.
- For a delivered artifact, compare source and shared-copy SHA-256 hashes before saying it is available.

A newly created share can be configured on the VPS before Connie accepts it. If Connie has not accepted the share yet, report that accurately rather than claiming the Windows path already exists.

## Artifact routing rule

For generated resumes and other user-facing files:

1. Save the canonical generated file to the writable VPS output location.
2. Attach it to chat when supported.
3. Copy it to `/root/.hermes/shared/<project>/` for ordinary Windows Explorer access.
4. Verify checksum + Syncthing database status.

Use the Obsidian vault only for curated notes and deliberate vault content—not as the default binary-file delivery bus once Hermes Shared exists.