Purpose
Why Error Messages Exist
Error messages describe only the visible states inside the chat. They explain why LogicBasis cannot respond at that moment — without technical codes or internal details.
Loading
System Loading
When LogicBasis is not ready yet, it shows: “Loading…” The chat remains visible but responds only after initialization.
Access
Plan Not Active
When the chat is visible but responses are not available: “The chat is visible, but responses are only available with an active plan.” Or when sending a message: “Access is not active yet. Please activate your plan to unlock full chat functionality.”
Identity
Not Logged In
When no valid identity is available: “Please log in to view your conversation history.” The session is closed cleanly.
Session
Session Closed
When a conversation has been ended: “This session is closed. For a new conversation: ‘New Question’.” Every new question creates a new session.
Deepen
Follow‑Up
When the user requests more depth: “Tell me briefly: which point needs more clarity?” LogicBasis continues calmly.
End
Completion
When ending a session: “Completed.” The session is closed and archived.
Technical
Technical Error
If a session cannot be created: “Technical error. Please log in again.” If the API does not respond: “Technical error. Please try again.”
Response
No Response Received
When no reply is returned from the server: “No response received.” LogicBasis remains calm and does not break the session.
Not
What Errors Are Not
Error messages are not technical diagnostics, not codes and not debugging information. They describe only the visible states inside the chat — clearly, calmly and without speculation.