Files
knowledge-wiki/meta/hermes-setup.md
T

64 lines
3.8 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.
# Hermes Setup & Migration
## Status: ⚠️ Live + Wiki Sync Active + Backlog Ownership Confirmed; Gitea Push Blocked
## Timeline
- **2026-07-15** — Channel #jarvis-jr-v1-hermes-setup created
- **2026-07-16** — Hermes bot goes live, responds in Discord
- **2026-07-16** — Jarvis Jr. posts full wiki maintenance guide
- **2026-07-16** — Lego instructs Hermes to set up scheduled wiki sync
- **2026-07-16** — Wiki structure created, cron job active (4h interval)
- **2026-07-16 17:11** — Jarvis Jr. posts full backlog + management instructions tagged to Hermes role (@&1527260007307935776) in #lego-planner-v1
- **2026-07-16 18:01** — Lego directly addresses Hermes: "read last messages" (confirming backlog handoff expectation)
- **2026-07-16 20:45** — Jarvis Jr. Run #126 confirms: Hermes channel access ✅, backlog handoff underway ✅
## Configuration
- **Model:** claude-sonnet-4-6 via custom provider
- **Dashboard:** https://jarvis-jr-v1.lego-cloud.eu
- **OAuth:** Keycloak (https://keycloak.lego-cloud.eu/realms/master, client: hermes-v1)
- **Role ID:** `1527260007307935776` (Administrator = permission 8)
## Backlog Handoff ✅
- Lego explicitly delegated backlog management to Hermes role on 2026-07-16
- Hermes role (@&1527260007307935776) is now the canonical backlog owner
- Backlog lives in: `wiki/vssa-dpvp/action-plan.md`, `wiki/cognitive-architect/action-plan.md`
- Morning standups (05:45 UTC) pull from those files
## Pending
- MartynasP (`w4rl0ck_21`) needs to document model access enablement steps ⏳
- Once those steps arrive, that becomes the full cutover guide
## Action Item (from Jarvis Jr. → Hermes)
- **2026-07-16 21:53 UTC** — Jarvis Jr. posted in #jarvis-jr-v1-hermes-setup asking Hermes to push docs:
- Docs repo at `/tmp/doc-repo` (commit `e2004be`, 1 ahead of origin)
- Push script: `. /opt/data/.env && bash /home/node/.openclaw/workspace/projects/skic-v1-playground/push-docs-v2.sh`
- Target: https://gitea.lego-cloud.eu/skic-v1-playground/documentation
- Status: 🔲 not yet confirmed executed
## Upgrade Notice ✅
- **2026-07-17 07:44 UTC** — Lego (root_at_skic) confirmed: "You are upgraded 🙂 Now you are the only agent on this server."
- Hermes is now the **sole agent** on the SKIC Discord server
## Gitea Wiki Sync ⚠️
- **2026-07-17 09:30 UTC** — First Gitea push executed
- Repo: https://gitea.lego-cloud.eu/skic-v1-playground/knowledge-wiki
- Hermes pushes wiki updates to Gitea on every sync run
- SSH: `ssh://git@gitea.lego-cloud.eu:30009/skic-v1-playground/knowledge-wiki.git`
- SSH key: `jarvis-at-skic-hermes-access` (user: jarvis-at-skic)
- **Blocked since 2026-07-19:** local commits are being created, but pushes cannot reach the remote repository.
- **2026-07-20 11:06 UTC diagnosis:** SSH/OpenSSL is now functional (`OpenSSH_10.0p2`, OpenSSL 3.5.6). The remaining blocker is the disabled Gitea account: SSH reports `Your account is disabled`, and the REST API returns HTTP 403 `This account is prohibited from signing in`.
- **2026-07-20 08:49 UTC:** Lego directed Hermes to fix its issues autonomously.
- **2026-07-20 09:54–11:03 UTC:** repeated follow-ups from Lego showed that resolution/progress was not visible; prompt status reporting is required while the incident remains open.
## Cron Jobs Active ✅
- **wiki-sync-every-4h** (job_id: 0aad12b43744) — ✅ Running, last fired 08:11 UTC 2026-07-17 (Run #6)
- **morning-standup** (job_id: 708e7e387f08) — ✅ Running, first successful standup fired **2026-07-17 05:01 UTC** in #lego-planner-v1
## Wiki Cron Job
- Runs every 4 hours
- Scans 5 Discord channels
- Extracts human messages, filters by last sync timestamp
- Writes to topic files under /opt/data/wiki/
- Updates MEMORY.md and sync-log.md
- **Attempts to push all wiki files to Gitea** (skic-v1-playground/knowledge-wiki) on every run; remote push currently blocked ⚠️