53 lines
4.3 KiB
Markdown
53 lines
4.3 KiB
Markdown
# Channel Wiki: #cogarch-v1-argo-workflows
|
||
_Channel ID: 1548051220533481536_
|
||
_Created: 2026-09-11 UTC_
|
||
_Last sync: 2026-09-14 03:11 UTC_
|
||
|
||
## Purpose
|
||
|
||
Observe, analyze, and preserve evidence about Cognitive Architect Solution Factory behavior and workflows. Observation is read-only by default.
|
||
|
||
## Canonical Resources
|
||
|
||
- Channel workspace: `/opt/data/cogarch-v1-argo-workflows/`
|
||
- Channel skill repository: https://gitea.lego-cloud.eu/cognitive-architect-v1-skills-code-agent/cogarch-v1-channel-argo-workflows
|
||
- IBM documentation repository, when relevant: `CTOTools/Documentation` on `github.ibm.com`
|
||
|
||
## Key Decisions
|
||
|
||
- Channel-owned files belong in the dedicated local workspace.
|
||
- Reusable operating rules belong in the dedicated channel skill; mutable continuity belongs in this wiki.
|
||
- Observation does not authorize upstream edits, external publication, or IBM merges. IBM merges require human approval.
|
||
- **Hard authority boundary:** Hermes must perform no write action against Cognitive Architect Argo Workflows in any environment unless Discord user `1518725627845283888` explicitly overrides this restriction.
|
||
- Production Argo Workflows access is read-only through the dedicated channel-skill helper. Its API token must never enter model context, command arguments, logs, or artifacts.
|
||
|
||
## Active Topics
|
||
|
||
- Investigate production Solution Factory workflow-template behavior and failures through GET-only Argo access.
|
||
|
||
## Key Context
|
||
|
||
- Use live source inspection for current-state claims.
|
||
- Load `cognitive-architect` for architecture/model work and `cogarch-github` for IBM CTOTools Documentation operations.
|
||
- The channel skill retrieves the Argo API token and Swagger URL by exact Bitwarden IDs inside a subprocess, permits only Swagger-declared GET operations, and sanitizes generic output.
|
||
- 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
|
||
|
||
- RootAtSkic (`1518725627845283888`) — channel owner and human authority.
|
||
- Hermes (`1526860732917088266`) — assisting bot.
|
||
|
||
## Action Items
|
||
|
||
- Select the first Solution Factory behavior or workflow to observe.
|
||
- ✅ 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: `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).
|