offplan · online
Session · conv-10

Session CONV-10

Donesessionconv-10

Resume Prompt

Continue Sergey's plan for 2026-04-28 (saved at docs/tomorrow-2026-04-28.md): (1) finish competitor research — 5 remaining after the 3 done with Claude yesterday; (2) finalise brandbook v1.1 review — last session added 10 implementation-idea callouts across all token sections, check nothing else needs them; (3) work through plan edits/ideas — focus on freshly-added Фаза 1.9 (Operator Dashboard, staff.offplan.online) at end of Stage 1, plus any open questions in 1.9.1 (AuditLog retention), 1.9.2 (2FA + IP allowlist), 1.9.6 (payment provider — Stripe/PayTabs/Telr/hybrid); (4) review what was/wasn't done from Monday plan. Also: Phase 1.9 was added AFTER Sergey sent the plan to Ilya — flag whether Ilya needs a follow-up. Visual mockup of staff panel: docs/staff-panel-preview.html.

Summary

Covered three concurrent threads. (1) Completed brandbook v1.1 implementation guidance — added 10 dashed-gold "implementation idea" callouts across all token sections (spacing, shadow, motion, full :root CSS vars, Figma-confirmed values table, colour decisions, glass tokens table, status tokens, cards anatomy, navigation specs), each framed deferentially as suggestions to the tech team. (2) Designed and built the Operator Dashboard concept (staff.offplan.online) — separate internal staff tool to manage studio clients. Single-page HTML mockup at docs/staff-panel-preview.html with sidebar nav, KPI row, filterable clients table with 8 fake studios, slide-out client detail drawer with 7 tabs. (3) Integrated the dashboard into the launch plan as Фаза 1.9, end of Stage 1 (so it ships before pilot launch). 8 sub-tasks 1.9.1–1.9.8: data model (Subscription/Payment/AuditLog), operator auth + subdomain, overview page, clients list+drawer, user management actions, provider-neutral payments page, audit log, operator settings. Visual appendix updated. User saved 4 tomorrow tasks to docs/tomorrow-2026-04-28.md.

Changes

Decisions

Brandbook callouts framed as suggestions, not directives. Sergey explicitly said "I don't want to appear or do competition with tech team." Each callout uses dashed gold border (vs solid for regular callouts), starts with "Implementation idea" eyebrow, ends with phrasing like "no action needed from product side." References specific tools (Style Dictionary, Figma Tokens plugin, Tailwind, MUI, Radix, shadcn) so the tech team has concrete reference points without feeling told what to do. Rejected: prescriptive "you should do X" language.

Subdomain staff.offplan.online chosen over ops.offplan.online. Sergey asked "what does ops mean?" — that was the test: if it's not intuitive to him, it won't be intuitive to a future support hire. Plain English wins. Other options rejected: admin.offplan.online (would confuse with the client admin panel), internal.offplan.online, team.offplan.online.

Operator dashboard placed in Stage 1 (Phase 1.9), not Stage 2. Rejected: deferring to pilot-launch phase. Reasoning: the moment a real studio signs up, the team needs to manage them — DB-console admin doesn't scale and isn't attributable. Audit log included in Phase 1 for the same reason — cheap to add early, expensive to retrofit later.

7-day trial (Sergey-confirmed) instead of the 14-day default I'd suggested.

Client-side roles deferred to Stage 4. User: "I am not sure currently about roles lets do without it." Phase 1 only needs operator visibility — the Owner/Admin/Editor/Viewer model on the client side is a separate architectural decision Ilya will make later. Operator-only model for now.

Provider-neutral payment adapter pattern. No payment provider chosen yet (Stripe / PayTabs / Telr / hybrid — open question). Decision: build the payments page UI against a normalised Payment record schema; manual entry adapter today, real provider plug-in deferred to Фаза 1.5. Keeps UI work unblocked and survives provider changes.

Single-page mockup preview chosen over multi-page (Sergey: "maybe we can do it more shortly?"). Saved ~30 minutes vs full multi-page version. Single page covers sidebar + top bar + KPIs + filterable table + slide-out drawer = enough surface to react to.

Next Steps

  1. Tomorrow (2026-04-28) per docs/tomorrow-2026-04-28.md: continue competitor research (5 remaining), finalise brandbook, work on plan edits/ideas, review Monday plan completion
  2. Share Фаза 1.9 spec with Ilya for tech estimate (current rough estimate: 5–8 weeks for one developer); flag that 1.9 was added AFTER the plan was first sent
  3. Resolve open question on payment provider (Stripe / PayTabs / Telr / hybrid) — needed for Фаза 1.5 to proceed
  4. Decide on 2FA + IP allowlist scope for operator auth (1.9.2 open questions)
  5. Decide on AuditLog retention policy (1.9.1 open question)
  6. Decide hard-delete (vs soft-suspend only) — Phase 1 or Phase 2 (1.9.5 open question)

Open Questions

Context for next session