# WeKnora API Capability Gaps These gaps must not be solved with private WeKnora source or database changes. | Capability | Current external handling | |---|---| | Like/dislike and unresolved reason | DobotAI PostgreSQL and API | | Formal covered/not-covered decision | DobotAI evaluation rules using references, scores, answer status, and offline calibration | | Support case, owner, SLA, and status | DobotAI workflow | | Human reply to original channel | DobotAI channel adapter; not written to WeKnora history by default | | Stable external turn correlation | DobotAI mapping of external message, turn, WeKnora session/request, and gateway trace | | Complete multi-call token usage | Model gateway/Langfuse; unknown remains null/unknown | | Strict image failure semantics | Adapter contract test; reject image traffic on failure | | Arbitrary human assistant-message append | Keep in DobotAI and submit an upstream API request only if context injection becomes necessary | Allowed responses to a gap: 1. adjust the product design; 2. implement it outside WeKnora; 3. open an upstream issue; 4. submit a general upstream pull request.