Plan — Launch Plan v3 corrections (CONV-11) · plan

Goal

Apply the corrections batch accumulated during CONV-10 and CONV-11 to the three launch-plan files. Concretely:

Cross-reference Ilya's tech-team backlog (received 2026-04-28) against the plan and apply [BL] (in backlog) and [OPL] (offplan.online side designing) markers across confirmed positions.
Backfill Phase 1.9 (Operator Dashboard) into the markdown — currently it exists only in the HTML version.
Re-scope Phase 1.9 from "build from scratch" → "extend existing Super Admin Panel" (confirmed during CONV-11 after Sergey shared Super Admin Panel screenshots — the panel already exists with project list, feature flag toggles, asset uploads, and action log).
Add four new sub-phases to Stage 3 + Stage 4 for items that emerged from the backlog discussion.
Add suggestion callouts for tech team (Organisation/Tenant entity gap + DB security ideas) framed deferentially per Sergey's guidance — "we are not tech team and we should respect their work and knowledge."
Replace the Operator Dashboard preview in the visual appendix with the refined operator-panel-v1.html mockup and add a description block.

When complete, both plans/launch-plan-v3.md and docs/launch-plan-v3-full.html should be in sync and accurately reflect:

which phases are already in Ilya's backlog (no duplication of effort)
which phases offplan.online side is actively designing
the corrected, narrower scope of Phase 1.9 given the existing panel
the new items surfaced by the backlog cross-reference

Approach

Edit-in-place across three files. No code changes — pure content editing. Apply changes in 8 ordered groups so each can be reviewed independently without state leaking between groups. Pause for user review after Group 3 (Phase 1.9 reframe) per the agreed checkpoint, then continue.

The markdown is the canonical source per CLAUDE.md. The HTML is the stakeholder-facing version. The visual appendix is the iframe-based companion. All three must stay consistent.

Steps

Group 1 — Markers section (legend)

Files: plans/launch-plan-v3.md (line 71–87), docs/launch-plan-v3-full.html (Markers section, around line 342)

Add two rows to the markers table:

Маркер	Значение
[BL]	Уже в backlog у tech team (Ilya) — не дублируем усилия, дожидаемся апдейта
[OPL]	offplan.online side — мы (Sergey + Claude) активно проектируем / уже сделали мокапы

Group 2 — Add Phase 1.9 to markdown

Files: plans/launch-plan-v3.md (insert at line 1336, between Phase 1.8 closing and # Стадия 2)

Copy Phase 1.9 from docs/launch-plan-v3-full.html (lines 1656–1838) into the markdown using the same heading convention as other phases. Convert HTML markup to markdown. Sub-phases 1.9.1 through 1.9.8.

This is a literal port — corrections happen in Group 3.

Group 3 — Phase 1.9 reframe + scope corrections (PAUSE FOR REVIEW)

Files: both (markdown after Group 2, and HTML)

Intro paragraph rewrite (in both files):

Old: "Внутренний инструмент для команды offplan.online — отдельная staff-панель на subdomain staff.offplan.online, чтобы управлять клиентами-студиями с первого дня после запуска…"

New direction: emphasise this extends the existing Super Admin Panel (which already has project list, per-project feature flag toggles, project managers, asset uploads, action log per Sergey's screenshots from CONV-11). Phase 1.9 = adding multi-tenant client/subscription/payment management on top of what exists. Reference operator-panel-v1.html mockup.

Sub-phase corrections:

1.9.1 — Fix dependency line. Currently: *"Зависит от: existing Org/User/Project."* The Organisation entity does not yet exist (this is the gap we're flagging in the suggestion callout). Replace with: *"Зависит от: Phase 1.2.1 (Organisation/Tenant entity — design once, share with Operator Dashboard)."*
1.9.2 — Simplify scope. Move 2FA + IP allowlist out of Phase 1 scope, mark as "Phase 2 of 1.9 — добавляется после первых 5–10 paying студий". Phase 1 keeps basic auth (email + password + session).
1.9.6 — Simplify. Manual entry adapter only in Phase 1; real provider integration (Stripe / Paddle / PayTabs / Telr) deferred and cross-referenced to Phase 1.5. Remove provider-specific webhook sub-tasks from this sub-phase. Note: Settings page in 1.9 includes a "Payment Provider" placeholder card (see operator-panel-v1.html Settings page).
1.9.7 — Simplify. Phase 1 = basic capture + viewer. Advanced filters (multi-tenant search, full-text search, JSON diff display) → Phase 2.
1.9.8 — Defer entirely to Stage 2 (operator team management + email templates). Mark as "перенесено в Стадию 2".

Effort signal: rough estimate drops from 5–8 weeks → 3–4 weeks given the existing panel covers ~40% of the surface.

🛑 PAUSE for user review after this group.

Group 4 — Suggestion callouts (DB security + Org entity gap)

Files: both, in Phase 1.2.1 (markdown line 250 / HTML data-model section)

Two callouts using the same dashed-border deferential pattern from the brandbook (10 callouts already established with this pattern in docs/brandbook/v1.html).

Callout A — Organisation/Tenant entity gap:

Implementation idea — Organisation entity as shared prerequisite. The plan references org_id in Phase 1.2.x and Phase 1.9.x but the Organisation table doesn't yet exist in the current data model. Suggesting we design it once during Phase 1.2.1 (shape: id, name, subdomain, plan, status, created_at, owner_user_id) and have both Phase 1.2 and Phase 1.9 consume the same shape. No action needed from product side — flagging in case useful.

Callout B — DB security ideas:

Implementation idea — DB security checklist (suggestions only). Surfacing common patterns the tech team is likely already familiar with, for completeness:

ORM over raw SQL where reasonable (parameterised queries)

Cross-tenant filter checks at query layer (every query scoped by org_id)

Mass assignment protection on all PATCH endpoints

Audit log table append-only at the DB level

Sensitive fields excluded from logs/error responses

Connection pool limits configured

No action needed from product side — purely as a reference.

Cross-reference Callout A from Phase 1.9.1 (after Group 2 brings 1.9 into markdown).

Group 5 — New sub-phases (4 items)

Files: both

5a. New sub-phase 3.3.4 — Visual Debug Mode `[BL]`

Insert in Phase 3.3 (Admin UX v2 Improvements) after 3.3.3 Audit log. Status: [BL] — already in Ilya's backlog, marked "в работе".

Что это: Режим визуальной отладки в админке — помогает пользователю понять почему загрузка не сработала (неправильный формат файла, размер, отсутствует обязательное поле, конфликт с существующей сущностью). Уменьшает support burden.