← سند dashboard All docs

Published copy of sanad/v2/V2-ROLLOUT-STATUS.md · source updated 8 Nov 2026 18:56 Asia/Riyadh · synced 8 Nov 2026 18:57 Asia/Riyadh. UUIDs kept (legacy/hand publish; not passed through the secret redactor).

سند v2 rollout status

Internal dashboard document. Not a public marketing page. Not a claim that all of v2 is live.

What is live (verified)

Stage 1 — pricing only is live on sanad.wa3e.ai.

Plan Price Notes
7-day trial 149 SAR Up to 7 applications. The client approves each application.
1 month 299 SAR Manual renewal
4 months 999 SAR Manual renewal
12 months 2,508 SAR Manual renewal

All four plans renew manually. No surprise charges.

Stage 1 being live does not mean v2 as a whole is live.

What is not live / must not be claimed

Topic Current state
Rest of v2 (beyond Stage 1 pricing) Pending. Later stages only after they are built, previewed and verified.
Tabby checkout Not live. Isolated QA sandbox only: tabby-sandbox.sanad-96k.pages.dev (deploy 09fcd298). Production checkout is unchanged. End-card Tabby logos (creative rule P23) are not a live-checkout claim.
Interview-prep pack Do not claim it is built. Claim only after an owner and pack are verified. They are not verified now.
Voice model UNRESOLVED. The approved A–F GO v2 confirmation (Emily chat, 17:22 Asia/Riyadh, 8 Nov 2026) says: v2 specifies eleven_v4; v1 locked eleven_v4_turbo. This needs an explicit choice rather than a silent switch. Do not pick a model or treat either as the only approved default.
“Up to 300 applications” O7 is UNDECIDED. Uptal’s public “up to 300” figure is a competitor claim, not an approved سند cap. Do not write 300 as our cap.
Spend Every spend needs a separate, direct owner approval.
External sends Every exact external message needs its own approval, after Copy Humanizer and Emily’s check.
Recovery automation, unapproved templates, new ads, new per-client bots, Studio Out of GO v2 scope. Not started as part of this rollout.
Boosts Not authorised by this GO.

Content manager correction (5:08 PM Asia/Riyadh, 8 Nov 2026)

Bot ack status (after the GO v2 instruction)

Acked, and making internal-only instruction and check updates (no client-facing text changes, no sends, holds kept). File-change reports are still pending:

Missing an ack for this staged rollout (list them as missing, not as done):

O1–O15 remain unresolved

These are open items from the 8 Nov v2 master PDF. They are not adopted as defaults.

ID Topic Note
O1 Week 1 grid vs two-reels-plus-one-carousel cadence Unresolved
O2 Pillar shares Unresolved
O3 Abdulaziz voice / Soul IDs Unresolved
O4 ManyChat paid plan Unresolved
O5 Scheduled WhatsApp check in the v2 open list Remains an open v2 item. Separately, the inbound WhatsApp check was turned back on 8 Nov (every 5 hours). That independent instruction is not “adopting O5 as a v2 default”.
O6 Recovery offer (code vs trial) Unresolved. No recovery automation in this GO.
O7 Monthly application cap per plan UNDECIDED. Do not publish an approved cap. Do not use 300 as ours.
O8 Credit the 149 trial toward a paid plan Unresolved
O9 Pause or transfer if hired early (4- and 12-month) Unresolved
O10 White Friday offer Unresolved
O11 Free CV match preview before paywall Unresolved
O12 Negotiation response-time promise Unresolved
O13 Carousel templates C, E, F, G, H, M Unresolved
O14 Snapchat, LinkedIn Unresolved
O15 Who owns the Ads bot role Unresolved

How to read the two master PDFs

File Status Use
Master Document v1 (4 Nov 2026) Superseded as the current master wherever it disagrees with the 8 Nov v2 PDF or with this rollout page Immutable historical copy. Do not rewrite it.
Master Document v2 (8 Nov 2026) Current compiled v2 text, read with this page Several lines in that PDF (Tabby listed with live payments, interview-prep described as built, Social Media running the Content Engine, treating O1–O15 proposals as ready defaults) are not verified live state. This page is the correction layer.

v1 remains the reference for client-operations runbooks until a later verified stage changes them. Historical dashboard locks under /sanad/locked/ stay published and are not rewritten.

What this update does not do