Two hard-question objection cards from live member Q&A (catch-eligibility: level = reach; fixed counts vs quadrupling value) + chatbot + AI prompt synced

Both verified against contract source today (payout loop: level > levelIndex && 2 directs; one structural skip per depth).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

public/tools.html

@@ -451,6 +451,20 @@ Watch the short training, look at the live payment feed, then ask me anything.
     </div>
   </details>
 
+  <details class="obj"><summary>Does my upline need to OWN a level to catch payments at it?</summary>
+    <div class="obj-body">
+      <div class="obj-truth"><span class="lab">The truth</span><p>The contract checks the catcher against the level the buyer is <strong>leaving</strong>, not the one being bought. A qualified member still at Scintilla <strong>does</strong> catch their two matrix children's Ascensus purchases (the check is level ≥ 1, which everyone has) — owning Ascensus is not required for that first catch. The own-the-level rule bites one floor deeper: catching a Fabrica purchase from 2 generations down requires Ascensus, a Culmen catch from 3 down requires Fabrica, and so on — <em>your level is your reach</em>. Verified in the contract source: the payout loop requires <code>level &gt; levelIndex</code> plus 2 directs, and structurally skips one more upline per level of depth.</p></div>
+      <div class="obj-say"><div class="obj-say-head"><span class="lab">Say this</span><button class="btn btn-teal btn-sm copy-btn" data-copy="Good news — it's better than you think. To catch your two's FIRST upgrade, your sponsor only needs to be qualified with their two. They don't have to own that level yet, because the contract checks against the level the buyer is jumping FROM, and everyone starts there. Owning levels matters for reaching DEEPER: each level you buy extends your catch one generation further down. That's why the team says stay one level ahead of your deepest active layer — your level literally is your reach. All verifiable in the public contract: rmcircle.team/how-pay-works#exact-costs">Copy</button></div><pre class="swipe">Good news — it's better than you think. To catch your two's FIRST upgrade, your sponsor only needs to be qualified with their two. They don't have to own that level yet, because the contract checks against the level the buyer is jumping FROM, and everyone starts there. Owning levels matters for reaching DEEPER: each level you buy extends your catch one generation further down. That's why the team says stay one level ahead of your deepest active layer — your level literally is your reach. All verifiable in the public contract: rmcircle.team/how-pay-works#exact-costs</pre></div>
+    </div>
+  </details>
+
+  <details class="obj"><summary>"Each level only pays 2, then 4, then 8 people — isn't that small?"</summary>
+    <div class="obj-body">
+      <div class="obj-truth"><span class="lab">The truth</span><p>The count is right — one payment per person, at the one depth that matches their generation (2 at gen 1, 4 at gen 2, 8 at gen 3…). The scale comes from three compounding facts: (1) <strong>payment size doubles as width doubles</strong> — 2 catches of 621.40 is ~1,243, but 16 catches of 4,971.22 is ~79,540, so full-generation value quadruples per level; (2) <strong>generations keep filling</strong> — it's one payment per person but new people keep arriving via recruiting and spillover, and each one owes their depth's payment when they climb; (3) <strong>pass-ups</strong> from under-leveled members below add catches beyond the fixed counts. Never present the totals as expected income — they're the contract's mechanical maximum at full fill.</p></div>
+      <div class="obj-say"><div class="obj-say-head"><span class="lab">Say this</span><button class="btn btn-teal btn-sm copy-btn" data-copy="Your math is right — and that IS the design. One payment per person, at the depth that matches where they sit. Here's what makes it bigger than it sounds: each deeper generation is twice as wide AND pays twice as much per person, so the full-generation value quadruples every level you climb. And a generation isn't a fixed set of people — new members keep landing in your matrix from recruiting and spillover, and every one of them owes that depth's payment when they level up. Plus anything someone below you can't catch rolls up. Fixed counts, growing people, escalating checks. The exact table is at rmcircle.team/how-pay-works — mechanical maximums, not promises.">Copy</button></div><pre class="swipe">Your math is right — and that IS the design. One payment per person, at the depth that matches where they sit. Here's what makes it bigger than it sounds: each deeper generation is twice as wide AND pays twice as much per person, so the full-generation value quadruples every level you climb. And a generation isn't a fixed set of people — new members keep landing in your matrix from recruiting and spillover, and every one of them owes that depth's payment when they level up. Plus anything someone below you can't catch rolls up. Fixed counts, growing people, escalating checks. The exact table is at rmcircle.team/how-pay-works — mechanical maximums, not promises.</pre></div>
+    </div>
+  </details>
+
   <details class="obj"><summary>Why is the entry price different from the upgrade price? Is the income chart inflated?</summary>
     <div class="obj-body">
       <div class="obj-truth"><span class="lab">The truth</span><p>Entry and upgrade are <strong>two different purchases paid to two different people</strong>. Entry (360.58 POL at Premium level 1, sent as ~362 with buffer) creates a position and pays the <em>sponsor</em> 95% of the base, with a 5% admin charge on entries only. Upgrades (621.40 to reach level 2) travel <strong>100% up the matrix</strong> to a qualified member — zero admin fee. The upgrade ladder doubles exactly at every rung (2 × 621.40 = 1,242.80, to the penny), so two pass-ups at your level always equal your next climb. Income illustrations are built from the <em>upgrade</em> stream because that's the only money that travels up — entry money isn't in them at all. Exact numbers: <a href="/how-pay-works#exact-costs">the contract-exact table</a>, verifiable via getAllCosts() on Polygonscan.</p></div>