PRODUCT SYSTEM
More than a Telegram command bot.
Oberezhno is structured as a recurring content experience. Subscribers receive messages at scheduled times; morning questions can affect evening responses; guest-author content is separated from the core content system; source tags help identify where subscribers came from.
USER FLOW
A simple interface built on a real state machine.
ENGINEERING
Persistence, delivery logic and deploy safety.
Subscriber storage and source attribution.
Morning/day/evening delivery in Moscow time.
Telegram limits, retries and cleanup of blocked subscribers.
Content deck, subscription, source and guest flows tested before deploy.
RESULT
A small digital product with content, data and automation working together.
This project shows that I can move from a content idea to system behavior, backend integration, deployment and ongoing maintainability.