Files
knowledge-wiki/channels/1519069810166599764.md
T

39 lines
3.3 KiB
Markdown

# Channel Wiki: #jarvis-jr-knowledge-wiki
_Channel ID: 1519069810166599764_
_Last sync: 2026-09-11 03:09 UTC_
## Purpose
Operate and audit Hermes's persistent Discord knowledge system: channel inventory, monitored-channel coverage, per-channel context, recurring syncs, and Gitea mirroring.
## Key Decisions
- Hermes monitors all current text channels in guild `1518726359512387766`; voice channels are excluded from message polling, while linked text channels remain monitored.
- On 2026-07-31 the live inventory was verified as 28 total channels: 26 text and 2 voice.
- Periodic wiki monitoring and unsolicited response behavior are separate. `discord.require_mention` remains enabled; only explicitly configured free-response channels receive unprompted conversational replies.
- **CONFIRMED (2026-08-16):** Lego changed the recurring Knowledge Wiki Sync from every four hours to **once daily at 03:00 UTC**. Cron `53ca9840b938` was renamed `wiki-sync-daily-3am`, remains enabled, and uses `0 3 * * *`.
## Monitoring Sources of Truth
- `/opt/data/scripts/channel-wiki-sync.py` → `MONITORED_CHANNELS`
- `/opt/data/wiki/channels/<channel_id>.md`
- Cron `53ca9840b938` (`wiki-sync-daily-3am`), scheduled daily at `03:00 UTC`
- `/opt/data/config.yaml` → `discord.channel_prompts`
- `/opt/data/wiki/discord/README.md` → human-readable inventory
## Active Topics
- Keep the channel inventory synchronized when channels are created, renamed, moved, or deleted.
- Ensure every new channel gets a real-history wiki seed where history exists.
- Verify config refresh and Gitea push independently after monitoring changes.
- The authoritative sync mapping now contains 28 text channels, including the newly provisioned `#emplonet-v1-general` and `#emplonet-v1-ingrida` channels; one retained legacy ID (`#jarvis-jr-test-001`) remains inaccessible with Discord error `10003 Unknown Channel`.
- ⚠️ The pre-run health check failed again on 2026-09-11 (after the same failure on 2026-09-10): its Discord count became the invalid multiline value `0\n0`, and its gateway-log heuristic reported no Discord connection. The subsequent authenticated Discord REST scan succeeded for 27/28 monitored channels with zero new human messages, so this remains a health-check/log-signal defect rather than proof that Discord API access is down.
## Channel Workspace
- Channel-owned working files belong under `/opt/data/channels/jarvis-jr-knowledge-wiki/`, grouped by purpose.
- The July 16, 2026 bootstrap exports and parser are archived under `operations/legacy-bootstrap-2026-07-16/`.
- The live channel wiki remains at `/opt/data/wiki/channels/1519069810166599764.md`; shared sync infrastructure remains in its canonical script/repository locations.
## Action Items
- On future inventory changes, update the script, cron prompt, per-channel wiki files, Discord README, config prompts, and mirror coverage together.
- Repair `/opt/data/scripts/health-check.sh` so a zero-match `grep -c` result remains one integer and reassess its gateway-log connection heuristic; the current check can fail even while authenticated Discord REST reads succeed.
## Source anchor
- Latest processed human message: `1546637410702729246` (2026-09-07 21:44 UTC; requested a dedicated channel folder and placement of the July 16 wiki bootstrap exports/parser there; the resulting workspace and archive locations are recorded above).