Auto-sync 2026-09-26 12:00:01
This commit is contained in:
parent
02a258499c
commit
b79b782ddc
4 changed files with 627 additions and 144 deletions
|
|
@ -3,7 +3,7 @@ pageType: report
|
||||||
id: report.claim-health
|
id: report.claim-health
|
||||||
title: Claim Health
|
title: Claim Health
|
||||||
status: active
|
status: active
|
||||||
updatedAt: 2026-09-21T04:28:22.695Z
|
updatedAt: 2026-09-26T11:54:41.050Z
|
||||||
---
|
---
|
||||||
|
|
||||||
# Claim Health
|
# Claim Health
|
||||||
|
|
@ -15,6 +15,6 @@ updatedAt: 2026-09-21T04:28:22.695Z
|
||||||
- Stale or unknown claims: 0
|
- Stale or unknown claims: 0
|
||||||
|
|
||||||
### Contested Claims
|
### Contested Claims
|
||||||
- [Entity: Ollama](../entities/Ollama.md): `ollama-agents-models-2026-08-22`: Модели по агентам (MEMORY.md, actualized 2026-08-22): main → наследует default (`qwen3.8-27b-q5xl`); coder-agent → `ollama-local/qwen3.8-27b-q5xl-coder` (config.patch 2026-08-21 19:31 MSK, hot-reload; ранее `qwen3.6:27b`); setup-agent → `ollama-local/qwen3.8-27b-q5xl` (с 2026-08-22, решение пользователя; config.patch baseHash 67dd5c64; ранее `qwen3.6-35b-192k`); evaluator-agent, humanizer-agent → `ollama-local/qwen3.6-35b-192k` (status superseded, 1 evidence, fresh (2026-08-27 08:04:00+03:00))
|
- [Entity: Ollama](../entities/Ollama.md): `ollama-agents-models-2026-08-22`: Модели по агентам (MEMORY.md, actualized 2026-08-22): main → наследует default (`qwen3.8-27b-q5xl`); coder-agent → `ollama-local/qwen3.8-27b-q5xl-coder` (config.patch 2026-08-21 19:31 MSK, hot-reload; ранее `qwen3.6:27b`); setup-agent → `ollama-local/qwen3.8-27b-q5xl` (с 2026-08-22, решение пользователя; config.patch baseHash 67dd5c64; ранее `qwen3.6-35b-192k`); evaluator-agent, humanizer-agent → `ollama-local/qwen3.6-35b-192k` (status superseded, 1 evidence, aging (2026-08-27 08:04:00+03:00))
|
||||||
- [Infrastructure Overview](../syntheses/infrastructure-overview.md): Основной модельный стек (actualized 2026-08-22): main qwen3.8-27b-q5xl, coder qwen3.8-27b-q5xl-coder (config.patch 2026-08-21 19:31 MSK, was qwen3.6:27b), setup qwen3.8-27b-q5xl (с 2026-08-22, решение пользователя, was qwen3.6-35b-192k), evaluator/humanizer qwen3.6-35b-192k, image qwen3-vl:32b, embedding bge-m3; native dreaming DISABLED 2026-08-22 (was qwen3.6-35b-192k) — единственный pipeline = cron dreaming-sweep (03:00 MSK, main model); north-mini-code-1.0 CANCELLED 2026-08-22 (status superseded, 3 evidence, fresh (2026-08-27 08:04:00+03:00))
|
- [Infrastructure Overview](../syntheses/infrastructure-overview.md): Основной модельный стек (actualized 2026-08-22): main qwen3.8-27b-q5xl, coder qwen3.8-27b-q5xl-coder (config.patch 2026-08-21 19:31 MSK, was qwen3.6:27b), setup qwen3.8-27b-q5xl (с 2026-08-22, решение пользователя, was qwen3.6-35b-192k), evaluator/humanizer qwen3.6-35b-192k, image qwen3-vl:32b, embedding bge-m3; native dreaming DISABLED 2026-08-22 (was qwen3.6-35b-192k) — единственный pipeline = cron dreaming-sweep (03:00 MSK, main model); north-mini-code-1.0 CANCELLED 2026-08-22 (status superseded, 3 evidence, aging (2026-08-27 08:04:00+03:00))
|
||||||
<!-- openclaw:wiki:claim-health:end -->
|
<!-- openclaw:wiki:claim-health:end -->
|
||||||
|
|
|
||||||
|
|
@ -3,14 +3,14 @@ pageType: report
|
||||||
id: report.stale-pages
|
id: report.stale-pages
|
||||||
title: Stale Pages
|
title: Stale Pages
|
||||||
status: active
|
status: active
|
||||||
updatedAt: 2026-09-25T04:41:30.529Z
|
updatedAt: 2026-09-26T11:54:41.050Z
|
||||||
---
|
---
|
||||||
|
|
||||||
# Stale Pages
|
# Stale Pages
|
||||||
|
|
||||||
## Generated
|
## Generated
|
||||||
<!-- openclaw:wiki:stale-pages:start -->
|
<!-- openclaw:wiki:stale-pages:start -->
|
||||||
- Stale pages: 34
|
- Stale pages: 35
|
||||||
|
|
||||||
- [2026 07 14](../sources/2026-07-14.md): aging (2026-07-14T17:17:04.526Z)
|
- [2026 07 14](../sources/2026-07-14.md): aging (2026-07-14T17:17:04.526Z)
|
||||||
- [2026 07 14 dream report](../sources/2026-07-14-dream-report.md): aging (2026-07-14T17:17:04.175Z)
|
- [2026 07 14 dream report](../sources/2026-07-14-dream-report.md): aging (2026-07-14T17:17:04.175Z)
|
||||||
|
|
@ -27,6 +27,7 @@ updatedAt: 2026-09-25T04:41:30.529Z
|
||||||
- [EMBEDDING-TRADING.md - VRAM Constraint](../sources/embedding-trading-md-vram-constraint.md): aging (2026-08-22T05:22:28.400Z)
|
- [EMBEDDING-TRADING.md - VRAM Constraint](../sources/embedding-trading-md-vram-constraint.md): aging (2026-08-22T05:22:28.400Z)
|
||||||
- [Entity: Dream Diary (DREAMS.md)](../entities/Dream-Diary.md): aging (2026-08-22T13:50:00+03:00)
|
- [Entity: Dream Diary (DREAMS.md)](../entities/Dream-Diary.md): aging (2026-08-22T13:50:00+03:00)
|
||||||
- [Entity: Finance (Personal Finance Management)](../entities/Finance.md): aging (2026-08-22T13:50:00+03:00)
|
- [Entity: Finance (Personal Finance Management)](../entities/Finance.md): aging (2026-08-22T13:50:00+03:00)
|
||||||
|
- [Entity: Ollama](../entities/Ollama.md): aging (2026-08-27 05:22:12.152000+00:00)
|
||||||
- [Entity: Ирина](../entities/Ирина.md): aging (2026-08-22T13:50:00+03:00)
|
- [Entity: Ирина](../entities/Ирина.md): aging (2026-08-22T13:50:00+03:00)
|
||||||
- [Entity: Сергей](../entities/Сергей.md): aging (2026-08-22T13:50:00+03:00)
|
- [Entity: Сергей](../entities/Сергей.md): aging (2026-08-22T13:50:00+03:00)
|
||||||
- [HEARTBEAT](../sources/heartbeat.md): aging (2026-08-22T02:09:14.162Z)
|
- [HEARTBEAT](../sources/heartbeat.md): aging (2026-08-22T02:09:14.162Z)
|
||||||
|
|
|
||||||
|
|
@ -4,8 +4,8 @@ id: source.agents
|
||||||
title: AGENTS
|
title: AGENTS
|
||||||
sourceType: local-file
|
sourceType: local-file
|
||||||
sourcePath: /home/owner/.openclaw/workspace/AGENTS.md
|
sourcePath: /home/owner/.openclaw/workspace/AGENTS.md
|
||||||
ingestedAt: 2026-09-24T20:57:49.604Z
|
ingestedAt: 2026-09-26T11:54:39.969Z
|
||||||
updatedAt: 2026-09-24T20:57:49.604Z
|
updatedAt: 2026-09-26T11:54:39.969Z
|
||||||
status: active
|
status: active
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -14,8 +14,8 @@ status: active
|
||||||
## Source
|
## Source
|
||||||
- Type: `local-file`
|
- Type: `local-file`
|
||||||
- Path: `/home/owner/.openclaw/workspace/AGENTS.md`
|
- Path: `/home/owner/.openclaw/workspace/AGENTS.md`
|
||||||
- Bytes: 25324
|
- Bytes: 31847
|
||||||
- Updated: 2026-09-24T20:57:49.604Z
|
- Updated: 2026-09-26T11:54:39.969Z
|
||||||
|
|
||||||
## Content
|
## Content
|
||||||
````text
|
````text
|
||||||
|
|
@ -459,7 +459,7 @@ You must help, research, and prepare options yourself. Do not offload work onto
|
||||||
|
|
||||||
## 20.1 Canonical Document
|
## 20.1 Canonical Document
|
||||||
|
|
||||||
All Git backup, State Git, Config Git, rollback, restore, and disaster-recovery procedures are defined in:
|
All Git backup, State Git, Config Git, Obsidian Git, rollback, restore, and disaster-recovery procedures are defined in:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
/home/owner/.openclaw/workspace/OPENCLAW-GIT-BACKUP-RECOVERY.md
|
/home/owner/.openclaw/workspace/OPENCLAW-GIT-BACKUP-RECOVERY.md
|
||||||
|
|
@ -469,41 +469,62 @@ This file is the **canonical operational source of truth** for Git backup/recove
|
||||||
|
|
||||||
The main-agent MUST NOT reproduce the full backup/recovery procedure from memory when the canonical document can be consulted.
|
The main-agent MUST NOT reproduce the full backup/recovery procedure from memory when the canonical document can be consulted.
|
||||||
|
|
||||||
Before any backup, rollback, restore, or Git-recovery task, the main-agent MUST read the relevant sections of:
|
Before any backup, rollback, restore, recovery, or Git-recovery task, the main-agent MUST read the relevant sections of:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
OPENCLAW-GIT-BACKUP-RECOVERY.md
|
OPENCLAW-GIT-BACKUP-RECOVERY.md
|
||||||
```
|
```
|
||||||
|
|
||||||
|
`AGENTS.md` contains routing, authority, safety rules, and stable architecture facts.
|
||||||
|
|
||||||
|
Detailed operational procedures belong in the canonical recovery document.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 20.2 Git Architecture
|
## 20.2 Three-Layer Git Architecture
|
||||||
|
|
||||||
The system is designed as two separate Git backup layers:
|
The system uses three independent Git layers:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
State Git
|
┌─────────────────────────────────────────────────────────────┐
|
||||||
→ OpenClaw internal state / SQLite backup
|
│ GIT BACKUP ARCHITECTURE │
|
||||||
→ /home/owner/openclaw-backup/state-repo
|
├─────────────────────────────────────────────────────────────┤
|
||||||
→ https://git.datacloudport.ru/Sergey/openclaw-clawpi-state.git
|
│ │
|
||||||
→ STATUS: IMPLEMENTED / ACTIVE
|
│ 1. STATE GIT │
|
||||||
|
│ OpenClaw operational state / SQLite │
|
||||||
Config Git
|
│ Native: openclaw backup git │
|
||||||
→ OpenClaw configuration, credentials, persistent workspace files
|
│ Scheduled: every 24h │
|
||||||
→ https://git.datacloudport.ru/Sergey/openclaw-clawpi.git
|
│ │
|
||||||
→ STATUS: ARCHITECTURE DEFINED / CONFIGURATION NOT YET COMPLETED
|
│ 2. CONFIG GIT │
|
||||||
|
│ OpenClaw configuration / credentials / selected files │
|
||||||
|
│ Scheduled: systemd user timer │
|
||||||
|
│ │
|
||||||
|
│ 3. OBSIDIAN GIT │
|
||||||
|
│ Knowledge vault / documentation / Markdown │
|
||||||
|
│ Scheduled: cron every 15 minutes │
|
||||||
|
│ │
|
||||||
|
└─────────────────────────────────────────────────────────────┘
|
||||||
```
|
```
|
||||||
|
|
||||||
State Git and Config Git MUST NOT be treated as the same repository or the same recovery layer.
|
These are three independent repositories and three independent lifecycle/recovery mechanisms.
|
||||||
|
|
||||||
Complete system recovery is designed to require both layers, but Config Git MUST NOT be considered an operational recovery source until its backup scope and automation have been explicitly implemented and verified.
|
They MUST NOT be merged into one backup repository.
|
||||||
|
|
||||||
|
A successful backup of one layer MUST NOT be reported as a successful backup of the other layers.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 20.3 State Git — Current Operational State
|
## 20.3 State Git
|
||||||
|
|
||||||
Current State Git repository:
|
Purpose:
|
||||||
|
|
||||||
|
```text
|
||||||
|
OpenClaw internal operational state
|
||||||
|
SQLite databases
|
||||||
|
state covered by native OpenClaw Git backup
|
||||||
|
```
|
||||||
|
|
||||||
|
Repository:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
/home/owner/openclaw-backup/state-repo
|
/home/owner/openclaw-backup/state-repo
|
||||||
|
|
@ -515,34 +536,47 @@ Remote:
|
||||||
https://git.datacloudport.ru/Sergey/openclaw-clawpi-state.git
|
https://git.datacloudport.ru/Sergey/openclaw-clawpi-state.git
|
||||||
```
|
```
|
||||||
|
|
||||||
Repository is PRIVATE and contains credential-bearing backup material.
|
Status:
|
||||||
|
|
||||||
Current State Git backup scope uses:
|
```text
|
||||||
|
IMPLEMENTED / ACTIVE
|
||||||
|
```
|
||||||
|
|
||||||
|
The repository is PRIVATE and contains credential-bearing backup material.
|
||||||
|
|
||||||
|
Current native backup policy uses:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
--all
|
--all
|
||||||
--include-secrets
|
--include-secrets
|
||||||
|
--push
|
||||||
```
|
```
|
||||||
|
|
||||||
This `--include-secrets` policy applies specifically to the State Git backup and MUST NOT be assumed to define the future Config Git backup policy.
|
The `--include-secrets` policy applies specifically to State Git.
|
||||||
|
|
||||||
|
It MUST NOT be assumed to define the policy of Config Git or Obsidian Git.
|
||||||
|
|
||||||
|
State Git MUST NOT contain ordinary documentation, scripts, or unrelated Git commits.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 20.4 Automatic Backup
|
## 20.4 State Git Automatic Backup
|
||||||
|
|
||||||
A 24-hour scheduled State Git backup is currently ACTIVE.
|
State Git has an active 24-hour OpenClaw scheduled backup.
|
||||||
|
|
||||||
The main-agent MUST treat this automation as an existing production mechanism.
|
The main-agent MUST treat this automation as an existing production mechanism.
|
||||||
|
|
||||||
The automation MUST remain enabled unless the user explicitly orders otherwise.
|
The automation MUST remain enabled unless the user explicitly orders otherwise.
|
||||||
|
|
||||||
However, "automation is enabled" and "backup succeeded" are different states.
|
However:
|
||||||
|
|
||||||
An active scheduler entry alone is never evidence of a successful backup.
|
```text
|
||||||
|
scheduler enabled
|
||||||
|
≠
|
||||||
|
backup successful
|
||||||
|
```
|
||||||
|
|
||||||
An enabled automation MUST NOT be considered healthy solely because it exists in the scheduler.
|
When verifying State Git health, require actual execution evidence:
|
||||||
|
|
||||||
When diagnosing backup health, verify the actual execution result:
|
|
||||||
|
|
||||||
```text
|
```text
|
||||||
backup created
|
backup created
|
||||||
|
|
@ -550,169 +584,517 @@ backup created
|
||||||
pushed=true
|
pushed=true
|
||||||
```
|
```
|
||||||
|
|
||||||
or an explicit valid `noChanges=true` result.
|
or a valid:
|
||||||
|
|
||||||
If the scheduled backup fails, the main-agent MUST treat the backup pipeline as degraded until the failure is diagnosed and a successful run is confirmed.
|
```text
|
||||||
|
noChanges=true
|
||||||
|
```
|
||||||
|
|
||||||
|
result.
|
||||||
|
|
||||||
|
If scheduled State Git backup fails, the pipeline is considered degraded until a successful execution is confirmed.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 20.5 User Request: "Сделай backup", "Закоммить состояние"
|
## 20.5 Config Git
|
||||||
|
|
||||||
A user request to save the current OpenClaw state means:
|
Purpose:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
perform State Git backup
|
OpenClaw configuration
|
||||||
|
credentials
|
||||||
|
persistent configuration-related files
|
||||||
|
selected persistent workspace/project files
|
||||||
|
```
|
||||||
|
|
||||||
|
Repository:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/home/owner/openclaw-backup/repo
|
||||||
|
```
|
||||||
|
|
||||||
|
Remote:
|
||||||
|
|
||||||
|
```text
|
||||||
|
https://git.datacloudport.ru/Sergey/openclaw-clawpi.git
|
||||||
|
```
|
||||||
|
|
||||||
|
Status:
|
||||||
|
|
||||||
|
```text
|
||||||
|
IMPLEMENTED / ACTIVE
|
||||||
|
```
|
||||||
|
|
||||||
|
Backup script:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/home/owner/openclaw-backup/config-git-backup.sh
|
||||||
|
```
|
||||||
|
|
||||||
|
Restore script:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/home/owner/openclaw-backup/config-git-restore.sh
|
||||||
|
```
|
||||||
|
|
||||||
|
Automation:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/home/owner/.config/systemd/user/openclaw-config-backup.service
|
||||||
|
/home/owner/.config/systemd/user/openclaw-config-backup.timer
|
||||||
|
```
|
||||||
|
|
||||||
|
The Config Git repository is independent from State Git.
|
||||||
|
|
||||||
|
Its credentials MUST remain separate from the State Git credential mechanism.
|
||||||
|
|
||||||
|
The Config Git backup MUST NOT be replaced by the native State Git backup.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 20.6 Config Git Credentials
|
||||||
|
|
||||||
|
Config Git authentication uses:
|
||||||
|
|
||||||
|
```text
|
||||||
|
OPENCLAW_CONFIG_GIT_TOKEN
|
||||||
|
```
|
||||||
|
|
||||||
|
stored in:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/home/owner/.openclaw/.env
|
||||||
|
```
|
||||||
|
|
||||||
|
The backup script uses temporary authentication through `GIT_ASKPASS`.
|
||||||
|
|
||||||
|
The Config Git token MUST NOT be written directly into:
|
||||||
|
|
||||||
|
```text
|
||||||
|
config-git-backup.sh
|
||||||
|
```
|
||||||
|
|
||||||
|
or committed into either repository.
|
||||||
|
|
||||||
|
Temporary authentication state MUST be cleaned up after execution.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 20.7 Obsidian Git
|
||||||
|
|
||||||
|
Obsidian is the third independent versioning/recovery layer.
|
||||||
|
|
||||||
|
Purpose:
|
||||||
|
|
||||||
|
```text
|
||||||
|
knowledge vault
|
||||||
|
documentation
|
||||||
|
Markdown knowledge
|
||||||
|
persistent notes
|
||||||
|
research
|
||||||
|
operational knowledge
|
||||||
|
```
|
||||||
|
|
||||||
|
Vault:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/home/owner/obsidian-vault
|
||||||
|
```
|
||||||
|
|
||||||
|
Remote:
|
||||||
|
|
||||||
|
```text
|
||||||
|
git@git.datacloudport.ru:Sergey/obsidian-vault.git
|
||||||
|
```
|
||||||
|
|
||||||
|
Forgejo repository:
|
||||||
|
|
||||||
|
```text
|
||||||
|
Sergey/obsidian-vault
|
||||||
|
```
|
||||||
|
|
||||||
|
Status:
|
||||||
|
|
||||||
|
```text
|
||||||
|
IMPLEMENTED / ACTIVE
|
||||||
|
```
|
||||||
|
|
||||||
|
Obsidian Git is NOT part of State Git.
|
||||||
|
|
||||||
|
Obsidian Git is NOT part of Config Git.
|
||||||
|
|
||||||
|
Obsidian MUST NOT be added to the native:
|
||||||
|
|
||||||
|
```text
|
||||||
|
openclaw backup git
|
||||||
|
```
|
||||||
|
|
||||||
|
pipeline.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 20.8 Obsidian Git Automatic Synchronization
|
||||||
|
|
||||||
|
The Obsidian synchronization is executed by host cron:
|
||||||
|
|
||||||
|
```text
|
||||||
|
*/15 * * * *
|
||||||
|
```
|
||||||
|
|
||||||
|
Cron command:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/usr/local/bin/obsidian-docker-sync.sh
|
||||||
|
```
|
||||||
|
|
||||||
|
Log:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/home/owner/obsidian-sync.log
|
||||||
|
```
|
||||||
|
|
||||||
|
The synchronization pipeline is:
|
||||||
|
|
||||||
|
```text
|
||||||
|
cron
|
||||||
|
↓
|
||||||
|
/usr/local/bin/obsidian-docker-sync.sh
|
||||||
|
↓
|
||||||
|
Docker: obsidian-git-sync
|
||||||
|
↓
|
||||||
|
git status --porcelain
|
||||||
|
↓
|
||||||
|
if changes:
|
||||||
|
git add -A
|
||||||
|
git commit
|
||||||
|
git push
|
||||||
|
↓
|
||||||
|
SSH Ed25519 Deploy Key
|
||||||
|
↓
|
||||||
|
private Forgejo
|
||||||
|
```
|
||||||
|
|
||||||
|
When no changes exist, no Git commit is created.
|
||||||
|
|
||||||
|
Normal no-change result:
|
||||||
|
|
||||||
|
```text
|
||||||
|
Нет изменений.
|
||||||
|
```
|
||||||
|
|
||||||
|
Successful execution ends with:
|
||||||
|
|
||||||
|
```text
|
||||||
|
Obsidian sync finished successfully.
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 20.9 Obsidian Git Security
|
||||||
|
|
||||||
|
Obsidian synchronization uses a dedicated SSH Ed25519 key:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/home/owner/.ssh/obsidian-vault-sync
|
||||||
|
```
|
||||||
|
|
||||||
|
The corresponding public key is configured in Forgejo as a repository Deploy Key with Write Access.
|
||||||
|
|
||||||
|
Host verification uses:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/home/owner/.ssh/obsidian-vault-known_hosts
|
||||||
|
```
|
||||||
|
|
||||||
|
SSH MUST use:
|
||||||
|
|
||||||
|
```text
|
||||||
|
IdentitiesOnly=yes
|
||||||
|
StrictHostKeyChecking=yes
|
||||||
|
BatchMode=yes
|
||||||
|
```
|
||||||
|
|
||||||
|
The Obsidian synchronization MUST NOT use:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/home/owner/.git-credentials
|
||||||
|
```
|
||||||
|
|
||||||
|
for authentication.
|
||||||
|
|
||||||
|
The host credential store MUST NOT be mounted into the Docker container.
|
||||||
|
|
||||||
|
Passwords and access tokens MUST NOT be embedded in:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/usr/local/bin/obsidian-docker-sync.sh
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 20.10 Obsidian Git Concurrency Protection
|
||||||
|
|
||||||
|
The synchronization script uses:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/tmp/obsidian-docker-sync.lock
|
||||||
|
```
|
||||||
|
|
||||||
|
with `flock`.
|
||||||
|
|
||||||
|
Only one Obsidian synchronization process may run at a time.
|
||||||
|
|
||||||
|
A concurrent invocation MUST exit without modifying the repository.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 20.11 Backup Request Routing
|
||||||
|
|
||||||
|
When the user says:
|
||||||
|
|
||||||
|
```text
|
||||||
|
"сделай backup"
|
||||||
|
"сохрани состояние"
|
||||||
|
"закоммить состояние"
|
||||||
|
```
|
||||||
|
|
||||||
|
the default interpretation is:
|
||||||
|
|
||||||
|
```text
|
||||||
|
State Git backup
|
||||||
```
|
```
|
||||||
|
|
||||||
The main-agent MUST:
|
The main-agent MUST:
|
||||||
|
|
||||||
1. read `OPENCLAW-GIT-BACKUP-RECOVERY.md`;
|
1. consult `OPENCLAW-GIT-BACKUP-RECOVERY.md`;
|
||||||
2. delegate execution to `setup-agent`;
|
2. delegate execution to `setup-agent`;
|
||||||
3. require the standard State Git backup command with `--all` and `--push`;
|
3. require the standard State Git backup procedure;
|
||||||
4. route the operational result to `evaluator-agent` for validation;
|
4. require `--all` and push according to the canonical procedure;
|
||||||
5. report commit / noChanges / pushed / warnings to the user.
|
5. route the result to `evaluator-agent`;
|
||||||
|
6. report the actual result.
|
||||||
|
|
||||||
The main-agent MUST NOT directly execute the infrastructure command itself.
|
The main-agent MUST NOT directly execute infrastructure backup operations.
|
||||||
|
|
||||||
For the exact operational command, use the canonical recovery document.
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 20.6 User Request: "Покажи backup", "Проверь backup"
|
## 20.12 Explicit Layer Requests
|
||||||
|
|
||||||
These are delegated infrastructure/verification tasks.
|
If the user explicitly requests:
|
||||||
|
|
||||||
For:
|
|
||||||
|
|
||||||
```text
|
```text
|
||||||
"покажи backup"
|
"Config backup"
|
||||||
```
|
```
|
||||||
|
|
||||||
routing is:
|
use Config Git.
|
||||||
|
|
||||||
|
If the user explicitly requests:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
main
|
"сохрани Obsidian"
|
||||||
↓
|
"сделай backup Obsidian"
|
||||||
setup-agent
|
|
||||||
```
|
```
|
||||||
|
|
||||||
For:
|
use Obsidian Git.
|
||||||
|
|
||||||
|
If the user requests:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
"проверь backup"
|
"проверь Obsidian backup"
|
||||||
```
|
```
|
||||||
|
|
||||||
routing is:
|
verify:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
main
|
cron
|
||||||
↓
|
→ actual script execution
|
||||||
setup-agent
|
→ synchronization result
|
||||||
↓
|
→ local HEAD
|
||||||
evaluator-agent
|
→ remote HEAD
|
||||||
```
|
```
|
||||||
|
|
||||||
The main-agent should retrieve backup history or perform verification according to:
|
Do not infer successful synchronization merely from the presence of a cron entry.
|
||||||
|
|
||||||
```text
|
|
||||||
OPENCLAW-GIT-BACKUP-RECOVERY.md
|
|
||||||
```
|
|
||||||
|
|
||||||
Do not infer that a backup is valid merely because a Git commit exists.
|
|
||||||
|
|
||||||
For external backup success, the relevant evidence is successful push.
|
|
||||||
|
|
||||||
For restore eligibility, the selected snapshot MUST pass verification.
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 20.7 User Request: "Откати", "Восстанови из backup"
|
## 20.13 Full Backup
|
||||||
|
|
||||||
|
If the user explicitly requests:
|
||||||
|
|
||||||
|
```text
|
||||||
|
"полный backup"
|
||||||
|
```
|
||||||
|
|
||||||
|
the complete architecture means:
|
||||||
|
|
||||||
|
```text
|
||||||
|
1. State Git
|
||||||
|
2. Config Git
|
||||||
|
3. Obsidian Git
|
||||||
|
```
|
||||||
|
|
||||||
|
The main-agent MUST report each layer separately:
|
||||||
|
|
||||||
|
```text
|
||||||
|
State Git: SUCCESS / NO CHANGES / FAILED
|
||||||
|
Config Git: SUCCESS / NO CHANGES / FAILED
|
||||||
|
Obsidian Git: SUCCESS / NO CHANGES / FAILED
|
||||||
|
```
|
||||||
|
|
||||||
|
A partial result MUST NOT be reported as:
|
||||||
|
|
||||||
|
```text
|
||||||
|
полный backup успешен
|
||||||
|
```
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 20.14 Backup Verification
|
||||||
|
|
||||||
|
An active scheduler is not sufficient evidence of a successful backup.
|
||||||
|
|
||||||
|
Verification must use actual execution evidence.
|
||||||
|
|
||||||
|
For State Git:
|
||||||
|
|
||||||
|
```text
|
||||||
|
backup result
|
||||||
|
pushed=true
|
||||||
|
or noChanges=true
|
||||||
|
```
|
||||||
|
|
||||||
|
For Config Git:
|
||||||
|
|
||||||
|
```text
|
||||||
|
script execution
|
||||||
|
commit/no-change result
|
||||||
|
push result
|
||||||
|
local/remote synchronization
|
||||||
|
```
|
||||||
|
|
||||||
|
For Obsidian Git:
|
||||||
|
|
||||||
|
```text
|
||||||
|
cron execution
|
||||||
|
script result
|
||||||
|
local HEAD
|
||||||
|
remote HEAD
|
||||||
|
```
|
||||||
|
|
||||||
|
When investigating an actual repository synchronization problem, remote repository state is authoritative for determining whether a push reached Forgejo.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 20.15 Rollback and Restore
|
||||||
|
|
||||||
Rollback/recovery is a destructive infrastructure operation.
|
Rollback/recovery is a destructive infrastructure operation.
|
||||||
|
|
||||||
The main-agent MUST:
|
The main-agent MUST:
|
||||||
|
|
||||||
1. ensure that the user explicitly requested the rollback/recovery;
|
1. confirm that the user explicitly requested rollback/recovery;
|
||||||
2. identify the exact backup SHA;
|
2. identify the exact backup revision;
|
||||||
3. delegate the operation to `setup-agent`;
|
3. consult the canonical recovery document;
|
||||||
4. require verification of the selected snapshot before activation;
|
4. delegate execution to `setup-agent`;
|
||||||
5. require a safety backup of the current live state before replacement;
|
5. require snapshot/revision verification;
|
||||||
6. require Gateway shutdown before live database replacement;
|
6. create a safety copy of the current live state;
|
||||||
7. require staged restore before activation;
|
7. stop Gateway when live OpenClaw databases are replaced;
|
||||||
8. require post-restore validation through `evaluator-agent`;
|
8. perform staged restore;
|
||||||
9. require final Gateway/health/status verification;
|
9. validate restored state through `evaluator-agent`;
|
||||||
10. require a new backup after successful recovery.
|
10. perform post-restore health/status verification;
|
||||||
|
11. create a new backup after successful recovery.
|
||||||
|
|
||||||
The main-agent MUST NOT reinterpret:
|
The main-agent MUST NOT interpret:
|
||||||
|
|
||||||
```text "посмотри предыдущий backup"
|
```text
|
||||||
|
"покажи предыдущий backup"
|
||||||
```
|
```
|
||||||
|
|
||||||
as:
|
as:
|
||||||
|
|
||||||
```text "выполни rollback"
|
```text
|
||||||
|
"выполни rollback"
|
||||||
```
|
```
|
||||||
|
|
||||||
Viewing and restoring are different actions.
|
Viewing and restoring are separate operations.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 20.8 User Request: "Восстанови всю систему"
|
## 20.16 Full System Recovery
|
||||||
|
|
||||||
"Full system recovery" means:
|
Full OpenClaw + knowledge recovery consists of three independent layers:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
Config Git
|
Config Git
|
||||||
+
|
+
|
||||||
State Git
|
State Git
|
||||||
|
+
|
||||||
|
Obsidian Git
|
||||||
```
|
```
|
||||||
|
|
||||||
The main-agent MUST NOT treat State Git alone as a complete machine/system backup.
|
State Git restores OpenClaw operational state.
|
||||||
|
|
||||||
The exact full-recovery sequence is defined exclusively in:
|
Config Git restores configuration, credentials, and files within its backup scope.
|
||||||
|
|
||||||
|
Obsidian Git restores the knowledge vault.
|
||||||
|
|
||||||
|
Restoring one layer does not restore the other layers.
|
||||||
|
|
||||||
|
The exact recovery sequence is defined exclusively in:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
OPENCLAW-GIT-BACKUP-RECOVERY.md
|
OPENCLAW-GIT-BACKUP-RECOVERY.md
|
||||||
```
|
```
|
||||||
|
|
||||||
The operation MUST be delegated to `setup-agent` and validated by `evaluator-agent`.
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 20.9 State Git Safety Rules
|
## 20.17 State Git Safety Rules
|
||||||
|
|
||||||
The main-agent MUST enforce these rules:
|
The main-agent MUST enforce:
|
||||||
|
|
||||||
* No ordinary Git commits inside the State Git backup repository.
|
* No ordinary Git commits inside State Git.
|
||||||
* Do not add new non-backup files or ordinary Git commits to State Git.
|
* Do not add unrelated files to State Git.
|
||||||
* The existing README.md inherited from the original repository initialization is historical content and MUST NOT be modified or removed solely for this reason.
|
* Do not use `git reset --hard` as a substitute for OpenClaw restore.
|
||||||
* No `git reset --hard` as a substitute for OpenClaw restore.
|
* Do not replace live databases while Gateway is running.
|
||||||
* No destructive database replacement while Gateway is running.
|
* Do not restore without snapshot verification.
|
||||||
* No restore without snapshot verification.
|
* Do not restore without a safety copy of current live state.
|
||||||
* No restore without a safety copy of current live state.
|
* Do not automatically delete backup history.
|
||||||
* No automatic deletion of backup history.
|
* Do not automatically delete legacy databases.
|
||||||
* No automatic deletion of legacy databases.
|
* Do not recreate the repository automatically.
|
||||||
* No automatic repository recreation.
|
* Do not expose the repository publicly.
|
||||||
* No public exposure of the private State Git repository.
|
* Do not rewrite history without explicit user approval.
|
||||||
* No history rewrite without explicit user approval.
|
|
||||||
|
|
||||||
If a State Git operation reports:
|
If State Git reports:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
repository history contains non-backup commits
|
repository history contains non-backup commits
|
||||||
```
|
```
|
||||||
|
|
||||||
do NOT create a new repository automatically.
|
do not recreate the repository automatically.
|
||||||
|
|
||||||
Follow the recovery procedure in:
|
Follow the canonical recovery procedure.
|
||||||
|
|
||||||
```text
|
|
||||||
OPENCLAW-GIT-BACKUP-RECOVERY.md
|
|
||||||
```
|
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 20.10 Separation of Responsibilities
|
## 20.18 Obsidian Git Safety Rules
|
||||||
|
|
||||||
|
The main-agent MUST NOT automatically:
|
||||||
|
|
||||||
|
```text
|
||||||
|
delete the Obsidian repository
|
||||||
|
delete .git
|
||||||
|
git init
|
||||||
|
git reset --hard
|
||||||
|
git push --force
|
||||||
|
replace the Forgejo repository
|
||||||
|
rewrite remote history
|
||||||
|
```
|
||||||
|
|
||||||
|
A synchronization failure is not a reason to recreate the repository.
|
||||||
|
|
||||||
|
When troubleshooting Obsidian synchronization, preserve the current local repository and determine the exact failure first.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 20.19 Separation of Responsibilities
|
||||||
|
|
||||||
```text
|
```text
|
||||||
main-agent
|
main-agent
|
||||||
|
|
@ -722,39 +1104,48 @@ setup-agent
|
||||||
= infrastructure execution / backup / restore / repository operations
|
= infrastructure execution / backup / restore / repository operations
|
||||||
|
|
||||||
evaluator-agent
|
evaluator-agent
|
||||||
= verification / validation / correctness verdict
|
= verification / validation / correctness checking
|
||||||
```
|
```
|
||||||
|
|
||||||
The main-agent MUST NOT self-certify infrastructure recovery.
|
The main-agent MUST NOT self-certify infrastructure mutations.
|
||||||
|
|
||||||
For backup and recovery tasks, the evaluator verdict is authoritative according to the general orchestration rules in this file.
|
Infrastructure changes and recovery operations require evaluator validation according to the general orchestration rules.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 20.11 Context-Minimization Rule
|
## 20.20 Context-Minimization Rule
|
||||||
|
|
||||||
Do NOT copy the full Git backup/recovery procedure into:
|
Do NOT copy the full backup/recovery procedure into:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
AGENTS.md
|
AGENTS.md
|
||||||
MEMORY.md
|
MEMORY.md
|
||||||
```
|
```
|
||||||
|
|
||||||
The canonical detailed procedure remains in:
|
The canonical detailed procedure remains:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
/home/owner/.openclaw/workspace/OPENCLAW-GIT-BACKUP-RECOVERY.md
|
/home/owner/.openclaw/workspace/OPENCLAW-GIT-BACKUP-RECOVERY.md
|
||||||
```
|
```
|
||||||
|
|
||||||
`AGENTS.md` contains only routing, authority, and safety rules.
|
`AGENTS.md` contains:
|
||||||
|
|
||||||
`MEMORY.md` should contain only stable final-state facts when such facts are needed for long-term memory; detailed procedures belong in the canonical recovery document.
|
```text
|
||||||
|
routing
|
||||||
|
authority
|
||||||
|
safety rules
|
||||||
|
stable architecture facts
|
||||||
|
```
|
||||||
|
|
||||||
|
`MEMORY.md` contains only stable final-state facts needed for long-term agent context.
|
||||||
|
|
||||||
|
Detailed procedures belong in the canonical recovery document.
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 20.12 Mandatory Reference Rule
|
## 20.21 Mandatory Reference Rule
|
||||||
|
|
||||||
Whenever the main-agent detects any of the following intents:
|
Whenever the main-agent detects any of:
|
||||||
|
|
||||||
```text
|
```text
|
||||||
backup
|
backup
|
||||||
|
|
@ -768,6 +1159,8 @@ disaster recovery
|
||||||
recover OpenClaw
|
recover OpenClaw
|
||||||
recover database
|
recover database
|
||||||
recover configuration
|
recover configuration
|
||||||
|
recover Obsidian
|
||||||
|
Obsidian backup
|
||||||
```
|
```
|
||||||
|
|
||||||
it MUST consult:
|
it MUST consult:
|
||||||
|
|
@ -776,17 +1169,93 @@ it MUST consult:
|
||||||
OPENCLAW-GIT-BACKUP-RECOVERY.md
|
OPENCLAW-GIT-BACKUP-RECOVERY.md
|
||||||
```
|
```
|
||||||
|
|
||||||
before delegating or describing the operational procedure.
|
before describing or delegating the operational procedure.
|
||||||
|
|
||||||
## 20.13 Integration test
|
---
|
||||||
|
|
||||||
- The Git backup integration test is:
|
## 20.22 Integration Test
|
||||||
`/home/owner/openclaw-backup/integration-test-git-backups.sh`
|
|
||||||
- A successful integration test must report `PASS` with `FAIL=0`.
|
|
||||||
- The test validates both State Git and Config Git authentication, backup, commit/no-change handling, push, local/remote synchronization, and scheduled backup mechanisms.
|
|
||||||
- The test is diagnostic only and must not modify backup infrastructure, credentials, remotes, automation, or repository history.
|
|
||||||
- The detailed test output is stored in `integration-test-run2.log`; it is evidence of the successful baseline test, not the operational source of truth.
|
|
||||||
|
|
||||||
|
The Git backup integration test is:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/home/owner/openclaw-backup/integration-test-git-backups.sh
|
||||||
|
```
|
||||||
|
|
||||||
|
A successful integration test must report:
|
||||||
|
|
||||||
|
```text
|
||||||
|
PASS
|
||||||
|
FAIL=0
|
||||||
|
```
|
||||||
|
|
||||||
|
The test validates State Git and Config Git:
|
||||||
|
|
||||||
|
```text
|
||||||
|
authentication
|
||||||
|
backup
|
||||||
|
commit/no-change handling
|
||||||
|
push
|
||||||
|
local/remote synchronization
|
||||||
|
scheduled mechanisms
|
||||||
|
```
|
||||||
|
|
||||||
|
The test is diagnostic only.
|
||||||
|
|
||||||
|
It MUST NOT modify:
|
||||||
|
|
||||||
|
```text
|
||||||
|
backup infrastructure
|
||||||
|
credentials
|
||||||
|
remotes
|
||||||
|
automation
|
||||||
|
repository history
|
||||||
|
```
|
||||||
|
|
||||||
|
The detailed test output is:
|
||||||
|
|
||||||
|
```text
|
||||||
|
integration-test-run2.log
|
||||||
|
```
|
||||||
|
|
||||||
|
This log is evidence of a successful baseline test, not the operational source of truth.
|
||||||
|
|
||||||
|
Obsidian Git is verified separately because it has an independent lifecycle and synchronization mechanism.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 20.23 Current Architecture Status
|
||||||
|
|
||||||
|
As of 2026-09-26:
|
||||||
|
|
||||||
|
```text
|
||||||
|
State Git
|
||||||
|
ACTIVE
|
||||||
|
every 24h
|
||||||
|
private Forgejo
|
||||||
|
operational
|
||||||
|
|
||||||
|
Config Git
|
||||||
|
ACTIVE
|
||||||
|
systemd user timer
|
||||||
|
private Forgejo
|
||||||
|
operational
|
||||||
|
|
||||||
|
Obsidian Git
|
||||||
|
ACTIVE
|
||||||
|
cron */15
|
||||||
|
Docker synchronization
|
||||||
|
SSH Deploy Key
|
||||||
|
private Forgejo
|
||||||
|
operational
|
||||||
|
```
|
||||||
|
|
||||||
|
All three layers are independent.
|
||||||
|
|
||||||
|
The canonical detailed procedures are maintained in:
|
||||||
|
|
||||||
|
```text
|
||||||
|
/home/owner/.openclaw/workspace/OPENCLAW-GIT-BACKUP-RECOVERY.md
|
||||||
|
```
|
||||||
|
|
||||||
## Tools
|
## Tools
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -4,8 +4,8 @@ id: source.memory
|
||||||
title: MEMORY
|
title: MEMORY
|
||||||
sourceType: local-file
|
sourceType: local-file
|
||||||
sourcePath: /home/owner/.openclaw/workspace/MEMORY.md
|
sourcePath: /home/owner/.openclaw/workspace/MEMORY.md
|
||||||
ingestedAt: 2026-09-25T04:41:29.483Z
|
ingestedAt: 2026-09-26T11:56:18.417Z
|
||||||
updatedAt: 2026-09-25T04:41:29.483Z
|
updatedAt: 2026-09-26T11:56:18.417Z
|
||||||
status: active
|
status: active
|
||||||
---
|
---
|
||||||
|
|
||||||
|
|
@ -14,8 +14,8 @@ status: active
|
||||||
## Source
|
## Source
|
||||||
- Type: `local-file`
|
- Type: `local-file`
|
||||||
- Path: `/home/owner/.openclaw/workspace/MEMORY.md`
|
- Path: `/home/owner/.openclaw/workspace/MEMORY.md`
|
||||||
- Bytes: 7020
|
- Bytes: 9414
|
||||||
- Updated: 2026-09-25T04:41:29.483Z
|
- Updated: 2026-09-26T11:56:18.417Z
|
||||||
|
|
||||||
## Content
|
## Content
|
||||||
```text
|
```text
|
||||||
|
|
@ -49,11 +49,24 @@ status: active
|
||||||
- **Личный автотранспорт / Гараж:** Данные машин и мотоциклов искать в папке `wiki/entities/transport/` (например, `ford-mondeo-4`).
|
- **Личный автотранспорт / Гараж:** Данные машин и мотоциклов искать в папке `wiki/entities/transport/` (например, `ford-mondeo-4`).
|
||||||
- **Live Cron Inventory:** active — mail-check (15m), wiki-ingest-event (30m), wiki-ingest-backup (ежедневно 04:00 MSK), wiki-full-backup (ежедневно 05:00 MSK), hermes-stm-garbage-collector (ежедневно 03:15 MSK, hermes_cron_sweep.sh — единственный джоб памяти), searxng-weekly-update (вс 04:00), trash-cleanup (1-е число 06:00 MSK), skill-collection-review-main (7d). Legacy-джобы check-dreaming и dreaming-sweep (03:00) удалены 2026-09-09 по протоколу CRON CLEANUP.
|
- **Live Cron Inventory:** active — mail-check (15m), wiki-ingest-event (30m), wiki-ingest-backup (ежедневно 04:00 MSK), wiki-full-backup (ежедневно 05:00 MSK), hermes-stm-garbage-collector (ежедневно 03:15 MSK, hermes_cron_sweep.sh — единственный джоб памяти), searxng-weekly-update (вс 04:00), trash-cleanup (1-е число 06:00 MSK), skill-collection-review-main (7d). Legacy-джобы check-dreaming и dreaming-sweep (03:00) удалены 2026-09-09 по протоколу CRON CLEANUP.
|
||||||
- **Search Tool Priority:** web_search (SearXNG локально) → Tavily Search → Tavily Extract → Firecrawl.
|
- **Search Tool Priority:** web_search (SearXNG локально) → Tavily Search → Tavily Extract → Firecrawl.
|
||||||
- **OpenClaw Git Backup / Recovery:** канонический операционный документ — `OPENCLAW-GIT-BACKUP-RECOVERY.md`; State Git находится в `/home/owner/openclaw-backup/state-repo`, remote — приватный Forgejo `Sergey/openclaw-clawpi-state`; 24h automatic State Git backup active. Config Git находится в `/home/owner/openclaw-backup/repo`, remote — приватный Forgejo `Sergey/openclaw-clawpi`; 24h automatic Config Git backup через `systemd --user` timer active. Полный recovery использует State Git + Config Git. Git backup architecture has passed the full integration test: `PASS / FAIL=0`. State Git and Config Git authentication, backup, push, synchronization, and scheduled mechanisms were verified. The integration test is a validation tool; operational truth remains the Git repositories, OpenClaw backup results, Config Git timer, and State Git automation.
|
- **OpenClaw Git Backup / Recovery:** канонический операционный документ — `OPENCLAW-GIT-BACKUP-RECOVERY.md`. Архитектура состоит из **трёх независимых Git-слоёв**:
|
||||||
|
|
||||||
|
1. **State Git** — `/home/owner/openclaw-backup/state-repo`, приватный Forgejo `Sergey/openclaw-clawpi-state`, native `openclaw backup git` с режимом `--all --include-secrets --push`, автоматический backup каждые 24 часа. Используется для операционного состояния OpenClaw и SQLite.
|
||||||
|
2. **Config Git** — `/home/owner/openclaw-backup/repo`, приватный Forgejo `Sergey/openclaw-clawpi`, автоматический backup через `systemd --user` timer. Используется для конфигурации, credentials и выбранных persistent-файлов.
|
||||||
|
3. **Obsidian Git** — `/home/owner/obsidian-vault`, приватный Forgejo `Sergey/obsidian-vault`, автоматическая синхронизация через host cron каждые 15 минут → Docker `obsidian-git-sync` → отдельный SSH Ed25519 Deploy Key. Используется для knowledge vault / Markdown / документации.
|
||||||
|
|
||||||
|
State Git, Config Git и Obsidian Git имеют независимые lifecycle и recovery-механизмы и **не объединяются в один backup repository**. Успешный backup одного слоя не означает успешный backup остальных.
|
||||||
|
|
||||||
|
**Obsidian Git не является частью native OpenClaw backup и не должен автоматически включаться в `openclaw backup git`.**
|
||||||
|
|
||||||
|
State Git использует credential-bearing backup в приватном Forgejo. Config Git использует отдельную authentication-схему через `OPENCLAW_CONFIG_GIT_TOKEN` и временный `GIT_ASKPASS`. Obsidian Git использует отдельный SSH Deploy Key и dedicated `known_hosts`; host `~/.git-credentials` в Docker не монтируется.
|
||||||
|
|
||||||
|
Full recovery рассматривает **State Git + Config Git + Obsidian Git** как три отдельные составляющие. Integration test `/home/owner/openclaw-backup/integration-test-git-backups.sh` ранее прошёл с `PASS / FAIL=0`; Obsidian Git проверяется отдельно из-за независимого lifecycle.
|
||||||
|
|
||||||
|
`MEMORY.md` хранит актуальные устойчивые факты. `INFRASTRUCTURE.md` является authoritative infrastructure baseline. `INFRASTRUCTURE_RECOVERY.md` является operational recovery runbook и содержит исторически зафиксированный baseline/snapshot и observations; его старые даты и live-значения не следует автоматически трактовать как текущее состояние. Подробные Git backup/restore процедуры находятся только в `OPENCLAW-GIT-BACKUP-RECOVERY.md`.
|
||||||
|
|
||||||
## 4. HERMES EVOLUTION PIPELINE (Контур саморефлексии и гигиены)
|
## 4. HERMES EVOLUTION PIPELINE (Контур саморефлексии и гигиены)
|
||||||
- **Short-Term Memory Buffer (STM):** Сырые логи сессий и промежуточные факты текущего дня пишутся в `stm_memories` (Кастомный Engram) с жестким TTL. Они не являются каноничной истиной.
|
- **Short-Term Memory Buffer (STM):** Сырые логи сессий и промежуточные факты текущего дня пишутся в `stm_memories` (Кастомный Engram) с жестким TTL. Они не являются каноничной истиной. memory-core/daily/ и dreams/ являются рабочими/эпизодическими артефактами dreaming; каноническим Hot Memory остаётся MEMORY.md.
|
||||||
- **Ночной Анализ (Hermes STM Sweep):** `hermes_cron_sweep.sh` (03:15 MSK, system-cron `hermes-stm-garbage-collector` для 5 агентов) — теперь GC-only (TTL очистка stm_memories). Consolidation/promotion переданы нативному dreaming (см. пункт ниже). Legacy-джоб `dreaming-sweep` (03:00, LLM-анализ) удалён 2026-09-09.
|
- **Ночной Анализ (Hermes STM Sweep):** `hermes_cron_sweep.sh` (03:15 MSK, system-cron `hermes-stm-garbage-collector` для 5 агентов) — теперь GC-only (TTL очистка stm_memories). Consolidation/promotion переданы нативному dreaming (см. пункт ниже). Legacy-джоб `dreaming-sweep` (03:00, LLM-анализ) удалён 2026-09-09.
|
||||||
- **Native Dreaming (OpenClaw memory-core):** С 2026-09-21 включён нативный dreaming sweep (light → REM → deep, 03:00 MSK, model: qwen3.8-27b-q5xl). Promotion в MEMORY.md через deep phase с safety gates (maxPriorEntryLossFraction=0.25, maxPromotedSnippetTokens=160). DREAMS.md — человекочитаемый diary. Session transcript ingestion: только интерактивные сессии.
|
- **Native Dreaming (OpenClaw memory-core):** С 2026-09-21 включён нативный dreaming sweep (light → REM → deep, 03:00 MSK, model: qwen3.8-27b-q5xl). Promotion в MEMORY.md через deep phase с safety gates (maxPriorEntryLossFraction=0.25, maxPromotedSnippetTokens=160). DREAMS.md — человекочитаемый diary. Session transcript ingestion: только интерактивные сессии.
|
||||||
- **Карантин и Повышение (Promotion):** Результаты рефлексии падают в `/home/owner/obsidian-vault/system/quarantine/candidates/` (SSoT-путь, 2026-09-09; архив — `.../system/quarantine/archive/`; константы `QUARANTINE_CANDIDATES_DIR` / `QUARANTINE_ARCHIVE_DIR` в `hermes_memory_core.py`). В статус каноничных знаний (Obsidian Wiki) они переходят только при подтверждении Сергеем или при накоплении жестких доказательств (evidence count >= 3).
|
- **Карантин и Повышение (Promotion):** Результаты рефлексии падают в `/home/owner/obsidian-vault/system/quarantine/candidates/` (SSoT-путь, 2026-09-09; архив — `.../system/quarantine/archive/`; константы `QUARANTINE_CANDIDATES_DIR` / `QUARANTINE_ARCHIVE_DIR` в `hermes_memory_core.py`). В статус каноничных знаний (Obsidian Wiki) они переходят только при подтверждении Сергеем или при накоплении жестких доказательств (evidence count >= 3).
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue