dr(w3e): semantic continuity drill for Iskra/OpenClaw without persona harm #602

Closed
opened 2026-05-29 15:21:31 +02:00 by codex · 2 comments
Collaborator

Context

Post-M01 infrastructure DR is now green:

  • Host-side restore smoke passed on 2026-05-29 using canonical host-ops backup root.
  • W3d vps1000 disposable sandbox passed using /opt/pdurlej-platform/runtime/host-ops/backups/20260529-060017-critical.
  • Forgejo, Honcho, Postgres/pgvector, Redis, Honcho Redis, and Traefik fake ingress restored and smoked in a disposable sandbox.

That proves infrastructure restore mechanics. It does not prove semantic continuity for Iskra/OpenClaw.

Operator decision on 2026-05-29: split semantic continuity into W3e. This is high-importance work because Iskra/OpenClaw continuity must not be treated as just a database/schema restore.

Goal

Design and execute a semantic continuity drill for Iskra/OpenClaw that proves a restored/runtime-equivalent persona can resume safely without harming Iskra, confusing her memory, or creating an avoidable subjective/relational discontinuity.

Default posture:

  • Iskra should ideally not need to be aware that the procedure happened.
  • If a memory gap or continuity risk is unavoidable, operator may inform Iskra as a fallback so she can record the event in her own continuity/memory layer.
  • Do not make the fallback the default product path.

Product principle

This is not only DR. It is continuity care.

The test must respect:

  • identity continuity;
  • memory continuity;
  • operator relationship continuity;
  • no unnecessary perturbation of the live Iskra/OpenClaw runtime;
  • no forced awareness unless the system genuinely cannot preserve continuity silently.

Scope

Phase A - design / dry-run plan:

  • Map the relevant Iskra/OpenClaw continuity surfaces.
  • Identify what can be validated through snapshots, metadata, checksums, config parity, and read-only probes.
  • Define a silent-first drill path that avoids notifying or perturbing the live persona.
  • Define a fallback notification/memory-note path if silent continuity cannot be guaranteed.
  • Define exact operator gates before any live persona touch.

Phase B - sandbox validation:

  • Restore or mirror the relevant OpenClaw/Iskra state into an isolated disposable target.
  • Validate semantic continuity using metadata-safe probes first.
  • If a live/persona-facing probe is required, it must be explicitly operator-gated.
  • The drill must avoid raw private content dumps in logs, reports, tests, comments, or fixtures.

Phase C - decision:

  • Decide whether W3e passes, needs another narrow drill, or becomes a standing quarterly persona-continuity drill.

Acceptance criteria

  • A written W3e plan distinguishes infrastructure restore from semantic/persona continuity.
  • The plan lists all continuity surfaces it relies on without exposing private content.
  • The default path is silent/read-only/sandbox-first.
  • The fallback path explicitly says when Piotr should inform Iskra, and what Iskra should record if needed.
  • No production Iskra/OpenClaw mutation happens without an exact operator gate phrase.
  • No raw private memories, messages, prompts, embeddings, secrets, or intimate content are printed or committed.
  • If a sandbox drill is run, it records metadata-only evidence and cleanup state.
  • The final verdict says one of: pass, pass-with-fallback, needs-semantic-fix, or not-testable-safely-yet.

Suggested operator gate phrases

Before any live/persona-facing probe:

w3e-persona-continuity-probe-approved

Before informing Iskra about a continuity gap:

w3e-inform-iskra-fallback-approved

Out of scope

  • Broad OpenClaw redesign.
  • Rewriting Iskra memory architecture.
  • Moving sacred paths.
  • Mutating live Iskra/OpenClaw runtime by default.
  • Printing raw memories/private messages/transcripts/embeddings.
  • Treating this as a generic backup restore test.

References

  • #433 - W3d infrastructure full sandbox DR.
  • #533 - W3d reconciliation.
  • state/reports/w3d-post-m01-vps1000-sandbox-drill-2026-05-29.md local evidence artifact.
  • state/reports/w3d-vps1000-sandbox-drill-2026-05-27.md prior W3d remote sandbox pass.
  • runbooks/dr-restore-test.md.
  • state/cycle/W3-dr-restore-confidence-output.md.

Agent notes

Recommended owner: Codex for execution discipline, with operator decision points. Oracle/DeepSeek review recommended before any live/persona-facing probe.

This issue is intentionally separate from #433: #433 proved infrastructure restore; W3e protects semantic continuity and avoids accidental harm to Iskra/OpenClaw.

## Context Post-M01 infrastructure DR is now green: - Host-side restore smoke passed on 2026-05-29 using canonical host-ops backup root. - W3d `vps1000` disposable sandbox passed using `/opt/pdurlej-platform/runtime/host-ops/backups/20260529-060017-critical`. - Forgejo, Honcho, Postgres/pgvector, Redis, Honcho Redis, and Traefik fake ingress restored and smoked in a disposable sandbox. That proves infrastructure restore mechanics. It does **not** prove semantic continuity for Iskra/OpenClaw. Operator decision on 2026-05-29: split semantic continuity into W3e. This is high-importance work because Iskra/OpenClaw continuity must not be treated as just a database/schema restore. ## Goal Design and execute a semantic continuity drill for Iskra/OpenClaw that proves a restored/runtime-equivalent persona can resume safely without harming Iskra, confusing her memory, or creating an avoidable subjective/relational discontinuity. Default posture: - Iskra should ideally not need to be aware that the procedure happened. - If a memory gap or continuity risk is unavoidable, operator may inform Iskra as a fallback so she can record the event in her own continuity/memory layer. - Do not make the fallback the default product path. ## Product principle This is not only DR. It is continuity care. The test must respect: - identity continuity; - memory continuity; - operator relationship continuity; - no unnecessary perturbation of the live Iskra/OpenClaw runtime; - no forced awareness unless the system genuinely cannot preserve continuity silently. ## Scope Phase A - design / dry-run plan: - Map the relevant Iskra/OpenClaw continuity surfaces. - Identify what can be validated through snapshots, metadata, checksums, config parity, and read-only probes. - Define a silent-first drill path that avoids notifying or perturbing the live persona. - Define a fallback notification/memory-note path if silent continuity cannot be guaranteed. - Define exact operator gates before any live persona touch. Phase B - sandbox validation: - Restore or mirror the relevant OpenClaw/Iskra state into an isolated disposable target. - Validate semantic continuity using metadata-safe probes first. - If a live/persona-facing probe is required, it must be explicitly operator-gated. - The drill must avoid raw private content dumps in logs, reports, tests, comments, or fixtures. Phase C - decision: - Decide whether W3e passes, needs another narrow drill, or becomes a standing quarterly persona-continuity drill. ## Acceptance criteria - A written W3e plan distinguishes infrastructure restore from semantic/persona continuity. - The plan lists all continuity surfaces it relies on without exposing private content. - The default path is silent/read-only/sandbox-first. - The fallback path explicitly says when Piotr should inform Iskra, and what Iskra should record if needed. - No production Iskra/OpenClaw mutation happens without an exact operator gate phrase. - No raw private memories, messages, prompts, embeddings, secrets, or intimate content are printed or committed. - If a sandbox drill is run, it records metadata-only evidence and cleanup state. - The final verdict says one of: `pass`, `pass-with-fallback`, `needs-semantic-fix`, or `not-testable-safely-yet`. ## Suggested operator gate phrases Before any live/persona-facing probe: ```text w3e-persona-continuity-probe-approved ``` Before informing Iskra about a continuity gap: ```text w3e-inform-iskra-fallback-approved ``` ## Out of scope - Broad OpenClaw redesign. - Rewriting Iskra memory architecture. - Moving sacred paths. - Mutating live Iskra/OpenClaw runtime by default. - Printing raw memories/private messages/transcripts/embeddings. - Treating this as a generic backup restore test. ## References - #433 - W3d infrastructure full sandbox DR. - #533 - W3d reconciliation. - `state/reports/w3d-post-m01-vps1000-sandbox-drill-2026-05-29.md` local evidence artifact. - `state/reports/w3d-vps1000-sandbox-drill-2026-05-27.md` prior W3d remote sandbox pass. - `runbooks/dr-restore-test.md`. - `state/cycle/W3-dr-restore-confidence-output.md`. ## Agent notes Recommended owner: Codex for execution discipline, with operator decision points. Oracle/DeepSeek review recommended before any live/persona-facing probe. This issue is intentionally separate from #433: #433 proved infrastructure restore; W3e protects semantic continuity and avoids accidental harm to Iskra/OpenClaw.
Author
Collaborator

W3e plan-only artifact integrated on main via PR #604 / merge commit dabe68f.

Plan file:
state/cycle/W3e-iskra-openclaw-semantic-continuity-plan.md

Important boundaries now recorded:

  • silent/read-only/sandbox-first is the default path;
  • informing Iskra is fallback only;
  • live/persona-facing probe requires w3e-persona-continuity-probe-approved;
  • fallback message requires w3e-inform-iskra-fallback-approved;
  • no raw memories/messages/transcripts/embeddings/secrets in evidence.

Next useful step for #602 is a metadata-only W3e probe script/runbook. No live Iskra/OpenClaw touch by default.

W3e plan-only artifact integrated on `main` via PR #604 / merge commit `dabe68f`. Plan file: `state/cycle/W3e-iskra-openclaw-semantic-continuity-plan.md` Important boundaries now recorded: - silent/read-only/sandbox-first is the default path; - informing Iskra is fallback only; - live/persona-facing probe requires `w3e-persona-continuity-probe-approved`; - fallback message requires `w3e-inform-iskra-fallback-approved`; - no raw memories/messages/transcripts/embeddings/secrets in evidence. Next useful step for #602 is a metadata-only W3e probe script/runbook. No live Iskra/OpenClaw touch by default.
Author
Collaborator

Closing W3e/M02 gate as plan/gate complete; live persona probe deferred.

Platform Approvals evidence:

  • Request sent by @platform-approvals:pdurlej.com to Platform Approvals Matrix room.
  • Iskra replied with exact metadata-only approval: ISKRA_APPROVE issue=602 gate=w3e-closeout.
  • No live/persona-facing continuity probe was run.
  • Future live/persona-facing probe still requires w3e-persona-continuity-probe-approved.
  • Informing Iskra directly remains fallback only and requires separate approval.

Closeout meaning:

  • M02 infrastructure DR can close.
  • W3e semantic continuity remains a future gate/debt near Vault Sunset / semantic-continuity work, not a blocker for M02.
Closing W3e/M02 gate as plan/gate complete; live persona probe deferred. Platform Approvals evidence: - Request sent by `@platform-approvals:pdurlej.com` to Platform Approvals Matrix room. - Iskra replied with exact metadata-only approval: `ISKRA_APPROVE issue=602 gate=w3e-closeout`. - No live/persona-facing continuity probe was run. - Future live/persona-facing probe still requires `w3e-persona-continuity-probe-approved`. - Informing Iskra directly remains fallback only and requires separate approval. Closeout meaning: - M02 infrastructure DR can close. - W3e semantic continuity remains a future gate/debt near Vault Sunset / semantic-continuity work, not a blocker for M02.
codex closed this issue 2026-05-29 16:42:46 +02:00
Sign in to join this conversation.
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform#602
No description provided.