How michaai/ctmtuci-schedule works
Main Components
a) Core Bot Components:
• Main Bot Service (src/main.rs)
• Telegram Interface Layer (src/tg.rs)
• Data Processing Components
• Sheet Parser (src/sheet_parser.rs)
• Sheet Updater (src/sheet_updater.rs)
b) Supporting Systems:
• Dialog Management System (src/dialoge/)
• Data Types Layer (src/datatypes.rs)
• Utility Functions (src/utils.rs)
┌─ External Services Layer ─┐
• Telegram API │
• Google Sheets API │
• ┘
• ↕
┌─ Interface Layer ────────┐
• Telegram Handler │
• Sheet Operations │
• ┘
• ↕
┌─ Core Logic Layer ───────┐
• Dialog Management │
• Data Processing │
• ┘
• ↕
┌─ Data Layer ────────────┐
• Data Types │
• Utils │
• ┘
Component Relationships
• Blue: External service connections
• Green: Internal component communications
• Orange: Data flow paths
Key relationships to highlight:
• Main service orchestrating all components
• Dialog system managing conversation flow
• Sheet parser/updater interacting with Google Sheets
• Telegram interface handling bot communications
Specific Implementation Details
Technical aspects:
• Docker container boundary (indicated by Dockerfile presence)
• CI/CD pipeline connection (shown by .github/workflows)
• Binary outputs (src/bin directory)
• Module dependencies and interactions