51 lines
3.3 KiB
Markdown
51 lines
3.3 KiB
Markdown
# Channel Wiki: #cogarch-v1-argo-workflows
|
|
_Channel ID: 1548051220533481536_
|
|
_Created: 2026-09-11 UTC_
|
|
_Last sync: 2026-09-12 03:15 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.
|
|
|
|
## 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.
|
|
- Deliver the requested investigation artifact as an HTML page; delivery status was not independently established by this sync.
|
|
|
|
## 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).
|