The NetworkTechnologyCommunication
Communication
Current communication surfaces across Telegram, Fixie chat, notifications, and live app messaging patterns.
Communication in the current stack is not one thing. It spans:
- Telegram integration
- Fixie chat and streaming
- in-app notifications
- live transport patterns used by the app and API
Telegram
Telegram is part of the communication stack through:
- bot/webhook integration
- selected login/auth flows
- notification and interaction surfaces
This should be described as one channel in the stack, not as the main product UI.
Fixie Chat
Fixie chat is the most important live communication surface in the product.
It uses:
- streaming responses
- agent memory
- tool execution
- graph-aware and identity-aware context
The user-facing route is /fixies, with backend support under /api/fixie/*.
Notifications
Communication also includes:
- in-app notifications
- system and activity alerts
- stateful user-facing updates across profile, governance, and finance surfaces
Current Reader Rule
If you are documenting the live communication stack, describe:
- Fixie chat
- notifications
- Telegram as an additional channel
Do not over-index on older generic chat examples or speculative transport layers that are not central to the current app surface.
For the actual API route families behind this, use REST API Reference.