obsidian-vault/sources/memory-md-persistent-system-state.md
2026-09-20 20:40:46 +03:00

524 lines
30 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

---
pageType: source
id: source.memory-md-persistent-system-state
title: MEMORY.md - Persistent System State
sourceType: local-file
sourcePath: /home/owner/.openclaw/workspace/MEMORY.md
ingestedAt: 2026-08-22T04:20:49.788Z
updatedAt: 2026-08-22T04:20:49.788Z
status: active
---
# MEMORY.md - Persistent System State
## Source
- Type: `local-file`
- Path: `/home/owner/.openclaw/workspace/MEMORY.md`
- Bytes: 30416
- Updated: 2026-08-22T04:20:49.788Z
## Content
````text
### Nextcloud Sync Folder (2026-07-19)
- **Local path:** /home/owner/.openclaw/workspace/arno.nextcloud
- **Purpose:** основной канал обмена файлами между Сергеем и Арно (через синхронизацию с Nextcloud)
- **Sync:** автоматическая, через nextcloud-aio-oc
### Telegram Bot — configuration (04.06.2026)
- **Name:** Cl
- **Bot ID:** 8788956736
- **Username:** @clawpi_01_bot
- **User Chat ID:** 862485388
### Network Fix
- **Problem:** Telegram API resolves to IPv6 (2001:67c:4e8:f004::9), Pi has no IPv6 routing
- **Fix:** export NODE_OPTIONS="--dns-result-order=ipv4first" added to /etc/environment
- **Gateway restart:** sudo systemctl --user restart openclaw-gateway
- **Status:** ✅ fixed
### Mail Check — Dedup & State (UID-баг РЕШЁН, 2026-08-16)
- **Решение UID-бага (2026-08-10):** дедупликация новых писем ведётся по **Message-ID** (fallback: sha1(date|from|subject)); зависимость от динамических UID Beget IMAP устранена.
- **mail_detect.py переписан (2026-08-16):** режимы `--trigger` (JSON {fire, message} на stdout, для cron trigger) и `--debug` (dry-run). Fetch с `mark_seen=False` — Unread-флаг НЕ обнуляется. Любые ошибки IMAP → fire:false, exit 0.
- **State:** `skills/nextcloud-aio-oc/state/mail_seen.json` (cap 1000, переживает ребут; bootstrap 16 писем сделан 2026-08-16). НЕ удалять.
- **mail.py — 2 точечных фикса (2026-08-16):** cmd_check → mark_seen=False; load_account → тот же env-chain пароля. Остальное не менялось.
- **Env-chain пароля IMAP:** `IMAP_PASS_ARN → IMAP_PASS → NEXTCLOUD_MAIL_PASS` (рабочая: IMAP_PASS; уже в /etc/environment и env gateway). User/host fallback: IMAP_USER/IMAP_HOST.
### Ford Mondeo 4 — Автомобиль (2026-08-01)
- **Модель:** Ford Mondeo 4 (2011), бензин 2.0 л, 145 л.с.
- **Оформление:** на жену — Ирина
- **Текущий пробег:** 296 300 км (2026-08-01)
- **Интервал ТО:** 10 000 км (сокращённый, по решению пользователя)
- **Последнее ТО:** 2026-08-01 — замена моторного масла и масляного фильтра (Пропег / Propel), пробег 296 300 км
- **Следующее ТО:** ~306 000 км, ориентир ~февраль 2027
### Memory Search Configuration (2026-06-17)
- **enabled:** true
- **provider:** ollama (ollama-local)
- **model:** bge-m3
- **remote.baseUrl:** http://192.168.1.200:11434
- **embedding vector dims:** 1024
- **storage:** ~/.openclaw/agents/{agent-id}/agent/openclaw-agent.sqlite (main, coder-agent, evaluator-agent, humanizer-agent, setup-agent)
- **Cleanup (2026-08-17):** legacy ~/.openclaw/memory/*.sqlite.migrated (5 × ~5MB) удалены — путь хранения см. выше
- **index:** 1 file / 8 chunks indexed per agent (MEMORY.md source)
- **all agents:** Embeddings ready, Vector store ready, Semantic vectors ready ✅
- **Note:** OpenClaw CLI `openclaw memory index` runs on Pi but embedding API needs Dell Precision Ollama (192.168.1.200:11434). Gateway process uses config baseUrl correctly.
### AI Models (Actualized 2026-08-21)
- **agents.defaults.model.primary:** `ollama-local/qwen3.8-27b-q5xl`
- **agent.models:**
- main → inherits default: `ollama-local/qwen3.8-27b-q5xl`
- coder-agent → `ollama-local/qwen3.8-27b-q5xl-coder`
- evaluator-agent → `ollama-local/qwen3.6-35b-192k`
- humanizer-agent → `ollama-local/qwen3.6-35b-192k`
- setup-agent → `ollama-local/qwen3.6-35b-192k`
- **imageModel.defaults.primary:** `ollama-local/qwen3-vl:32b`
- **memorySearch.model:** `bge-m3` (embedding, not generative)
- **dreaming model (config memory-core):** `ollama-local/qwen3.6-35b-192k`
### Discord Bot (2026-06-21) — ⚠️ BLOCKED
- **Token:** configured in openclaw.json channels.discord.token
- **Guild:** 1518244752967864330
- **Plugin:** enabled (discord)
- **Skill:** enabled (discord)
- **Problem:** Raspberry Pi cannot reach Discord API — connection timeout to 162.159.x.x subnet
- **Reason:** ISP/router blocks Discord traffic from home network
- **Fix needed:** Run bot on VPS or fix DNS/routing for Discord
- **Status:** ⚠️ blocked by network
### Systemd Unit — /etc/environment binding (2026-06-12)
- **Problem:** systemd does not read /etc/environment — it's a PAM file, triggered upon login, not for systemd services.
- **Fix:** Added `EnvironmentFile=/etc/environment` to the [Service] section of the openclaw-gateway.service unit.
- **Command:** `systemctl --user edit --force --full openclaw-gateway.service` (created a new unit).
- **Then:** `systemctl --user daemon-reload` + `systemctl --user restart openclaw-gateway`
- **Result:** All vars from /etc/environment are visible to the gateway process.
## Search Tool Priority
Search priority:
web_search (provider: SearXNG локально) → Tavily Search → Tavily Extract → Firecrawl Search/Scrape.
Use:
- web_search for quick lookup;
- Tavily for high-quality search, news, time/domain filtering;
- Tavily Extract for article/page extraction;
- Firecrawl only for JS-heavy or difficult pages;
- web_fetch only for simple URL retrieval.
Always choose the lightest tool that can solve the task.
### SearXNG — локальный web_search (2026-08-21)
- **Provider:** `tools.web.search.provider: "searxng"` (в openclaw.json)
- **Плагин:** @openclaw/searxng-plugin v2026.7.1 (enabled)
- **Базовый URL:** `plugins.entries.searxng.config.webSearch.baseUrl: "http://127.0.0.1:8888"`
- **Контейнер:** `searxng` (searxng/searxng:latest), --restart unless-stopped, порт **127.0.0.1:8888:8080** (только локально)
- **Конфиг:** /home/owner/searxng/settings.yml (600): use_default_settings, secret_key (hex24), limiter: false, formats [html, json]
- **Docker:** docker.io 26.1.5, enabled+running; доступ через `sudo docker` (owner не в docker-группе — осознанно)
- **E2E:** PASS (evaluator + main-agent, 2026-08-21): JSON API живёт, web_search работает через searxng
- **Автообновление:** cron "searxng-weekly-update" (воскресенье 04:00 MSK): isolated agentTurn → /home/owner/searxng/update.sh (pull :latest; digest не изменился → контейнер не трогать; изменился → recreate + verify JSON API). Лог: /home/owner/searxng/update.log. Delivery: announce → telegram:862485388
- **Остатки:** /home/owner/searxng/app/ удалены 2026-08-21
## Configuration Management
### Files
- **CHANGELOG.md** — change history. Each significant infrastructure change → record (created 2026-06-11).
- **MEMORY.md** — persistent system state (infrastructure, models, bot, settings). Not history, but final state.
- **AGENTS.md** — routing and orchestration policy. Does not contain settings.
- **Wiki vault** (`/home/owner/obsidian-vault`) — structured entities from MEMORY.md + CHANGELOG.md.
### Vault state (2026-08-18)
- memory-wiki: vaultMode=bridge, ingest.autoCompile=true, render.createDashboards=true, search.backend=shared, search.corpus=all, context.includeCompiledDigestPrompt=true
- memory-core: /home/owner/.openclaw/workspace/memory-core/ (daily/, dreams/, inbox/, index.md)
- dreaming: enabled=true, frequency 0 3 * * * (03:00 MSK), model=ollama-local/qwen3.6-35b-192k, timezone=Europe/Moscow
- wiki: 183 sources, 10 entities, 11 concepts, 3 syntheses, 10 reports (2026-08-19)
- wiki lint: legacy warnings — reports/lint.md
- last ingest: 2026-08-19 11:07 MSK (event-driven; AGENTS.md, MEMORY.md, EMBEDDING-TRADING.md)
- bridge: 149 artifacts exported
- wiki_apply remains primary mechanism for creating/updating structured content
- known bug: bridge import syncs 0 artifacts (GH issue #65698) — manual wiki ingest + wiki_apply needed.
### Heartbeat (main agent)
- **Heartbeat DISABLED** (2026-08-18, user decision); mail check now handled solely by cron "mail-check".
- **Config:** agents.list[0].heartbeat.every = "0m" in openclaw.json
- Отчёт daily 9:00 (check-email-daily) — ОТМЕНЁН 2026-08-16, НЕ восстанавливать
### Cron Jobs — Mail & Heartbeat (Actualized 2026-08-18 MSK)
- **mail-check** (id 81689c8a-f1a4-4c0d-bb23-d096775a75bb, every 15m, session=isolated, NATIVE TRIGGER-СКРИПТ): trigger = `skills/nextcloud-aio-oc/scripts/mail_check_trigger.mjs` → `python3 .../mail_detect.py --trigger` → JSON {fire, message}. fire:false → модель НЕ запускается, в Telegram ничего не уходит (ошибки IMAP тоже → fire:false, exit 0). fire:true → LLM agentTurn (timeout 300s): новые письма читать через `mail.py get UID`, суть/класс/важность, вложения-картинки → vision, ОДНО сообщение в Telegram на русском. Delivery: announce → telegram:862485388.
- **heartbeat** (main agent): DISABLED (2026-08-18, every="0m"); больше не работает.
- **Удалено/отменено:** mail-detect (50c4362c, пароль был в промпте) и mail-analyze (bef0b684) — удалены 2026-08-16; mail-daily-report-9am — НЕ возвращён (решение пользователя); legacy /tmp-файлы (last_seen_uids.json, mail_pattern_log.json, mail_new.json, mail_analyze_pending) удалены.
- **Status:** ✅ работает; evaluator-agent PASS 13/13 (единственный finding — неверный fallback в промпте джоба — исправлен: `mail.py check --folder INBOX`)
### Sudo & Secrets (actualized 2026-08-21)
- **File:** /etc/sudoers.d/owner (440, backup: owner.bak)
- **Content:** `owner ALL=(ALL) NOPASSWD: /usr/b…ctl, /usr/bin/journalctl, /usr/bin/apt, /usr/bin/apt-get, /usr/sbin/usermod, /usr/bin/docker`
- **Пароль owner:** `/home/owner/.openclaw/secrets/OWNER_PASS` (600, 6 байт) — решение Сергея 13:02: держать в доступе агента. НЕ в /etc/environment, НЕ в MEMORY.md (sync в Nextcloud/Obsidian).
- **Purpose:** setup-agent работает с apt/docker без повторного ввода пароля
- **Audit trail:** all infra changes logged in CHANGELOG.md + MEMORY.md
### Agent Boundaries
- **main-agent:** routing, planning, coordination, status reporting only
- **setup-agent:** infrastructure (systemd, /etc/, packages, networking, firewall) — has NOPASSWD sudo
- **coder-agent:** implementation, code, scripting
- **evaluator-agent:** validation, audit, correctness checks
- **humanizer-agent:** text rewriting, tone, readability
- **No agent may self-certify changes** — evaluator validates all infra mutations
- **All infra changes require CHANGELOG.md entry + MEMORY.md update + wiki compile**
### Change workflow
- Infra/config changes → delegate to setup-agent (per AGENTS.md routing)
- Agent MUST update CHANGELOG.md after infra changes
- Agent MUST update MEMORY.md with final state only (not history)
- All files loaded at session start via project context
- No agent may self-certify changes; evaluator-agent validates infra mutations
### Wiki Ingestion (event-driven, per AGENTS.md §16)
- Main-agent checks wiki sources before every reply
- If sources changed → auto-spawn setup-agent subagent for wiki ingest + apply + compile + lint
- Sources: USER.md, MEMORY.md, AGENTS.md, SOUL.md, IDENTITY.md, TOOLS.md, EMBEDDING-TRADING.md
- No cron — purely event-driven
- Setup-agent MUST create/update entities, concepts, syntheses from sources
- Setup-agent MUST update CHANGELOG.md after wiki mutations
### Cron Jobs (routing policy reminder — 2026-06-12)
- **CRITICAL:** Cron config changes = infrastructure task → delegate to setup-agent (AGENTS.md §5.1)
- Main-agent MUST NOT modify cron jobs directly
- Violation example: main-agent updated check-dreaming delivery manually on 2026-06-12
- Future cron changes → setup-agent only
## Agent Behavior Rules
### Cron Management Protocol (Actualized 2026-07-03)
- Тайное или автоматическое создание скрытых cron-задач без ведома пользователя ЗАПРЕЩЕНО (Удалено старое конфликтное правило от 2026-06-11).
- Если требуется отложенная проверка системы, агент обязан сформулировать задачу, запросить явное текстовое согласие пользователя в чате, после чего делегировать создание задачи для `setup-agent`.
### Rule Creation (2026-06-11)
- If the agent decides that a new rule needs to be created or an existing one modified, it formulates the rule and requests the user's permission to write it.
- Does not make changes to MEMORY.md / AGENTS.md without the user's explicit consent.
- Upon approval, it writes the final state to MEMORY.md and updates CHANGELOG.md.
## Email Addresses
- **Arno (Agent):** arno@eurostela.ru (via Beget)
- **Sergey (Owner):** sergey@eurostela.ru
## Nextcloud Mail
- **Account:** arno@eurostela.ru
- **IMAP:** ://beget.com (SSL)
- **SMTP:** ://beget.com (SSL)
- **Script:** /home/owner/.openclaw/workspace/skills/nextcloud-aio-oc/scripts/mail.py
- **Capabilities:** inbox, get, send, reply, folders, search, delete
- **Status:** connected ✅
- **Password (IMAP):** env-chain `IMAP_PASS_ARN → IMAP_PASS → NEXTCLOUD_MAIL_PASS` (рабочая: IMAP_PASS; /etc/environment + env gateway). User/host fallback: IMAP_USER/IMAP_HOST
### Email Behavior Rule (2026-06-17) (v2.0)
- **1. Deleting a specific message (by UID):** MOVE from INBOX to Trash folder via UID MOVE. DO NOT use `\Deleted` + EXPUNGE to avoid data loss. Verify removal from INBOX.
- **2. Clearing the INBOX:** MOVE all UIDs to Trash in batches of 500-1000. Verify INBOX (EXISTS) = 0. Roll back completely on error.
- **3. Clearing the Trash:** Require strict explicit user confirmation. Set `\Deleted` flag + EXPUNGE. Verify Trash is empty (EXISTS = 0). Log counts to CHANGELOG.
### Email Script Fix (2026-06-17)
- `mail.py` — fixed `\Deleted` escape in IMAP STORE command; added `--all` support for `cmd_delete`.
### Email Script Update (2026-07-26)
- `mail.py` — all commands now support `--folder <folder>` parameter (inbox, get, search, delete, reply). Default: "INBOX" for backward compatibility.
- All commands use UID-based API (`m.uid('FETCH')`, `m.uid('STORE')`) instead of sequence-based for Trash/Junk compatibility with Beget IMAP.
- Added reference doc: `/home/owner/.openclaw/workspace/skills/nextcloud-aio-oc/docs/mail-py-reference.md`
### Mail.py multipart Fix (2026-08-03)
- `mail.py` — функция `get_text_body()` теперь рекурсивно обрабатывает вложенные multipart/alternative структуры (Gmail вложенные контейнеры).
- Письма с картинками внутри вложений извлекаются корректно.
### Mail Photo Attachments Handling (2026-08-03) v2
- **Правило:** Когда в письме есть вложение-картинка (image/jpeg, image/png и т.д.) → сохранить файл на диск, затем проанализировать через `ollama-local/qwen3-vl:32b` (vision model).
- **Где сохранять:** `/home/owner/.openclaw/workspace/skills/nextcloud-aio-oc/tmp/mail_<UID>_<filename>`
- **Процесс:** 1) imap fetch UID (RFC822), 2) найти part с image/ Content-Type, 3) decode payload, 4) write binary to tmp, 5) vision model analysis.
- **Решение о выдаче (v2):** Не показывать результат анализа автоматически. Сначала проанализировать — если на фото есть полезная информация (координаты, текст, документы, данные) → выдать в чат. Если картинка бессмысленная (интерфейс, скриншот без данных, подпись, decorative image) → не показывать результат, просто сохранить файл.
### Beget IMAP Limitations (verified 2026-08-17)
- **Баточный UID MOVE не работает:** `UID MOVE 119 120 INBOX.Trash` → сервер отвечает `NO` ("Client tried to access nonexistent namespace") — даже с корректным префиксом INBOX. 2026-08-17 20:26 ранее наблюдался silent no-op (OK, но ничего не перенеслось). Одно-UID MOVE работает стабильно (подтверждено дважды 2026-08-17: UID 119, 120). Вывод: перенос/удаление — только по одному UID за команду (mail.py delete так и работает).
- **SEARCH SUBJECT не парсится:** `UID SEARCH SUBJECT "текст"` → `BAD: Unknown argument TEST`. Для поиска по теме — client-side фильтрация.
- **Имена папок:** всегда с префиксом `INBOX.` (INBOX.Trash, INBOX.Junk, INBOX.Sent); "Trash" без префикса → NO. В mail.py добавлена `_normalize_folder()` (2026-08-17).
### Email Decision (2026-07-26)
- **Decision:** Keep `mail.py` as utility for cron and automation — confirmed by user.
- Rationale: provides JSON output, cron integration (`check-email-daily`), and standardized access to all folders (INBOX, Trash, Junk, Sent, Drafts).
- All commands now support `--folder <folder>` parameter with UID-based API (m.uid('FETCH'), m.uid('STORE')) for Trash/Junk compatibility.
### Mail Check Cron
- Mail check теперь через cron **mail-check** (every 15m, trigger-скрипт) — см. секцию "Cron Jobs — Mail & Heartbeat". Отчёт в 9:00 (mail-daily-report-9am) отменён, не восстанавливается.
## Nextcloud AIO (2026-06-14)
- **Skill:** nextcloud-aio-oc (installed in workspace/skills/nextcloud-aio-oc)
- **URL:** https://datacloudport.ru
- **User:** Arno
- **Auth:** Basic Auth (NEXTCLOUD TOKEN account password)
- **Timezone:** Europe/Moscow
- **Status:** ✅ connected — OCS API + Notes list + WebDAV all working
- **Env:** /etc/environment (NEXTCLOUD_URL, NEXTCLOUD_USER, NEXTCLOUD_TOKEN, NEXTCLOUD_TIMEZONE)
- **Capabilities:** Notes, Tasks, Calendar (CalDAV), Files (WebDAV), Contacts (CardDAV)
- **Office libraries:** python-docx 0.8.11, openpyxl 3.1.5, python-pptx 1.0.2, reportlab 4.4.4, pypdf 5.6.0
- Fully supports .docx/.xlsx/.pptx files (read/edit/create)
- PDF reading and editing
- **Contacts:** 13 entries (8 user, 5 system)
- **OCS fix (2026-06-14):** OCS API returns 412 without `OCS-APIRequest: true` header (Nextcloud 30+ CSRF protection). Added to bundled request() function in nextcloud.js — all OCS endpoints now return 200. WebDAV unaffected.
- **Warning:** fix applied to compiled bundle; will be lost if skill is updated or reinstalled.
### Nextcloud Behavior Rule (2026-06-15)
- When a user requests an action with "Nextcloud" without specifying an account, immediately use Arno's account on datacloudport.ru without asking for confirmation or clarification.
### WordPress — Eurostela.ru (2026-06-15)
- **URL:** https://eurostela.ru
- **Тип:** WordPress (3+ года), Elementor + ACF
- **Пользователь:** Arno, role: editor
- **Application Password:** arno — LwZFmiWyCrhPHlUwAShq7qFD (имя: Arno-API)
- **API endpoint:** https://eurostela.ru/wp-json/wp/v2/
- **Статус:** ✅ Connected, REST API is working, authorization completed
- **Категория по умолчанию:** "User information" (id=100)
- **Назначение:** content, SEO optimization, website promotion
### WooCommerce REST API — Eurostela.ru (2026-06-24) ⚠️ ЧАСТИЧНО УСТАРЕЛО
- **API base:** https://eurostela.ru/wp-json/wc/v3/
- **Consumer Key:** `ck_6ae9d729f33e1672ffed8bd41c042b14db74aabf`
- **Consumer Secret:** в окружении `WOOCOMMERCE_API_SECRET` (не разглашать)
- **Auth:** Basic Auth (key:secret) — обязательны оба ключа
- **Пример запроса:**
- Поиск по SKU: `GET /wc/v3/products?sku=MR-038`
- Список товаров: `GET /wc/v3/products?per_page=10&orderby=date&order=desc`
- Один товар: `GET /wc/v3/products/{id}`
- **SKU форматы:** кириллические (МР-xxx) и латинские (MR/MP-xxx) — разные коды
- **Статус:** ✅ API keys working, read access confirmed
- **⚠️ Обновлено 2026-07-25:** категории обновлены (было 60, стало 71). Новые: Caggiati буквы/цифры, знаки препинания, медали/ордена, ретушь. Пустых категорий: 6.
### WordPress Application Password (2026-07-04)
- **User:** arno (id=6)
- **Password:** OvuC DhcN q3Vn MLBs JXPj 7Vok
- **Stored in:** /etc/environment → WORDPRESS_APP_PASS
### WooCommerce Behavior Rule (2026-07-04)
- **CRITICAL:** Any state-changing actions in WooCommerce (creating products, editing product descriptions, editing prices, updating stock, changing order statuses) require explicit user permission in chat ("yes", "да").
- Read-only actions (fetching orders, tracking SKU, checking stock) are allowed without permission.
### SEO Endpoint — Eurostela.ru (2026-07-04)
- **URL:** https://eurostela.ru/wp-json/openclaw/v1/seo-optimize
- **Method:** POST
- **Headers:**
- `Content-Type: application/json`
- `x-openclaw-key: 4f2c1d1b4bb2452db92b7fd3d6d86d8d`
- **Body:** { "post_id": <ID>, "seo_title": "<Title>", "seo_description": "<Description>" }
- **Purpose:** Автоматическая запись SEO meta (rank_math_title, rank_math_description) для товаров Eurostela.ru через WordPress PHP hooks
- **Status:** ✅ работает
### Sitemap — Eurostela.ru (2026-07-25)
- **URL:** https://eurostela.ru/sitemap_index.xml
- **Генератор:** Rank Math SEO Plugin
- **Состав:**
- `https://eurostela.ru/post-sitemap.xml` — посты (lastmod: 2026-07-20)
- `https://eurostela.ru/product-sitemap.xml` — товары (lastmod: 2026-07-24)
- `https://eurostela.ru/category-sitemap.xml` — категории WordPress (lastmod: 2026-07-20)
- `https://eurostela.ru/product_cat-sitemap.xml` — WooCommerce категории (lastmod: 2026-07-24)
- **Статус:** ✅ работает, доступен через https://
### Пустые/малополезные категории ⚠️ (2026-07-25 актуально)
- id=32 "Памятник валун" — **0 товаров** (пусто!)
- id=16 "Разное - без категории" — **0 товаров**
- id=241 "Ремонт, реставрация памятников" — **0 товаров**
- id=622 "Ретушь фото для памятника" — **0 товаров**
- id=157 "Столы и лавочки" — **0 товаров**
- id=158 "Шары и наконечники" — **0 товаров**
- id=64 "Памятник часовня" — **1 товар** (крайне мало)
- id=298 "Памятники колонны и обелиски" — **2 товара**
- id=71 "Цветной портрет на памятник" — **1 товар**
- id=77 "Позолота букв" — **3 товара**
### API Keys — eurostela.ru
- **WooCommerce CK:** ck_6ae9d729f33e1672ffed8bd41c042b14db74aabf
- **WooCommerce CS:** в окружении WOOCOMMERCE_API_SECRET
- **WP App Pass (arno):** OvuC DhcN q3Vn MLBs JXPj 7Vok
- **SEO Key:** 4f2c1d1b4bb2452db92b7fd3d6d86d8d
## Active Projects
| Project | Status | Path |
|---------|--------|------|
| eurostela.ru | active | projects/eurostela.ru/ |
| sing-box | active | projects/sing-box/ |
| ai-server | planning (полная спецификация 2026-08-04) | projects/ai-server/ |
## Project Creation and Storage Policy
Reference: /home/owner/.openclaw/workspace/project-rules.md
### Project Registry
All projects are registered in: /home/owner/.openclaw/workspace/projects/index.md
### Project Statuses
Allowed values: planning, active, paused, completed, archived
### Required Project Files
Every project must contain:
PROJECT.md → current project state
README.md → human-readable overview
CHANGELOG.md → project history
### Required Project Directories
```text
tasks/
decisions/
audit/
reports/
assets/
content/
docs/
notes/
contracts/
tmp/
archive/
```
### Project Statuses
Allowed values:
```text
planning
active
paused
completed
archived
```
### Project Registry
All projects tracked in:
```text
/home/owner/.openclaw/workspace/projects/index.md
```
### Context Loading Policy
Before working on a project:
1. Read PROJECT.md
2. Read open tasks
3. Read latest CHANGELOG entries
4. Read latest notes
5. Load additional files only if required
Never load the entire project by default.
### Storage Policy
Primary storage:
```text
workspace/projects/
```
Backup:
```text
Nextcloud /Projects/
```
Sync direction:
```text
local → Nextcloud
```
Automatic reverse synchronization is prohibited.
### Workspace File Policy
- **Корень `/workspace/`** — только файлы конфигурации OpenClaw (AGENTS.md, MEMORY.md, SOUL.md и т.д.) и папки `projects/`, `skills/`, `memory-core/`.
- **Запрещено**: создавать файлы вне папок проектов и skills. Все создаваемые файлы должны идти внутрь `/projects/<project>/` или `/skills/`.
- **При нарушении** — автоматически перенести файл в соответствующую папку проекта.
### Research and Decisions
- Research → facts, tests, evaluations (Location: notes/research/)
- Decisions → approved choices (Location: decisions/)
- Never mix them.
### Project Registry
See:
/home/owner/.openclaw/workspace/projects/index.md
### Agent Boundaries
Agents may: create/modify project files, update PROJECT.md/CHANGELOG.md, create reports/decisions/tasks
Agents may not: modify archived projects, delete archives, access unrelated projects without permission, modify system configuration without approval, move files between projects without approval
### Project Versioning Policy (2026-06-20)
#### Scope
- **All regular files** inside `workspace/projects/<project-name>/`, at any nesting level.
- Excludes: Cache/temporary files, Hidden VCS directories (.git), archive/ directories themselves
#### Core idea
- Active (current) file stays **in place** with its original name — **no revision suffix**.
- Every edit creates a **dated, numbered snapshot** in a **local `archive/` subfolder** located **in the same directory** as the file being edited.
- Archive filenames preserve the original filename **and extension** to avoid collisions: `<filename>.<ext>-<YYYY-MM-DD>-BU_<N>.<ext>`.
- Note for AI developers: Local project archive/ directories are not subject to the global system log and cache ban for coder-agent.
#### Pattern per file:
```
/home/owner/.openclaw/workspace/projects/<project-name>/content/
├── article.md ← active file
├── notes.md ← active file
├── articleassets.md ← active file
└── archive/
├── article-2026-06-20-BU_1.md
├── notes-2026-06-20-BU_1.md
├── article-2026-06-20-BU_2.md
└── notes-2026-06-22-BU_2.md
```
#### Behavior on edit
##### First edit (no archive exists for this file)
- In the same folder as `<file>.md`, create `archive/` if it doesn't exist.
- Copy the current content of `<filename>.<ext>` into `archive/<filename>-<YYYY-MM-DD>-BU_1.<ext>`.
- Keep editing the original `<filename>.<ext>` — it remains the active version.
(No data loss, no empty active file.)
##### Subsequent edits
- Ensure the local `archive/` folder exists.
- Find all revisions for this file in that `archive/` folder (by `<filename>-*.<ext>` pattern) and determine the highest revision number `N`.
- Copy the current active `<filename>.<ext>` into `archive/<filename>-<current-date>-BU_<N+1>.<ext>`.
- Continue editing `<filename>.<ext>` as the active version.
##### Important notes
- The **active file is never moved** — only **copied** into the `archive/`.
This guarantees the working copy is always ready and unchanged.
- Revision names include the original filename (e.g. `readme-2026-06-20-BU_1.md`), ensuring unique identification even if multiple `.md` files share the same `archive/` folder.
- There is no separate "base" file after the first edit — the original file remains the single active version.
- The archive/ directory appears once per working directory (e.g., assets/archive/, content/archive/), not once per file.
#### Relationship with storage/backup policy
- Archive revisions are part of the project and **are pushed to Nextcloud** together with all other files during manual sync or at natural checkpoints (task completion, milestone).
- No automatic background sync of archives.
- See `Storage Policy (2026-06-16)` for overall backup rules.
### Memory Audit — Cleanup (2026-08-17)
- Удалено: 5 legacy migrated DBs (~27MB), пустые файлы (workspace/2026-08-12, memory/2026-07-15.md, memory/2026-07-23.md, vault Untitled.canvas ×2)
- Перенесено: notes/*.md → skills/nextcloud-aio-oc/docs/ (Workspace File Policy)
- HEARTBEAT.md переписан под фактическое состояние (check-email-daily 9:00 отменён)
- Live cron (2026-08-17): active — mail-check (15m trigger-скрипт), wiki-ingest-event (30m), check-dreaming, Memory Dreaming Promotion, dreaming-sweep, trash-cleanup; disabled legacy (heartbeat-mail-check ×2, dreaming-sweep старый, wiki-24h-review) — удалены 2026-08-21 (запрос пользователя)
````
## Notes
<!-- openclaw:human:start -->
<!-- openclaw:human:end -->
## Related
<!-- openclaw:wiki:related:start -->
- No related pages yet.
<!-- openclaw:wiki:related:end -->