> ## Documentation Index
> Fetch the complete documentation index at: https://xerg.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Hermes analysis

> Understand state-only coverage, full first-party observer reconciliation, and local mechanical evidence.

Hermes `state.db` is Xerg's sole monetary authority. Xerg opens it read-only,
reconciles Hermes's session/model/task usage, and never lets observer or trace
records add tokens, requests, or spend.

## State-only audits

```bash theme={null}
npx @xerg/cli@latest audit --runtime hermes --state-db ~/.hermes/state.db
```

State-only audits provide exact aggregate economics, tool inventory when
Hermes stored tool-message records, compression/branch/delegation lineage,
workload economics, and explicit analysis coverage.

Because a state aggregate may represent several API requests, Xerg excludes it
from retry, tool-loop, context-growth, and other sequence-dependent monetary
rules. The report says when those analyses were not eligible; missing evidence
is never presented as proof of zero inefficiency.

## Full first-party request evidence

Install Xerg's optional local observer:

```bash theme={null}
hermes plugins install xergai/hermes-observer --enable
```

Then run:

```bash theme={null}
npx @xerg/cli@latest audit \
  --runtime hermes \
  --state-db ~/.hermes/state.db \
  --hermes-events-dir ~/.hermes/xerg/events
```

The observer records content-free request, tool, terminal, delegation, and
lifecycle evidence. For each provider/model group Xerg requires request count
and input/output/cache buckets to equal `state.db` exactly. Exact groups become
ordered one-request calls; incomplete, dropped, ambiguous, or conflicting
groups remain unchanged aggregates. Authoritative cost is allocated across
exact requests and sums back to the state cost exactly.

The observer never persists prompts, messages, tool definitions, arguments,
commands, paths, results, delegated goals, summaries, or file contents.
Content may be inspected transiently only to compute counts, byte sizes, and
process-scoped keyed fingerprints.

## Local analysis blocks

Both Hermes and OpenClaw local summaries can include:

* `analysisCoverage`: eligible/fallback request counts plus tool, lineage, and context coverage
* `toolActivity`: execution names/counts, exact/heuristic/unassociated linkage, result bytes, and associated model spend
* `workloadEconomics`: root/child/descendant calls and spend, depth, first-child economics, and lineage gaps

Hermes also retains `mechanicalEfficiency` for direct terminal/tool mechanics.
These blocks remain local. They do not change findings taxonomy,
recommendations, thresholds, Audit Push Payload v3, hosted storage, dashboards,
or MCP.