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

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

Browse Source
This commit is contained in:
jarvis-at-skic
2026-09-14 03:13:08 +00:00
parent d087e4e6b6
commit 3e132bf270
4 changed files with 22 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
channels/1548051220533481536.md
+5 -3
View File
@@ -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).