docs(hermes): ground OpenClaw history in retained evidence

services/hermes/skills/master-hermes-on-atlas/SKILL.md

@@ -72,9 +72,9 @@ student commits to a finding.
 ## Validate claims honestly
 
 Use the claim audit in `references/mastery-rubric.md`. Current configuration and
-live demonstrations can support current-use claims. They cannot prove that
-OpenClaw previously ran or was replaced; require Git history, retained manifests,
-or other evidence before treating that historical claim as demonstrated.
+live demonstrations support current-use claims. The retained Git history and
+bound OpenClaw PVC support the deployment/replacement history; require Brad to
+inspect that evidence and distinguish it from proof of every past interaction.
 
 End every session with:
 

services/hermes/skills/master-hermes-on-atlas/references/architecture.md

@@ -49,6 +49,23 @@ kubectl -n hermes-chat get deploy hermes-chat -o wide
 
 Do not change the GPU owner as part of a lesson.
 
+## Retained OpenClaw replacement evidence
+
+OpenClaw is not part of the current inference path, but its deployment history
+is retained:
+
+- `1bc58e10` added the OpenClaw testing-triage workspace, workload, model,
+  ingress, RBAC, and storage.
+- follow-up commits wired local diagnosis, OIDC, persistence, and the gateway.
+- `97ecb36b` replaced OpenClaw with Hermes and moved the agent-facing resources.
+- `bb5e286f` decoupled Hermes from the retired OpenClaw Flux dependency.
+- the `openclaw-home` PVC remains bound as retained state while no OpenClaw
+  workload is running.
+
+Have Brad verify the commits and live resource shape. This establishes the
+cluster deployment and replacement sequence; Brad's direct experience remains
+the evidence for how he personally used the old agent.
+
 ## Operator evidence path
 
 The operator role is designed for supervised test-failure triage:

services/hermes/skills/master-hermes-on-atlas/references/mastery-rubric.md

@@ -35,7 +35,7 @@ different real incidents and improved a workflow based on what failed.
 | Access starts read-only and scoped | RBAC, NetworkPolicy, separate identities and state | Produce and explain the allow/deny matrix from live authorization checks. |
 | Human approval protects changes | Approval config, deny patterns, Flux workflow | Identify every mutation in a proposed incident response and stop before it. |
 | Local GPU gracefully yields to gaming | Owner state, model gate, fallback | Explain or observe a Wolf ownership window and verify continued fallback service. |
-| OpenClaw previously ran and was replaced | Not established by the current Hermes deployment | Show retained Git history/manifests/logs or qualify the statement as recollection. |
+| OpenClaw previously ran and was replaced | `1bc58e10` deploys the OpenClaw triage stack; follow-up commits add gateway/OIDC/persistence; `97ecb36b` replaces it with Hermes; `bb5e286f` retires the dependency; the bound `openclaw-home` PVC remains without a workload | Inspect the commits and live Flux/PVC state, then explain what they prove versus what depends on Brad's personal recollection. |
 
 ## Triage answer scoring
 

services/hermes/skills/master-hermes-on-atlas/references/two-hour-proof-sprint.md

@@ -1,9 +1,11 @@
 # Atlas two-hour proof sprint
 
 The sprint establishes usable, defensible evidence for the current Hermes
-claims. It does not award mastery and it cannot retroactively prove historical
-OpenClaw use. Brad performs the work; Hermes gives one task at a time, checks
-the evidence, and withholds later answers until Brad commits to a result.
+claims. It does not award mastery. Retained Git and PVC evidence establishes
+the OpenClaw deployment/replacement sequence; Brad's direct experience remains
+the evidence for how he personally used it. Brad performs the work; Hermes
+gives one task at a time, checks the evidence, and withholds later answers until
+Brad commits to a result.
 
 ## 0–15 minutes — control surface and request path
 
@@ -70,6 +72,7 @@ and show a passing and adversarial evaluation.
    pipeline trigger, Flux reconcile, credential/environment change, or manual
    backfill.
 3. Audit the interview answer sentence by sentence using `mastery-rubric.md`.
+   Include the retained OpenClaw commits and live PVC/no-workload state.
 4. Offer to record progress only after Brad approves the write.
 
 Minimum honest outcome:
@@ -78,5 +81,5 @@ Minimum honest outcome:
 - the established Atlas automation path and read-only boundary are explained;
 - one reusable writable skill is created, tested, and improved by Brad;
 - autonomous production mutation is not claimed;
-- historical OpenClaw replacement remains unproven unless independent retained
-  evidence is produced.
+- historical OpenClaw deployment and replacement are supported by retained Git
+  and PVC evidence, with personal-use details identified as Brad's testimony.