skic-v1-playground/knowledge-wiki
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

wiki: sync 2026-09-16 03:13 UTC — 4 file(s) updated

Browse Source
This commit is contained in:
jarvis-at-skic
2026-09-16 03:13:27 +00:00
parent 2865b253f7
commit 9334eb99d5
4 changed files with 19 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
channels/1519069810166599764.md
+2 -2
View File
@@ -1,6 +1,6 @@
# Channel Wiki: #jarvis-jr-knowledge-wiki
_Channel ID: 1519069810166599764_
_Last sync: 2026-09-15 03:07 UTC_
_Last sync: 2026-09-16 03:11 UTC_
## Purpose
Operate and audit Hermes's persistent Discord knowledge system: channel inventory, monitored-channel coverage, per-channel context, recurring syncs, and Gitea mirroring.
@@ -24,7 +24,7 @@ Operate and audit Hermes's persistent Discord knowledge system: channel inventor
- 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 #154 on 2026-09-15 scanned 32/33 monitored IDs; `#jarvis-jr-test-001` remains inaccessible with Discord `10003 Unknown Channel`. One new human message advanced `#lego-v1-cv` through `1549020705843060847`; the CV workspace, source attachment, brand-neutral template requirement, and generated DOCX/PDF were already captured in that channel wiki before this run.
- ⚠️ Run #155 on 2026-09-16 scanned 32/33 monitored IDs; `#jarvis-jr-test-001` remains inaccessible with Discord `10003 Unknown Channel`. Six human messages in `#cogarch-v1-argo-workflows` advanced its anchor through `1549399634302992447` and established that the failed run's fail-open Redis warning did not recur in the read-only-verified rerun pod; the overwritten detailed agent log reportedly contained operation timeout/retry-limit errors.
## Channel Workspace
- Channel-owned working files belong under `/opt/data/channels/jarvis-jr-knowledge-wiki/`, grouped by purpose.
channels/1548051220533481536.md
+6 -2
View File
@@ -1,7 +1,7 @@
# Channel Wiki: #cogarch-v1-argo-workflows
_Channel ID: 1548051220533481536_
_Created: 2026-09-11 UTC_
_Last sync: 2026-09-14 03:11 UTC_
_Last sync: 2026-09-16 03:11 UTC_
## Purpose
@@ -34,10 +34,12 @@ Observe, analyze, and preserve evidence about Cognitive Architect Solution Facto
- The production namespace exposes six namespaced WorkflowTemplates: one four-phase coordinator, four generation/refinement phases, and a separate propagation phase. No CronWorkflows were listed; cluster-scoped template inventory is inaccessible to the read-only service account, so its existence is unknown.
- For architecture `arch_up7BoYhj-` and iteration `iter_QfJ3shQvZ`, no Workflow object exists in the live or archived lists. An Argo GET label selector using that architecture ID returns HTTP 400 because Kubernetes label values cannot end with `-`; normal Solution Factory submissions copy `architecture-id` into Workflow metadata labels. This is strong evidence that submission is rejected before the Processing workflow is created, not that a Processing pod starts and fails.
- Live inspection on 2026-09-13 found no active or archived Workflow labeled `architecture-id=arch_kiSj9jBKI`; the daily inventory also contained no record for it from 2026-09-06 through 2026-09-13. The current Processing template does include the intended image path: conversion-to-markdown → markdown-chunking → describe-images → merge-descriptions. Processing Workflows have `ttlStrategy.secondsAfterCompletion: 86400`, while the accessible archived list is empty, so Argo logs disappear with the Workflow after roughly 24 hours unless retained elsewhere. For a recent iteration, absence strongly suggests that the Processing Workflow was never created; for an older iteration, Argo alone cannot distinguish non-submission from TTL cleanup.
- Live inspection on 2026-09-15 for architecture `arch_xOQ5jks0b`, iteration `iter_fMfOM35fb`, found Processing succeeded (`phase-0100-processing-sn74b`, 6/6) but High-Level Insights failed (`phase-0200-high-level-insights-ffmgf`, 1/2). The first high-level step, `0200-phase-0600-step-generate-knowledge-wiki-plan`, launched the Cline/code agent but it exited with code 201 on the initial attempt and all three error retries. The original centralized agent log reportedly showed an operation timeout and retry-limit failure, but a rerun at 2026-09-15 12:02:57 UTC overwrote that file. A Redis DNS warning (`redis:6379` unresolved) appeared only in the failed run's Argo `main`-container stdout, was handled fail-open, and was not causal. Fresh read-only inspection of rerun pod `phase-0200-high-level-insights-9p7vz-run-step-2817085442` found 17 log entries, zero Redis references/errors, and normal one-key credential-pool initialization.
## People & Roles
- RootAtSkic (`1518725627845283888`) — channel owner and human authority.
- `whyt6249` (`204689314796273674`) — supplied the overwritten agent-log finding and identified the rerun pod for comparison.
- Hermes (`1526860732917088266`) — assisting bot.
## Action Items
@@ -49,4 +51,6 @@ Observe, analyze, and preserve evidence about Cognitive Architect Solution Facto
## Evidence
- `1548051382714507325` — RootAtSkic requested a local folder, dedicated channel skill, and Gitea publication.
- Latest processed human message: `1548759488570466527` (2026-09-13 18:17 UTC; RootAtSkic confirmed that the lookup must use the exact Kubernetes selector `architecture-id=arch_kiSj9jBKI`; live and archived Argo queries using that selector returned no items).
- Previous processed human message: `1548759488570466527` (2026-09-13 18:17 UTC; RootAtSkic confirmed that the lookup must use the exact Kubernetes selector `architecture-id=arch_kiSj9jBKI`; live and archived Argo queries using that selector returned no items).
- `1549364076239397005` — RootAtSkic requested diagnosis of failed High-Level Insights for `arch_xOQ5jks0b` / `iter_fMfOM35fb`; read-only Argo inspection isolated the failure to knowledge-wiki-plan agent exit code 201 after retries.
- Latest processed human message: `1549399634302992447` (2026-09-15 12:40 UTC; `whyt6249` requested comparison against rerun pod `phase-0200-high-level-insights-9p7vz-run-step-2817085442`; live read-only inspection found no recurrence of the Redis warning).