Matches _payUpline (level > levelIndex, levelIndex = buyer.level-1). The old
depth+1 rule told #21 (Culmen) it could not catch #49's Apex buy; #21 is #49's
4th matrix upline and does catch it. Fixed in the owner alert, coaching scan,
dashboard pipeline, AI prompt, leader digest, chatbot and how-pay-works copy.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two problems with pulling the poster straight out of the recording: it caught
the walkthrough's synthetic cursor, and the hero QR was in shot. That QR
resolves to the CURRENT TEAM SPONSOR via the moving link, so anyone scanning
it off the builder entry would route around the AdRevSplit sponsor whose
{affiliateid} the entry is personalised with. Shot fresh with .qr-cta hidden.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The 88s walkthrough itself lives in the data volume at /tv/rmcircle-what-it-is.mp4
(same route as the Suite tool videos) so it doesn't ride along in the image.
Only the poster frame needs to be static.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Clearing our session was only half the problem. eth_requestAccounts returns
whichever account the wallet already has connected to the site - it never
opens the picker - so a member holding two positions could sign out, switch
accounts in MetaMask, reconnect, and be handed the same address again. Signing
with it resolved to the same position, which looked exactly like the switch
doing nothing.
This is the trap already documented in our own Triple Play guidance, and the
Triple Play is what puts members in this situation in the first place.
Switching now calls wallet_requestPermissions first, which forces the account
selector open. Only on switch, so ordinary single-position sign-ins are
unchanged. And if the wallet still returns the same address, the page now says
so - naming the address and pointing at the wallet's connected-sites list -
instead of silently redisplaying the same position.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A member holding #2 and #3 connected #3's wallet, closed the browser, came
back, and still saw #2. Not a wallet problem: the sign-in cookie lasts 30 days
and there was no sign-out anywhere on the site, so the first position he
authenticated as was pinned to that browser and the wallet was never consulted
again.
This hits precisely the people we tell to buy several positions - the Triple
Play is on /how-pay-works and in the chatbot - so it will keep happening.
Adds POST /api/public/signout (drops the server session and expires the
cookie) and a "not this position? switch" link beside the identity line on
/suite.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The moving link is team-first by design: it routes a new join to whoever needs
directs next, so the position whose link was actually clicked earns no entry
reward. Measured on #21 that came to 80 joins in seven days and zero entry
rewards, while the traffic paying for those joins was the owner's.
For a position being deliberately built out, that default is backwards. Any ID
listed in the new directDefaultIds config now behaves as ?direct=1 on its own
/join/<id> link - including every promo tool, flyer QR and downline-builder
entry that resolves through it - without needing the parameter appended.
?direct=0 still forces rotation for a single share, so the team-first behaviour
stays available rather than being replaced.
Config rather than hard-coded, and editable from the admin settings form, so
which positions get this can change without a deploy.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A member sent a nudge to #102, then went looking for what had gone out. The
only feedback was a small "Delivered to their dashboard" note, so she checked
her clipboard - which still held the unrelated "Copy plain-English summary"
text describing her OWN position. She reasonably concluded the nudge had sent
her position instead of the recipient's.
It had not: the message log shows #34 -> #102 carrying #102's own numbers.
The feature was right and the feedback was wrong, which is its own kind of
bug - a member who cannot verify what they sent will assume the worst.
Every nudge now has a Preview button that names the recipient and shows the
exact text before sending, and on success the panel shows what was sent and
to whom rather than a bare "Delivered".
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
"The money came. Where did it go?" - 4:06, Marty's voice, rendered from
specs/climb-with-your-catches.json.
Covers why 95% of qualified members cannot cover their next rung despite
having earned past it: the doubling maths, pass-overs being silent, and the
contrast with members who joined days ago and are already climbing. Ends on
the self-paced / afford-to-lose line and a teach-your-two close. No income
claims, no member identified.
Shareable at /v/rmc-climb-catches-d15c3f03fa.mp4 with a poster frame
alongside it.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The upgrade panel showed a price, a funded badge and a button. Nothing on it
said what the member would get. 53 of 87 qualified members in the org are
parked at Ascensus, and a panel that reads as a bill is part of why.
It now leads with what the rung unlocks, in the member's own numbers: the
generation it extends reach to, how many people they already have sitting
there, and what each of those pays when they climb. genCounts already existed
in getOrgShare; this just points it at the member instead of at the admin.
The line that matters most is arithmetic, not persuasion: because every rung
costs exactly twice the last, the first catch at the new level is exactly
double what the upgrade cost. That is Lesson 8's whole argument, and the
panel now makes it where the decision is actually taken rather than leaving
it in a lesson nobody opens at the right moment.
Wrapped in try/catch — if the org walk fails the panel renders as before.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The AI system prompt still carried "CURRENTLY IN PRIVATE TEAM BETA: do NOT
proactively promote it; if a member asks, say it is being finalized and will
be announced soon." That stopped being true when the Suite launched to the
org. /suite has been serving publicly, and the best-performing massifly story
to date sells precisely this — so the bot was deflecting questions about the
strongest answer we have to "what's the actual product".
The prompt now says it is live, open to every position, and should lead any
what-do-I-actually-get question.
chat.js had no Suite entry at all, so the canned side never mentioned it
either. Added one covering the product question in the words people actually
use, with the level ladder and the honest note that in-development tiles are
labelled as such.
Both sides updated together — they drift apart the moment only one is
touched, which is how this one survived the launch.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The Sponsor Queue table carries min-width:850px but the 1.6fr side of the
split only handed it about 800px, so the Actions column was clipped — the
Reset button cut in half and the delete button off-screen entirely.
Sponsor Queue and Member ID Submissions now run the full width. Add Sponsor
moves below the queue as a single collapsible row of fields instead of a
narrow two-column form in a sidebar, which is both less tall and no longer
squeezing the table next to it.
The rule this follows: a card holding a .table gets the whole width; only
compact forms share a row. Settings keeps its split — those are all short
forms.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The page was a fixed 1.5fr/.75fr split — ten tall panels on the left, four
short config forms on the right. The right column ran out about a quarter of
the way down, so the rest of the page scrolled past an empty gutter, and
finding anything meant scrolling through everything.
Five tabs now, each using the full width: Team (queue, add sponsor, coaching
radar, award capacity, messages), Traffic (conversions, org vs network),
Members (submissions, lookup, matrix), My Money (positions income), Settings
(AI chat, SendGrid, public page).
The panels themselves are untouched — same markup, same ids, same JS. Only
their grouping changed. Panes are moved in the HTML rather than by script, so
the layout does not depend on JS running; the tab file only toggles which
pane is visible and remembers the last one.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
It was sitting between the login panel and #adminView — outside the admin
view entirely, so it rendered above the page header and showed on the login
screen to anyone who loaded /admin.
Now it sits after the Coaching Radar, which is the panel that tells you who
needs a nudge; this is the lever for nudging them. Collapsed by default and
the log is capped at a scrollable 240px, because awarding is occasional and
the log grows every month.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The site sends script-src 'self'. The panel's logic was an inline <script>
block, so the browser refused to run it: window.agBoot was never defined,
admin.js's guarded call did nothing, and the "What" select stayed empty with
no console-visible cause beyond the CSP report.
admin.html had no inline scripts before this panel — the extraction restores
that, so the next person adding a panel copies a pattern that works.
Fourth thing this CSP has silently broken. Inline scripts are not an option
on this site; new panels ship as files.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The panel fetched its tool list on DOMContentLoaded — which fires while the
admin page is still showing the login form. The request 401'd, the handler
returned silently, and the "What" select was left permanently empty with no
path back.
Loads from the same post-login block as the coaching radar and messages
panels now, plus a refetch if the select is opened while still empty.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Marty asked for a way to grant impressions to anybody, labelled as an admin
bonus. Team Grants already did this for leaders, but only within their own
organisation and only out of a level pool.
adminGrant() is deliberately a different thing: it comes from no pool (the
team is not a position and has no allowance), it can reach ANY registered
position rather than only someone downline, and it carries a reason that
survives in the ledger. Recorded with by:0 so nothing downstream mistakes it
for a leader's grant — the member's own page renders those as "the team"
rather than "#0".
The route verifies the position exists on-chain before crediting it; a typo
would otherwise sit in the ledger crediting nobody, and it would be invisible
until someone went looking.
Awards land on top of whatever the level already allows and expire with the
month like every other allowance. The admin page lists what has been awarded
this month, so bonuses stay auditable rather than vanishing once given.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
My own sweep created this. Deactivating an ad ZEROES `remaining` on the
network, and for banners — where that column counts UP — zero reads as
"served nothing". So every campaign the sweep closed flipped to 0 served /
2,500 left, despite the ledger correctly recording served=2500,
completed=true.
Closed campaigns now read from what we recorded at the time rather than
re-deriving from a counter that no longer holds anything. Live campaigns
still compute from the network, per placement type.
Also removed the em-dash placeholder that blanked LEFT for stopped rows —
there is a real number to show — and made stop()'s error path assume fully
served rather than fully unserved, since guessing high would refund
impressions that had actually been delivered.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Marty: "if it's just gonna keep running, why would anyone use impressions to
place the ad at all?" He is right, and my previous answer — calling the
over-delivery a bonus — papered over a real flaw.
Banner placements on this network have no cap. Left alone, 2,500 impressions
buys an ad that runs until expiry, which makes the allowance decorative and
the whole level ladder (2,500 at Scintilla to 150,000 at Corona) worth
nothing. Nobody would ever spend the larger allowance for an identical
outcome.
Two changes so the impressions are genuinely the thing being spent:
sweepCompleted() deactivates any campaign that has served its purchased
amount. Runs 90s after boot and every 15 minutes, batches its stat reads, and
only touches campaigns that are live, un-stopped and provably at or past what
was bought. Nothing is refunded — they delivered in full. It re-reads the
ledger after the network calls, since deactivating takes real time and
another member may have launched in that window.
New campaigns get days:30 instead of days:365. The allowance is monthly, so a
campaign outliving the month it was paid from is the same bug by another
route. Belt and braces — whichever ends it first.
Copy corrected too: "still serving as a bonus" became "served in full —
closing out", and the footnote now states plainly that a campaign ends when
it has served what was bought.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Marty asked why banners still show "running" with 0 left. They genuinely are
running — banners on this network have no cap. The counter runs past the
purchase and the ad keeps rotating until its 365-day expiry, so a
fully-delivered banner is still serving. #2707 is at ~6,129 on a 2,500 buy.
"running / LEFT 0" reads as broken though, so the row now says "delivered —
still serving as a bonus, Stop to end it", and the footnote explains it once:
the extra costs nothing further against their allowance, and Stop actually
ends it on the network.
Worth flagging what this does NOT do: nothing auto-stops a banner at its
purchased amount. Members get free over-delivery, which is fine on our own
inventory, but it means every banner ever launched keeps rotating for a year
unless someone stops it. If that becomes noisy, the fix is a scheduled job
that deactivates ads once served >= bought — deliberately not built now,
since it needs a cron and the over-delivery currently costs nothing.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Marty reported banner impressions never moving while text ads did. They were
serving the whole time — we were reading the counter backwards.
Measured against the live network, because none of this is documented:
TEXT `remaining` counts DOWN from the purchase to zero.
ad 2689: 1,111 left mid-flight, 0 once complete.
BANNER `remaining` counts UP as impressions deliver, straight past the
amount bought. ad 2707: 3,521 one day, 6,129 the next, on a 2,500
buy. Every live banner sits above its purchase and rising.
Reading both as count-down made every banner report "0 served" while quietly
delivering thousands — and made stop() treat delivered impressions as
unserved, so stopping a finished banner refunded the lot. That was giving
back inventory that had already been spent on the network.
interpret(kind, bought, stat) now resolves both directions in one place, used
by stop() and by the table. served + left always reconciles to what was
bought and neither can exceed it.
This also supersedes the earlier "counter drift" note: the drift WAS the
count-up, seen through a count-down lens.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
A 2m35 tour of all 19 tools at 50,000 feet — what each one is, tier by tier,
without opening any of them. It scrolls the wall as it names each level, so
the viewer sees the thing being described.
Recorded the same way as the per-tool walkthroughs: narration generated first
in Marty's cloned voice, then the browser driven on the measured clip
timings, so speech and scrolling cannot drift apart.
Closes with the line that matters most: these tools make the work lighter,
they do not do the work — getting your two and helping them get theirs is
still the job. Same reason the individual walkthroughs carry their caveats
out loud rather than only on the page.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Janie linked successfully and the dashboard kept showing the Connect button,
so a working link looked like a failed one — and she had no way to tell which.
The Messages panel had no idea about link state: msg-inbox never reported it.
It now returns tgLinked (from tgbot.memberChat) on the response the panel
already fetches, so this costs no extra request. Linked members get a
confirmation telling them where their pings arrive and how to open the Mini
App, instead of a button asking them to do something already done.
Third variant today of the same failure: the interface not knowing a state it
could easily have known, and the member left guessing. The bot had it too —
telling an already-linked member their code had expired.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Printable Handouts and Generation Pay both have a .nav-actions bar but never
loaded nav-dash.js, so they got neither the dashboard shortcut nor the Suite
link. Every other member page already includes it.
Also worth recording: the audit's 'no nav on Fast Start / Weekly Rhythm' flag
was the audit's own fault — those are print sheets carrying .scr-nav rather
than .nav-actions, and the screen-only bar shipped correctly.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Ran a signed-in walkthrough of 23 pages at desktop and mobile widths. Three
real problems.
1. ELEVEN Suite pages showed "My Dashboard" TWICE — they ship their own
button and nav-dash.js injected a second one. It now bails if a /my link
is already present.
2. The Suite link was hide-mobile, so on a phone — where most members are —
the toolkit was invisible on every page except the dashboard. That is
precisely backwards for the tool we just launched to the whole org. It is
now visible at every width.
3. Fast Start and Weekly Rhythm had NO navigation at all and an unclickable
brand mark: a member landing there was stuck with the browser back button.
They are PRINT sheets, so bolting the site header on would have wrecked
what they are for — they now carry a small screen-only bar that is hidden
by @media print.
Printable Handouts and Generation Pay were also missing the Suite link; they
pick it up from nav-dash now that it is no longer hidden on mobile.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The Circle Suite went live to all 216 positions, but nothing outside its own
pages linked to it. Members could only reach it by knowing the URL, which
means most of them could not reach it at all.
The dashboard now leads with it: "My Tools" is the primary action, and Promo
Tools drops to secondary — the Promo Center is itself a level-1 Suite tool, so
the Suite is its parent rather than its sibling.
Everywhere else it rides the existing nav-dash.js injection, which already
runs on every member page and already knows who the visitor is. Same identity
test as the dashboard button: if we know who they are, they hold a position,
and a position is a licence to the toolkit. Prospects still see nothing.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Janie can now sign in from Trust's DApp browser but cannot link Telegram.
Cause: the handler called window.open(url,'_blank'), and wallet DApp browsers
routinely block programmatic window.open. The call does nothing, no error is
raised, and the member is left staring at an unchanged screen.
Now the button fetches the link and then renders a real anchor for the member
to tap — an actual tap is handled by the OS, which is what launches the
Telegram app — plus a "copy the link" button with an execCommand fallback for
webviews that refuse both.
Third failure today from the same root assumption: that members are in a
normal browser. They are usually in someone's webview.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Janie's screenshot showed the X / chevron / share / kebab chrome of TELEGRAM'S
in-app browser, not Trust's DApp browser. She tapped her sponsor's link in a
Telegram chat, Telegram opened it in its own webview, and that webview can
never hold a wallet. The page said "no wallet in this browser", she said she
was using Trust — both true, completely at cross purposes.
Our advice made it worse: "open your wallet's browser and type the address" is
useless to someone whose whole reason for being on the page is that they
tapped a link.
Now we name the browser they are actually in — Telegram, Facebook, Instagram,
LINE, Messenger, X, or a generic Android WebView — say plainly that it cannot
hold a wallet and that this is not their fault, and give them the one useful
thing: a button that copies the address to the clipboard so they can paste it
into Trust. There is an execCommand fallback because older webviews have no
clipboard API, and leaving a button that silently does nothing would be worse
than not having one.
Detection deliberately requires the absence of window.ethereum before calling
something an in-app browser: wallet browsers ARE WebViews, and those are
exactly the ones that work. Verified against Telegram, Android WebView, Trust
(correctly ignored) and mobile Safari (correctly ignored).
This will hit far more members than Janie — every link tapped inside a chat
app lands in the same trap.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Once every member from Ascensus up could hold several pages, the Funnel
Factory's differentiator became a count — the same quantity-not-kind flaw the
upper tiers had. L6 now unlocks identity instead: a member's own name,
monogram and accent colour on every page they build. Below Fastigium you have
a page on the team site; at Fastigium it becomes yours.
Three deliberate limits.
NO IMAGE UPLOADS. A logo file uploaded by a member and served from
rmcircle.team is an abuse surface — whatever they upload lives on our domain.
The mark is a monogram generated from their brand name instead: real identity,
nothing to moderate. Same reasoning that keeps Traffic Desk creative
team-only.
ACCENTS ARE A CURATED SET, not a colour picker. Every option is checked
against the dark ground, so nobody can pick something that makes their own
page unreadable and then wonder why it converts badly.
THE DISCLAIMERS ARE NOT THEIRS TO BRAND. Branding replaces the header
identity only; the footer — independent team resource, no income guaranteed,
cryptocurrency risk — is rendered by us and cannot be removed or restyled.
Co-branding, not white-labelling. Verified in the renderer.
Branding is resolved against the LIVE contract level at render time, so a
position that drops below Fastigium reverts to team identity on its own
rather than keeping something it no longer holds.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The quota and the capability used to contradict each other. An Ascensus
member was allowed 3 page builds a month, but every build overwrote the same
file — so they could build three times and never have more than one page. The
slug plumbing to do better already existed and was only exposed at level 6,
which made the Funnel Factory's differentiator a COUNT rather than a KIND, the
same flaw the upper tiers had.
Now: hold caps by level (2 at Ascensus rising to 50 at Corona), separate from
the monthly build quota. Rebuilding spends a build but needs no hold room;
adding a new page needs both. The Page Builder is a list of your pages with
view / copy link / rebuild / delete, plus a form that ADDS one instead of
silently replacing what you had.
Two things kept deliberately fixed. The first page a member builds stays at
/p/<id> forever and cannot be deleted — that address ends up on banners,
printed flyers and in people's DMs, so it must never move. Extra pages take a
slug from the headline the writer produced, de-duplicated, so the address
describes the page without anyone having to invent one.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two sign-in failures with different causes and no way to tell them apart from
the outside, so stop guessing and get the data off the member's device.
/wallet-check reports what the page can actually see: whether window.ethereum
exists, which wallet flags are set, which EIP-6963 wallets announced, the
accounts and chain the wallet returns — and critically, any CSP violation.
Our script-src is 'self' with no 'unsafe-inline', and a wallet browser that
injects its provider via a script tag would be blocked silently, producing
symptoms identical to "no wallet installed". The company dApp sends no CSP at
all, which is a plausible reason it connects where we do not. This page will
confirm or kill that theory rather than us theorising further.
"Signature does not match this wallet" was true but useless — it never said
WHICH wallet signed. It now names both the address the page asked for and the
address that actually signed, which identifies the classic multi-account case
(wallet signs with the selected account, not the one the page picked up) in
one glance.
Verified for the case in hand: 0x20E0…2248 IS the wallet registered to
position #52 on-chain, so ownership was never the problem.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two things Marty raised.
1. Member pages did not look like the rest of the site. The byline is now the
gold uppercase eyebrow used above every other h1, the heading is larger and
tighter with the last beat in gold (house style is "Team <gold>Grants</gold>"),
and the subhead steps up from 18px to a fluid 19-22px in a brighter colour.
The headline is model-written so the gold split cannot be hand-picked —
goldTail() takes the final two words, or one on a short line. Everything is
escaped before the span is added; the only markup is ours.
2. The "no wallet found" error listed five wallet names and described a DApp
tab without saying the thing that matters: you are in the wrong browser,
and here is the address to type. It now says exactly that, names the page
address, and warns that Trust on iPhone has no browser at all any more —
previously those members were reading instructions they could not follow.
Diagnosed from a real case (#34): the company dApp at thermcircle.com supports
WalletConnect, so it connects from any browser; this site is injected-provider
only, so it needs the wallet's own browser. That is the whole difference, and
WalletConnect is the actual fix — this is the stopgap.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Marty spotted rows where "left" exceeded "bought" — 3,521 remaining on a
2,500-impression purchase, with "served" reading 0 across those rows.
Reproduced against the network: on 11 of 26 campaigns the ad app's own
assigned/remaining counters have grown past what we inserted. We write
assigned = remaining = the purchased amount; later both sit higher. Actively
serving campaigns still reconcile exactly (served + remaining = bought), so
our arithmetic is right and the inputs are drifting. The cause is inside the
ionCube-encoded ad application, so there is nothing to fix at source.
Direction matters: this is OVER-delivery. Members receive more impressions
than their allowance and the ledger still only charges what they asked for,
so nobody loses anything.
The table now clamps both columns to what was actually bought, so a row
always reconciles: served + left = bought. Showing a member more impressions
remaining than they purchased reads as broken software, which costs more
trust than the bonus impressions are worth.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Replaces the roadmap with the corrected version that now carries the Circle
Method and the Circle Suite ladder alongside the original strategy content.
Every figure on it was checked against the contract before shipping: the 362
quote / 360.58 send / 326.24 sponsor split, all seven upgrade prices, both
payment streams, and the tool-to-tier mapping against the live tool wall.
The contract address was deliberately dropped from the artwork in favour of
"verify on Polygonscan" — image generation cannot render 42 hex characters
reliably, and a wrong address on a trust document is worse than none.
Aspect ratio changed (1149x1369 -> 1086x1448), so the width/height attributes
move with it; leaving them stale would reserve the wrong space and shift the
page as it loads. Converted to WebP at quality 86 (246KB, against 202KB
before) — checked at the smallest text on the sheet, since text-heavy images
blur under aggressive WebP.
Previous version kept as roadmap-v1.webp for a one-line revert.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The player was showing a blank white rectangle, which reads as broken. That
is frame zero of each recording — the instant before the page painted. Only
frame zero is white (by 0.5s the real UI is up), but frame zero is exactly
what a browser picks when no poster is set.
Each video now has a poster pulled from ~30% in, where the tool is in a
meaningful state rather than mid-intro. Posters live beside the videos in the
volume and the player derives the URL from the video's own, so adding a new
walkthrough needs no page change.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Marty asked why they start muted. Browsers only permit autoplay when a video
is muted, so "expand and play" necessarily meant "expand and play silently" —
and for these that is the wrong trade, because the narration IS the training.
A member's first visit was showing them a silent walkthrough.
So the panel now opens paused with the play button showing. Pressing it is a
user gesture, which means it plays with sound, every time. preload stays
'none' until the panel opens, then goes to 'metadata' so an open panel shows
a real first frame instead of a black rectangle.
Each bar now also carries its runtime ("· 71 sec"), so nobody has to guess
whether they are committing to one minute or ten.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Twelve narrated walkthroughs, one per Suite tool, in Marty's cloned voice.
No screen recording involved: Playwright drives and records the real UI,
ElevenLabs narrates, ffmpeg muxes. Pipeline lives outside this repo at
../video-pipeline.
Placement (Marty's call): TOP of each tool page but COLLAPSED — a one-line
"Watch the walkthrough" bar that auto-opens on a member's first visit to that
specific tool and stays shut after. A video in a separate library never gets
watched; an embedded player pushes the tool below the fold on mobile for every
returning member. First-visit autoplay is muted, so it is never a surprise
noise, and every localStorage access is guarded because it throws outright in
private windows.
Served from the data volume via /tv/<slug>.mp4, NOT from public/. That
directory is already 199MB and another 33MB of MP4 would ride along on every
deploy forever; this way a video can also be re-cut and dropped in without a
rebuild. The route implements HTTP range requests — without them the scrub bar
renders but cannot seek, which looks broken in a way people rarely report.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Marty's read was right — the upper tiers felt flat, and the reason is that
they scaled QUANTITY, not KIND. L1->L2 was a category change (you couldn't
write, now you can). Everything above L4 was a multiplier on a capability
already owned at L2: sound more like you, measure it, more pages, five at
once. Meanwhile the price doubles each rung — Corona costs ~17x Culmen. No
batch button is worth 17x a voice profile.
The fix is a change of axis. Every tool from L1 to L8 was a "me" tool, but
past the first levels this business isn't about you: get two, help your two,
teach them to teach. So the top now operates on the ORGANISATION.
L7 Team Grants — hand Suite capacity down to anyone in your own org.
Deliberately from a separate pool that the level grants, NOT out of the
leader's own allowance: making someone choose between equipping their team
and using their own tools means nobody ever grants anything. Recipients are
verified in-org against the contract. Grants can lift a tool the recipient's
level hasn't unlocked — that's the point, not a loophole. Being helped is
made visible to the recipient, since half the value is knowing an upline
backed you.
L8 Network Intelligence — every team ad pooled and anonymised: which angles,
headlines, creative and formats actually earn their impressions. No member
alone has enough traffic to learn anything from display; together they do.
It can't be bought, and it compounds monthly with no further work. Holds two
lines: nothing identifies anyone, and nothing under 2,000 impressions gets a
reported rate — under-evidenced rows are counted and disclosed rather than
silently dropped. The written readout is hand-authored, not generated:
these are conclusions about money, and a model paraphrasing a table is
exactly where an invented number slips in.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The QR on /p/<id> and /p/<id>/<slug> was drawn by an inline <script>, but the
site sends `script-src 'self'` with no 'unsafe-inline'. The browser silently
refused to run it, so the QR box rendered as an empty white square on every
member page, not just Funnel Factory ones.
Moved the bootstrap to /page-qr.js and pass the link via a data attribute, so
no page data is interpolated into executable script and the CSP stays as
strict as it is. Loosening script-src to fix this would have traded a
site-wide security property for one widget.
This matters more than it looks: these pages go on printed flyers and ad
destinations, where an unscannable QR is discovered by the person holding the
paper.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two bugs Marty spotted from a screenshot of his own wall.
1. The Traffic Desk rendered between L5 and L6 under a stray second
"L1 SCINTILLA" header. The wall emits a section header whenever the level
changes while walking the TOOLS array, and the Traffic Desk was still in
its original L5 array slot from before it moved to L1. Now the wall sorts
by level before rendering, so the array can be edited in any order and
this class of bug cannot come back.
2. Tiles above L4 still showed "UNLOCKS AT ..." despite suiteLevelOverride.
/api/public/suite-me carried its OWN copy of the org/allowlist logic
rather than calling suiteEntitlement, so the override reached every tool
page but not the wall linking to them. That duplication is the actual
defect — the route now calls the shared helper, and the override also
carries levelName so the header cannot disagree with the tiles.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Completes the ladder — no tier is a placeholder now.
Every tier below builds one thing at a time, which is right for someone
still finding their words. At the top the constraint is different: these are
people running organisations who don't have an afternoon to spend clicking.
So one pass produces five social posts across five different angles, three
outreach messages (first approach, follow-up, pyramid-scheme answer), an
email, and three text ads — all carrying their link, all in the member's own
voice profile if they have one.
Partial failures are reported rather than hidden: if the engine can't finish
a section the pack says which, instead of quietly handing over a short week.
API access is real, not a label: a personal key over
GET /me, GET /team, POST /generate. Keys are stored hashed and shown exactly
once, compared in constant time, and every call goes through the same meters
and compliance rules as the web tools.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Four new tools, so no tier is a placeholder any more:
L4 Voice Profile (/suite/voice) — five short answers that ride along with
every Copy Engine and Email Engine generation. It sits BEFORE the compliance
block in the prompt on purpose: a personal voice must never be able to talk
the model out of the honesty rules. suite-email builds its own prompt, so the
profile is threaded in there separately or email would keep sounding generic
while the Copy Engine sounded like the member.
L5 Split Tester (/suite/split) — 2-3 variants launched as one test with the
impressions split evenly, then click counters compared. Deliberately
conservative: it will not declare a winner until both arms have real volume
AND the leader is clearly ahead, because a 3-click gap on 400 impressions is
noise. A genuine tie is reported as a tie, which is useful information too.
A failed arm rolls back the whole test rather than leaving half of it running.
Apex is the right home for it — that is where impressions jump to 50,000.
L6 Funnel Factory (/suite/funnel) — extra named pages at /p/<id>/<slug>, so a
leader can run one page per audience and point different ads at each. Missing
slugs fall back to the member's main page, same no-dead-ends rule as /p/<id>.
L7 Leader Ops (/suite/leader) — the coaching radar already existed in chain.js
and only admin could see it, which was backwards: the leaders running those
legs need it more than anyone. Now scoped to the member's own organisation,
with a written plan built on contract-read facts only. Follows the
teach-forward rule — the digest gives the leader words to hand down, not just
numbers to act on.
Tile copy across the wall and the payout alerts now describes what actually
exists rather than what was sketched. suite-tools.js was stale in both
directions (it still had the Traffic Desk at L5 and L3 not live).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Text placements out-perform banners on this network — 357 text ads average
~171 clicks each against ~150 for banners, on far less inventory — so
members can now run them too.
The format is measured, not guessed. Across 60 live text ads: Subject caps
at 20 characters and Body is ALWAYS exactly three <br>-joined lines of at
most 24 characters. Every ad in the sample obeyed it.
Emoji: the NAS columns are latin1, but so is the connection, so UTF-8 bytes
pass through and render — which is how the existing emoji ads got there. The
bridge's clean() would have deleted every emoji via iconv //TRANSLIT//IGNORE,
so text copy now uses clean_ad_text(), which preserves them and strips angle
brackets instead. The bridge builds the <br> separators itself from a lines[]
array, so a member can never inject markup.
The engine writes plain text to a tight budget and we apply emoji ourselves:
models cannot count characters, least of all with emoji, so decoration is
arithmetic we control. It also lets the emoji rotate independently of the
copy. The palette carries no money emoji — the network is full of them, but
implying earnings outranks matching the neighbours.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Three fixes from live testing of the Traffic Desk:
- /p/<id> with no page built now 302s to /join/<id> instead of returning
raw JSON 404. Any /p/ link already on a banner, flyer, or in a DM must
always land somewhere useful.
- The personal-page ad destination is only offered (client) and only
accepted (server) once a page actually exists; otherwise the member is
pointed at the Page Builder.
- Members can stop a running banner and get the unserved impressions back
in their monthly balance. Counters are read before deactivation, since
deactivating zeroes `remaining` and would look fully served.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
martbost