# Channel Wiki: #jarvis-jr-knowledge-wiki
_Channel ID: 1519069810166599764_
_Last sync: 2026-09-21 03:15 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 33 text-channel IDs, including the recently provisioned `#cogarch-v1-iac`, `#cogarch-v1-shorts`, `#cogarch-v1-argo-workflows`, `#jarvis-jr-v1-storm`, and `#lego-v1-cv` channels; one retained legacy ID (`#jarvis-jr-test-001`) remains inaccessible with Discord error `10003 Unknown Channel`.
- ✅ On 2026-09-13 the recurring health-check defect was repaired: zero-match `grep -c` output can no longer become the invalid multiline value `0\n0`, and the Discord check now recognizes the gateway's actual inbound/send activity log forms. A syntax check and complete rerun passed all four checks; the same run's authenticated Discord REST scan succeeded for 31/32 monitored channels.
- ⚠️ Run #160 on 2026-09-21 scanned 32/33 monitored IDs; `#jarvis-jr-test-001` remains inaccessible with Discord `10003 Unknown Channel`. No human messages were newer than the durable anchors in the 32 accessible channels.
- ⚠️ RootAtSkic asked how people will obtain/use the numeric-ID Markdown channel files and whether moving the wiki to the “Google” `OKF` format would be useful. The intended format name and desired delivery interface are **UNKNOWN** and must be clarified before any migration; no format change was authorized.

## 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.
- ✅ Repaired `/opt/data/scripts/health-check.sh` on 2026-09-13 and verified a complete successful rerun. Continue treating authenticated REST scan results as the source of truth for wiki coverage.
- 🔲 Define a user-facing way to discover and retrieve channel wiki Markdown files whose filenames are Discord channel IDs.
- 🔲 Clarify what RootAtSkic meant by Google `OKF`, then assess migration value and compatibility before changing the current Markdown wiki.

## Source anchor
- Latest processed human message: `1550913962810282146` (2026-09-19 16:58 UTC; asked how numeric-ID Markdown files will be delivered and whether a move to Google `OKF` would be useful; exact format intent remains unknown).