Terry asked how a new referral of his would be set up as 'Direct with
spillover', and Marty asked whether a leader's choice should carry down to
their team. This writes up the answer for the three of them to agree on
before anything is built.
Three states — Team first, Direct, Follow my sponsor — with a new member
starting on whatever their sponsor uses, so a team duplicates its leader
by default without anyone being locked in.
The rule that needed pinning down: inherit from the SPONSOR, never the
matrix parent. Under spillover those are frequently different people, and
the setting should follow whoever recruited and teaches them rather than
whoever they happened to land beneath.
Also names the pitfalls rather than leaving them to be discovered — chiefly
that inherited Direct is a doctrine change, not just a setting, since it
reverses the team-first play for everyone below a leader who picks it.
Nothing built. Three open questions at the end need Marty's call.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
qa/live-visitor.mjs is read-only against production: a visitor on any ID-keyed
shared link must see no modal, no invitation, no 401 and no page errors. It is the
check that the optional-profile change did not disturb anyone who is not signed in.
Passing 9/9 against rmcircle.team.
docs/for-manson-optional-profiles.md is the note to send him before anything goes
to the team, since he asked to see it first. It leads with his objection being
right, states plainly that nothing is required, and is honest about the trade: we
accept lower coverage rather than mandate identity. It also covers the level-8
question, where the pay rules were already fine and only the ladder graphic was
misleading.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
martbost