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

channels/1547923343905259601.md

@@ -1,8 +1,8 @@
 # Channel Wiki: #cogarch-v1-shorts
 _Channel ID: 1547923343905259601_
 _Created: 2026-09-11 10:54 UTC_
-_Last sync: 2026-09-12 03:15 UTC_
-_Latest processed human message: 1548040175114788867_
+_Last sync: 2026-09-13 UTC_
+_Latest processed human message: 1548754239445012481_
 
 ## Purpose
 
@@ -12,17 +12,18 @@ Plan, create, review, and maintain concise short-form CogArch content. Specific
 
 - Channel workspace: `/opt/data/cogarch-v1-shorts/`
 - Channel skill repository: https://gitea.lego-cloud.eu/cognitive-architect-v1-skills-code-agent/cogarch-v1-channel-shorts
-- Presentation-skill provisioning and final deck delivery state were not independently verified by this daily scan.
+- Current verified deck: `/opt/data/cogarch-v1-shorts/workspace/cognitive-architect-shorts-2-slide-deck/release/2026-09-13-ibm-cognitive-architect-shorts-solution-factory-1.3.1.pptx`.
 
 ## Action Items
 
-- Verify the `powerpoint-cognitive-architect` remote repository/runtime installation and the final two-slide deck artifact before treating either as delivered.
+- Verify the `powerpoint-cognitive-architect` remote repository/runtime installation separately; the current deck artifact is locally verified.
 
 ## Key Decisions
 
 - The channel was assigned its own workspace, durable wiki, dedicated channel skill, and daily knowledge-sync coverage.
 - Maintain a CogArch-specific presentation skill named `powerpoint-cognitive-architect` under the Cognitive Architect skills organization. It must reference the general PowerPoint skills instead of duplicating or overlapping their capabilities.
-- The requested Shorts deck is a two-slide, light, professional IBM presentation titled `IBM | Cognitive Architect | Shorts (Solution Factory)`; it must omit the date, identify presenter Oleg Lukasonok (`oleg.lukasonok@lt.ibm.com`, Slack nickname `lego`), and present the Cognitive Architect, Solution Factory tutorial, and `cognitive-architect` Slack channel as clearly labeled links.
+- The Shorts deck is a light, professional IBM presentation titled `IBM | Cognitive Architect | Shorts (Solution Factory)`; it omits the date, identifies presenter Oleg Lukasonok (`oleg.lukasonok@lt.ibm.com`, Slack nickname `lego`), and presents the Cognitive Architect, Solution Factory tutorial, and `cognitive-architect` Slack channel as clearly labeled links.
+- The deck has three slides: title, Agenda, and links. The Agenda contains: “What is Solution Factory?”, “How to enable Solution Factory?”, and “How to access Solution Factory?”.
 - Discord topic: `Plan, create, review, and maintain concise short-form CogArch content.`
 - Pinned channel guidance: message `1547924959656157256`.
 - Mutable channel history belongs in this wiki, not in Hermes gateway configuration or the reusable channel skill.

channels/1548051220533481536.md

@@ -1,7 +1,7 @@
 # Channel Wiki: #cogarch-v1-argo-workflows
 _Channel ID: 1548051220533481536_
 _Created: 2026-09-11 UTC_
-_Last sync: 2026-09-12 03:15 UTC_
+_Last sync: 2026-09-14 03:11 UTC_
 
 ## Purpose
 
@@ -33,6 +33,7 @@ Observe, analyze, and preserve evidence about Cognitive Architect Solution Facto
 - Live verification on 2026-09-11 identified Argo Workflows `v4.0.5` and service-account namespace `solution-factory`.
 - 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.
 
 ## People & Roles
 
@@ -42,9 +43,10 @@ Observe, analyze, and preserve evidence about Cognitive Architect Solution Facto
 ## Action Items
 
 - Select the first Solution Factory behavior or workflow to observe.
-- Deliver the requested investigation artifact as an HTML page; delivery status was not independently established by this sync.
+- ✅ The requested standalone HTML investigation page was delivered in Discord messages `1548064910263586922`–`1548064913602379868`.
+- Obtain the exact `iter_...` ID and approximate start time for `arch_kiSj9jBKI` to determine whether it should remain inside Argo's 24-hour retention window and to correlate any external S3 or Solution Factory history.
 
 ## Evidence
 
 - `1548051382714507325` — RootAtSkic requested a local folder, dedicated channel skill, and Gitea publication.
-- Latest processed human message: `1548063934853025966` (2026-09-11 20:13 UTC; RootAtSkic changed the requested investigation artifact from Markdown to HTML).
+- 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).