Any runtime exception inside the conversation workflow is recorded as UNKNOWN (src/main/java/com/kof22/carlai/domain/CarlClientWorkflows.java:316-320); FAILED only arises from capacity rejection (CarlConversation.java:150-152). An unconfigured or unreachable model therefore shows "The outcome is unknown. No completed answer is available; this message will not be sent again automatically." (CarlNativeChat.java:160, CarlTalkHtml.java). The user cannot tell "Carl is not connected to a model" from "the request may have partially applied".
The foundation side has the same silence (KofTwentyTwo/kof22-agent-foundation#31). When the foundation surfaces a failure class, Carl should map a clean provider failure before any write to a distinct FAILED/unavailable status and keep UNKNOWN for genuinely uncertain outcomes.
Priority rationale
P2: honest but unhelpful; blocks a usable "model unavailable" state in the UI.
Filed from the 2026-10-01 real-versus-fake audit of Carl (branch feature/cicd-liquibase-gitops, HEAD 5414d7a, main 1b334d1). Four read-only reviews covered domain and services, QQQ metadata and data model, tests/CI/evidence, and docs/integrations. A local offline build of a Carl copy against the installed foundation 0.5.0-SNAPSHOT is in progress; its result will be added as a comment. Existing issues #3, #4 and #5 (real Monarch accounts, Authentik with real data, CI/CD with Liquibase and ArgoCD) are referenced rather than duplicated.
## Summary
Any runtime exception inside the `conversation` workflow is recorded as `UNKNOWN` (`src/main/java/com/kof22/carlai/domain/CarlClientWorkflows.java:316-320`); `FAILED` only arises from capacity rejection (`CarlConversation.java:150-152`). An unconfigured or unreachable model therefore shows "The outcome is unknown. No completed answer is available; this message will not be sent again automatically." (`CarlNativeChat.java:160`, `CarlTalkHtml.java`). The user cannot tell "Carl is not connected to a model" from "the request may have partially applied".
The foundation side has the same silence (KofTwentyTwo/kof22-agent-foundation#31). When the foundation surfaces a failure class, Carl should map a clean provider failure before any write to a distinct `FAILED`/unavailable status and keep `UNKNOWN` for genuinely uncertain outcomes.
## Priority rationale
P2: honest but unhelpful; blocks a usable "model unavailable" state in the UI.
---
Filed from the 2026-10-01 real-versus-fake audit of Carl (branch `feature/cicd-liquibase-gitops`, HEAD `5414d7a`, main `1b334d1`). Four read-only reviews covered domain and services, QQQ metadata and data model, tests/CI/evidence, and docs/integrations. A local offline build of a Carl copy against the installed foundation 0.5.0-SNAPSHOT is in progress; its result will be added as a comment. Existing issues #3, #4 and #5 (real Monarch accounts, Authentik with real data, CI/CD with Liquibase and ArgoCD) are referenced rather than duplicated.
This repo is archived. You cannot comment on issues.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Any runtime exception inside the
conversationworkflow is recorded asUNKNOWN(src/main/java/com/kof22/carlai/domain/CarlClientWorkflows.java:316-320);FAILEDonly arises from capacity rejection (CarlConversation.java:150-152). An unconfigured or unreachable model therefore shows "The outcome is unknown. No completed answer is available; this message will not be sent again automatically." (CarlNativeChat.java:160,CarlTalkHtml.java). The user cannot tell "Carl is not connected to a model" from "the request may have partially applied".The foundation side has the same silence (KofTwentyTwo/kof22-agent-foundation#31). When the foundation surfaces a failure class, Carl should map a clean provider failure before any write to a distinct
FAILED/unavailable status and keepUNKNOWNfor genuinely uncertain outcomes.Priority rationale
P2: honest but unhelpful; blocks a usable "model unavailable" state in the UI.
Filed from the 2026-10-01 real-versus-fake audit of Carl (branch
feature/cicd-liquibase-gitops, HEAD5414d7a, main1b334d1). Four read-only reviews covered domain and services, QQQ metadata and data model, tests/CI/evidence, and docs/integrations. A local offline build of a Carl copy against the installed foundation 0.5.0-SNAPSHOT is in progress; its result will be added as a comment. Existing issues #3, #4 and #5 (real Monarch accounts, Authentik with real data, CI/CD with Liquibase and ArgoCD) are referenced rather than duplicated.