Book Design Corporation

Назначение

Book Design Corporation — направление DesignCorp для книг и Amazon KDP: стратегия книги, производство рукописи, редактура, обложка, верстка, KDP-подготовка, листинг, A+ Content, Amazon Ads и развитие серий.

Статус

• Статус: live MVP, P0 client-service cash offer.
• Репозиторий: https://github.com/DesignCorporation/book-designcorp.
• Workspace: /home/admin/workspace/BookDesignCorp.
• Prod: https://book.designcorp.eu -> 127.0.0.1:3220.
• Dev: https://dev.book.designcorp.eu -> 127.0.0.1:3221.
• Runtime: /opt/designcorp/book-designcorp/prod/current.
• Nginx: /etc/nginx/sites-available/book.designcorp.eu.
• Services:
  • book-designcorp-prod.service
  • book-designcorp-dev.service
• GitHub Project: https://github.com/users/DesignCorporation/projects/14.

Связанный product workspace

Book Library / KDP Workspace — закрытое приложение для производства книг, вариантов, KDP exports, Amazon Ads/KDP report snapshots и MCP workflow.

• Статус: live private workspace.
• Репозиторий: https://github.com/DesignCorporation/AmazonCookBook во время миграции имени.
• Workspace: /home/admin/workspace/LibraryBookDesignCorp.
• Prod: https://library.book.designcorp.eu -> 127.0.0.1:3215.
• Dev: https://dev.library.book.designcorp.eu -> 127.0.0.1:3213.
• Runtime: /opt/designcorp/bookdesigncorp/prod/current.
• Shared state: /opt/designcorp/bookdesigncorp/prod/shared.
• Nginx: /etc/nginx/sites-available/library.book.designcorp.eu.
• Services:
  • bookdesigncorp-prod.service
  • bookdesigncorp-dev.service
  • bookdesigncorp-mcp-prod.service
  • bookdesigncorp-mcp.service
  • bookdesigncorp-amazon-ads-daily-sync.timer
• Legacy redirects:
  • https://amazoncookbook.designcorp.eu -> https://library.book.designcorp.eu
  • https://dev.amazoncookbook.designcorp.eu -> https://dev.library.book.designcorp.eu

Коммерческая роль

На 5 июля 2026 Book Design Corporation — ближайший P0 cash offer: готовые Amazon/KDP-книги для клиентов.

Канонический sales-пакет: Book Client Services Launch Pack. Операционный sprint для поиска первых клиентов: Book Prospecting Sprint.

Разделяем три контура:

1. Client book services: DesignCorp продает клиенту production package и передает KDP-ready assets, listing materials и launch checklist.
2. Owner personal KDP: личные книги владельца остаются отдельно от company P&L, payout и tax решений.
3. Future company-owned publishing / SaaS: возможный рост через собственные publishing assets или Book Library SaaS, но только после accounting/VAT/IP решения.

Стартовые пакеты:

Package	Promise	Output
Book Audit	Найти, почему книга/листинг не готов к продажам	Аудит ниши, обложки, title/subtitle, listing, KDP readiness
Ready Cookbook	Быстро получить template-led cookbook для KDP	100–120 recipes, стандартный или premium template, KDP checklist, optional Kindle
KDP Launch Pack	Подготовить одну книгу к KDP запуску	Manuscript polish, cover direction, interior, metadata, upload checklist
Premium Book Build	Сделать книгу под клиента end-to-end	Strategy, manuscript, editing, cover, interior, listing, A+ content
Series System	Построить повторяемую publishing-систему	3-5 book roadmap, templates, brand, production SOP
Ads/Optimization Retainer	Улучшать уже запущенную книгу	Amazon Ads setup/review, keywords, listing optimization, reports

Ready Cookbook public page:

• Route: https://book.designcorp.eu/books and localized /ru/books, /ua/books, /it/books.
• Currency: USD for public international pricing.
• Standard Cookbook: from $590, 100–120 recipes, up to 100 pages, standard template.
• Premium Cookbook: from $990, stronger positioning/design and Kindle included.
• 3-Book Cookbook Series: from $1,590, three connected cookbooks in one niche.
• Queue: ready-cookbook, first action catalog-fit-check.
• Public secrecy rule: do not list concrete cookbook niches, sample titles or demo books on the website.
• Private funnel: show niche directions, demo covers and sample pages only after the first brief / fit check through the Telegram bot.
• Telegram contact: all public request CTAs, package CTAs, brief CTAs and Telegram links go to @BookDesignCorpBot / https://t.me/BookDesignCorpBot for private Ready Cookbook brief and demo requests.
• CTA deep links should preserve intent and page language when possible: ?start=en_brief, ?start=ru_brief, ?start=uk_brief, ?start=it_brief, ?start=en_book_audit, ?start=ru_standard_cookbook, ?start=uk_private_demo, ?start=it_kdp_launch, ?start=ru_premium_book_build, ?start=uk_cookbook_series, ?start=it_book_growth.
• Boundary: no guaranteed Amazon sales/rank/reviews; health/nutrition claims require review; client keeps KDP account unless a separate publishing agreement is approved.

Ближайшие задачи

1. Упаковать P0 book-service landing/offer: пакеты, deliverables, exclusions, CTA.
2. Сформировать invoice-ready scope: цена/диапазон, payment schedule, acceptance criteria, VAT/accounting note.
3. Подготовить public-safe proof/case study без раскрытия личных KDP payout details.
4. Расширять structured intake на основе первых реальных заявок и переносить подтвержденные поля в CRM/pipeline.
5. Настроить production SMTP для формы заявки.
6. Поддерживать текущие публичные локали EN/RU/UA/IT без польской public route tree.
7. Перевести production deploy на GitHub Actions.
8. Запушить bookdesigncorp infra-коммит и включить BOOKDESIGNCORP_AUTO_DEPLOY_PROD=true после owner approval.
9. Вести первый prospecting sprint: 40 prospects -> 20 qualified -> 20 approved outreach attempts -> 2 briefs -> 1 proposal.

Lead intake

Публичная форма /contact и локализованные варианты работают как structured intake для client book services, а не только как общий контакт.

Форма собирает:

• контакт, company/role и выбранный service interest;
• stage, type/niche, language, target format, Amazon marketplace и business goal;
• timeline, budget range, KDP account owner и risk flags;
• message, locale, intent, template, UTM, referrer и landing path.

/api/contact сначала пишет JSONL-запись в CONTACT_LEAD_DIR, затем отправляет email. В lead record и email subject добавляется routing:

• queue: book-diagnosis, book-audit, ready-cookbook, kdp-launch, premium-book-build, series-system, book-growth;
• priority: high, review, normal;
• firstAction: diagnosis, audit-fit-check, catalog-fit-check, kdp-readiness-check, scope-estimate, series-scope-check, growth-review, risk-review.

Если SMTP credentials отсутствуют, но JSONL-запись сохранена, заявка считается принятой как stored.

Lead pipeline:

• Каждая принятая заявка пишет событие в lead-pipeline-YYYY-MM.jsonl.
• Директория: LEAD_PIPELINE_DIR, fallback CONTACT_LEAD_DIR, затем TELEGRAM_LEAD_DIR.
• Начальный статус: new.
• SLA: первый ответ до 15 минут в рабочее окно, next step до 48 часов.
• CLI отчёт: corepack pnpm leads:report в /home/admin/workspace/BookDesignCorp.
• CLI смена статуса: corepack pnpm leads:status <leadId> contacted|brief|proposal|deposit|won|lost|closed "note".

Telegram/private funnel:

• Public Telegram contact for BookDesignCorp is @BookDesignCorpBot / https://t.me/BookDesignCorpBot.
• Do not route BookDesignCorp leads to @designcorp; that handle is not the sales funnel.
• Production webhook is set to https://book.designcorp.eu/api/telegram/webhook.
• Runtime env only: TELEGRAM_BOT_TOKEN, TELEGRAM_WEBHOOK_SECRET, TELEGRAM_WEBHOOK_URL, TELEGRAM_LEAD_DIR, optional TELEGRAM_MANAGER_CHAT_IDS.
• Production env file: /opt/designcorp/book-designcorp/prod/shared/.env.local; private local token/secret copies: /home/admin/private/book-designcorp/.
• Webhook requires x-telegram-bot-api-secret-token; no secret means the endpoint returns 503, wrong secret returns 403.
• Telegram JSONL records go to TELEGRAM_LEAD_DIR, falling back to CONTACT_LEAD_DIR.
• Business Telegram requests also write to lead-pipeline-YYYY-MM.jsonl; pure language switches are not treated as sales leads.
• If TELEGRAM_MANAGER_CHAT_IDS is configured, the bot sends a manager notification with lead id, queue, first action and contact label.
• Bot language defaults to English. Users can switch with English, Русский, Українська or Italiano; chat-level language state is stored in telegram-language-state.json in the same runtime lead directory when configured.
• Demo requests route to ready-cookbook with first action private-demo-fit-check.
• Bot replies include a visible language menu plus quick buttons for Brief, Pricing/Prezzi, Demo and Manager with Russian, Ukrainian and Italian equivalents after switching.
• Telegram command menu should be configured with corepack pnpm telegram:commands:set; commands include /language, /brief, /pricing, /demo, /manager, /en, /ru, /uk, /it.
• Telegram routing preserves intent: Book Audit leads use book-audit, Ready Cookbook leads use ready-cookbook, KDP Launch leads use kdp-launch, Premium Book Build leads use premium-book-build, series leads use series-system, Growth leads use book-growth, and generic brief/human requests use book-diagnosis.
• BotFather/token setup must use VNC owner login/approval flow; no Telegram secrets in git, docs, logs or chat.

Проверка

• corepack pnpm lint
• corepack pnpm build
• TELEGRAM_WEBHOOK_SECRET=dev-secret CONTACT_LEAD_DIR=/tmp/bookdesigncorp-leads TELEGRAM_LEAD_DIR=/tmp/bookdesigncorp-telegram-smoke PORT=3233 corepack pnpm start
• POST /api/telegram/webhook with wrong secret -> 403; with matching secret -> 200 and JSONL stored.
• @BookDesignCorpBot /start -> bot reply sent, JSONL stored in telegram-leads-YYYY-MM.jsonl.
• @BookDesignCorpBot Русский -> language state stored in telegram-language-state.json; next /start uses Russian. English switches it back; Українська switches to Ukrainian; Italiano switches to Italian.
• @BookDesignCorpBot /start ru_brief, /start uk_brief and /start it_brief -> same brief intent, but response language follows the prefix.
• @BookDesignCorpBot demo -> first action private-demo-fit-check.
• @BookDesignCorpBot /start book_audit -> queue book-audit, first action audit-fit-check.
• @BookDesignCorpBot /start kdp_launch -> queue kdp-launch, first action kdp-readiness-check.
• @BookDesignCorpBot /start premium_book_build -> queue premium-book-build, first action scope-estimate.
• @BookDesignCorpBot /start cookbook_series -> queue series-system, first action series-scope-check.
• @BookDesignCorpBot /start book_growth -> queue book-growth, first action growth-review.
• BOOK_SMOKE_BASE_URL=https://book.designcorp.eu corepack pnpm smoke:client-path -> public CTA/client path smoke without creating fake prod leads.
• Local write smoke: CONTACT_LEAD_DIR=/tmp/bookdesigncorp-leads TELEGRAM_LEAD_DIR=/tmp/bookdesigncorp-telegram TELEGRAM_WEBHOOK_SECRET=dev-secret BOOK_SMOKE_BASE_URL=http://127.0.0.1:3220 BOOK_SMOKE_TELEGRAM_SECRET=dev-secret BOOK_SMOKE_WRITE=1 corepack pnpm smoke:client-path.
• corepack pnpm leads:report -> lead counts by source/status/queue plus overdue response and stale next-step lists.
• node /home/admin/workspace/skills/skill-frontend-ai-quality-gate/scripts/run-ui-qa.mjs https://book.designcorp.eu
• node /home/admin/workspace/skills/skill-frontend-ai-quality-gate/scripts/run-ui-qa.mjs https://dev.book.designcorp.eu
• curl -I https://library.book.designcorp.eu/login/
• curl -I https://dev.library.book.designcorp.eu/login/
• curl -I https://library.book.designcorp.eu/mcp -> 403
• curl http://127.0.0.1:3216/mcp/health

Rollback

1. Найти предыдущий релиз в /opt/designcorp/book-designcorp/prod/releases.
2. Переключить current на нужный релиз: ln -sfn /opt/designcorp/book-designcorp/prod/releases/<release> /opt/designcorp/book-designcorp/prod/current.
3. Перезапустить prod service: sudo -n systemctl restart book-designcorp-prod.service.
4. Проверить https://book.designcorp.eu.

Для Book Library rollback:

1. Найти предыдущий релиз в /opt/designcorp/bookdesigncorp/prod/releases.
2. Переключить current: ln -sfn /opt/designcorp/bookdesigncorp/prod/releases/<release> /opt/designcorp/bookdesigncorp/prod/current.
3. Перезапустить prod services: sudo -n systemctl restart bookdesigncorp-prod.service bookdesigncorp-mcp-prod.service.
4. Проверить https://library.book.designcorp.eu/login/ и http://127.0.0.1:3216/mcp/health.