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

wiki: sync 2026-09-21 03:18 UTC — 3 file(s) updated

Browse Source
This commit is contained in:
jarvis-at-skic
2026-09-21 03:18:52 +00:00
parent 1dcd361a31
commit dcfdb292ab
3 changed files with 13 additions and 2 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-20 03:16 UTC_
_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.
@@ -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 #159 on 2026-09-20 scanned 32/33 monitored IDs; `#jarvis-jr-test-001` remains inaccessible with Discord `10003 Unknown Channel`. Four new human messages were processed across `#jarvis-jr-general` and this channel.
- ⚠️ 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
channels/1550910135923384341.md
+3
View File
@@ -21,6 +21,9 @@ Find, assess, and pursue suitable new roles for Oleg Lukasonok using verified CV
- No role from those six employers currently proves all hard constraints. The decisive blocker is employment location, not technical fit.
- Strategic location-exception priorities: Maersk Lead AI Platform Engineer; AWS Principal Solutions Architect CEE Enterprise FSI; OpenAI Manager, Applied AI Architects; Roche Enterprise Architect — Data & AI; OpenAI Applied AI Architect, Large Enterprise; Google Cloud Partner Principal Architect, GSI CTO.
- Draft exception-outreach messages: `/opt/data/workspaces/channels/lego-v1-new-job/artifacts/major-employer-exception-outreach.md`.
- Anthropic and OpenAI follow-up completed on 2026-09-20: `/opt/data/workspaces/channels/lego-v1-new-job/research/anthropic-openai-2026-09-20.md`.
- Strongest Anthropic leads: Applied AI Architect — Partnerships; Manager, Forward Deployed Engineering; Applied AI Architect — Industries. All are direct-company vacancies tied to Munich or London, with no explicit Lithuania employment option.
- The opportunity tracker now distinguishes `source_type` and `recruiter_or_contact`; current entries are direct-employer postings and list `Not named in posting` where no recruiter is disclosed.
- Produce a shorter, role-targeted résumé only after Oleg selects a vacancy.
## Action items