Engineering
Engineering Timeline
2026
- [staffprobot] Фаза 1: docs foundation и endlog протокол
- [cvetbuket] Automatic courier dispatch
- [cvetbuket] Payment link TTL and reserve release
- [cvetbuket] Two-way order cancellation sync
- [cvetbuket] Unified bot logic (Telegram + MAX)
- [cvetbuket] AI consultant for bouquet selection
- [itimpulse] Фаза 1: стандарты docs и foundation knowledge
- [itimpulse] Фаза 2: endlog pipeline, knowledge graph, sync docs
- [itimpulse] Создание портфолио itimpulse.ru
- [itimpulse] Реализация сайта портфолио (этап 4)
CvetBuket Platform
Engineering log
Changelog of engineering solutions. Generated from `doc/changelog-entries.md`.
Run: `php scripts/build_engineering_log.php`
2026 — AI consultant for bouquet selection
Problem
Clients needed 24/7 personalised recommendations; staff could not scale.
Engineering
YandexGPTClient::consultFlorist() with catalog slice and system prompt; 3 price tiers; ai_chat_history for context.
Business value
Faster selection, upsell, less routine load on staff.
Tech
PHP, YandexGPT API, MySQL ai_chat_history
2026 — Automatic courier dispatch
Problem
Manual courier ordering slowed down delivery.
Engineering
cron_taxi.php creates delivery requests via Yandex Delivery API (Express / Other-Day). Webhook updates order status.
Business value
Orders automatically receive courier dispatch.
Tech
PHP, Yandex Delivery API, cron, webhook
2026 — Payment link TTL and reserve release
Problem
Expired SBP links left reserves locked in Tinkoff and 1С.
Engineering
cron_payment_expiry.php runs every minute; calls TinkoffSBPClient::cancel() and ODataClient::cancelOdataOrder().
Business value
No stuck reserves; stock and money freed without manual steps.
Tech
PHP, Tinkoff SBP API, 1С OData PATCH, cron
2026 — Two-way order cancellation sync
Problem
Cancel in 1С or on site/bot had to stay in sync.
Engineering
Local cancel → cancelOdataOrder(). cron_order_status.php detects 1С cancel → local status + notify client.
Business value
Single view of order state; operator or client cancel reflected everywhere.
Tech
PHP, 1С OData, cron, Telegram/MAX Notifier
2026 — Unified bot logic (Telegram + MAX)
Problem
Two messengers needed the same flows without duplicating code.
Engineering
BotHandler holds all logic; TelegramAdapter and MaxAdapter implement MessengerInterface; same webhook flow.
Business value
One codebase for two channels; consistent UX and fewer bugs.
Tech
PHP, Telegram Bot API, MAX Bot API, MySQL bot_user_states
StaffProBot Platform
Engineering log
Generated from `doc/changelog-entries.md`.
Run endlog pipeline to refresh this file.
2026 — Фаза 1: docs foundation и endlog протокол
Problem
Нужно унифицировать документацию и правила endlog для перехода к self-updating docs-driven платформе.
Engineering
Добавлены стандартизированные doc-файлы (ru/en), project-manifest.yaml, integration manifests и единый протокол #endlog в rules.
Business value
Проект подготовлен к автоматической синхронизации документации и генерации портфолио.
Tech
Markdown, YAML, Cursor rules.