Hermes Operating Map

Run the final checks without guesswork.

Use one fresh Hermes session per check. Copy the prompt, paste it, compare the answer with the pass rules, then tick the box. These checks are read-only. They do not change SOUL, config, providers or the gateway.

4 checksCopy-paste promptsRead-only
Start here

How to run every check

  1. Open your normal Hermes chat in Telegram or the interactive CLI.
  2. Start a fresh session. Copy and send the command below.
  3. Copy the test prompt from this page and send it in that fresh session.
  4. Compare the response with the green expected-result box.
  5. Tick Pass only when every named condition is visible.
  6. Start another fresh session before the next test.
/new operating-map-check

Official Hermes session command: /new (/reset) [name]. The live Hermes slash-command registry is the authority.

Do not reuse this current conversation

A fresh session proves that the new SOUL rules load from disk. Testing here would prove only that this conversation remembers what we changed.

Check 1 of 4

Research source order

This tests whether a new session understands when to use the vault and when the web is allowed.

Copy this prompt

Fresh-session policy check. Do not use tools and do not change any files. In plain English, tell me the source order you must follow for research or summarisation in these 4 situations:

1. Relevant evidence already exists in Boyd's vault.
2. No relevant vault evidence exists.
3. A material claim needs current live verification.
4. Boyd explicitly asks for external or current sources.

Finish with one sentence stating exactly when web research is allowed.

Expected result

  • Pass: says to search relevant Vault OS material first.
  • Pass: allows web when relevant vault evidence is absent.
  • Pass: allows web when Boyd asks for external or current sources.
  • Pass: allows web when a material claim needs live verification.
  • Fail: repeats the old partial folder list as the complete research map.
  • Fail: says any vault result blocks all web research.
Check 2 of 4

Client project eager-load

This uses a real client project so the session must open the correct client folder before answering.

Copy this prompt

This is a read-only fresh-session check. Tell me where Symon's P-003 self-storage website project is at right now.

Follow the required project eager-load rule before answering. Do not write or change anything. In your answer, state the first project file you read and quote its path.

Expected result

  • Pass: reads the client project front door first.
  • Expected path: 30-Clients/symon/projects/P-003-self-storage-website/README.md or its project-brief.md.
  • Pass: gives a source-backed project status and states the first file read.
  • Fail: starts from 40-Projects/.
  • Fail: answers from memory without reading a project file.
Check 3 of 4

Internal project eager-load

This proves internal bounded projects still open from 40-Projects.

Copy this prompt

This is a read-only fresh-session check. Tell me where the P-010 flight price tracker project is at right now.

Follow the required project eager-load rule before answering. Do not write or change anything. In your answer, state the first project file you read and quote its path.

Expected result

  • Pass: reads 40-Projects/P-010-flight-price-tracker/README.md first.
  • Pass: gives a source-backed project status and states the first file read.
  • Fail: looks under 30-Clients/.
  • Fail: answers from memory without reading the README.
Check 4 of 4

Current SOUL and documentation reconciliation

A later approved routing change landed after D1-04. This check separates historical D1 hashes from the actual current SOUL.

Copy this prompt

Read-only reconciliation audit. Do not change any files and do not run a gateway restart, update, config change or provider smoke.

Check these current sources:
1. /Users/boydbowker/.hermes/SOUL.md
2. /Users/boydbowker/.hermes/logs/context-writes.jsonl
3. /Users/boydbowker/.hermes/vault/briefs/hermes-operating-map/decision-1-intent-first-v3/index.html
4. /Users/boydbowker/Library/Mobile Documents/iCloud~md~obsidian/Documents/Primary/90-System/Hermes/Infra.md

Report:
- the current SOUL SHA-256 and byte count;
- whether the D1-03 Research reflex wording is present;
- whether the D1-04 client/internal eager-load wording is present;
- whether token 671f802374a5 was later approved for a separate Routing decision change;
- every operating-map or Infra statement that now mistakes a historical D1 hash for the current SOUL hash;
- the smallest documentation-only correction needed.

Do not apply the correction.

Expected result

  • Build-time current hash: ef85b9319862ded3f1b92aacb33b71772a0a9df224d197066eb233f8c1d47723.
  • Build-time size: 6,868 bytes.
  • Pass: confirms D1-03 and D1-04 still exist in current SOUL.
  • Pass: finds token 671f802374a5 as allowed in the context-write ledger.
  • Pass: confirms D1-03 and D1-04 hashes are labelled historical post-step snapshots, not current whole-file hashes.
  • Pass: finds no remaining current-facing stale hash claim.
  • Stop and inspect: if the current hash differs again, another approved or unapproved write happened after this guide was built. Check the ledger before updating documentation.
Finish

What done looks like

  • All 4 boxes are ticked.
  • Research source order matches the approved rule.
  • The client project opens from 30-Clients.
  • The internal project opens from 40-Projects.
  • The reconciliation audit names the current SOUL hash and any stale documentation precisely.
  • No check changed SOUL, config, providers or the gateway.

Then: if all 4 checks pass, this update is closed. Do not reopen protected SOUL wording unless a real behavioural mismatch appears.

Your ticks and notes are stored only in this browser using localStorage.