What the platform tracks about itself.

What we report aggregate

When PLAUSIBLE_DOMAIN is set, the site fires aggregate events (no IPs, no cookies):

• search_openSearch palette opened (Cmd-K, /, or trigger button).
• search_navigateResult picked from search — surfaces which nodes are findable vs. discoverable.
• tutor_openTutor FAB opened — node-scoped, so we see which nodes prompt questions.
• tutor_askQuestion submitted to the tutor (length only — not the question text).
• playbook_sharedUser generated a share-link for their playbook.
• playbook_printedUser printed the playbook.
• playbook_emailedUser exported the playbook as a self-addressed email.
• playbook_csvUser downloaded the playbook as CSV.

What we don't track

• The text of your tutor questions or your playbook notes.
• Your IP address or any device fingerprint.
• Per-user reading progress on the server. Visited-node markers and the “continue” card are stored only in your browser's localStorage and never leave the device.
• Any third-party analytics beyond Vercel Analytics (which is cookieless).

Topics flagged as contested

• G4 · contested
  AI and labor

  The honest answer: nobody knows. The dishonest answers come from anyone with a confident number. Track G holds the disagreement up to the light instead of resolving it.

• G5 · contested
  Digital money: CBDCs, stablecoins, the rest

  The technical debate is small. The political debate — who can program your money, who can see your transactions, who can confiscate them — is enormous and largely under-discussed.

• H9 · contested
  Crypto in a real portfolio

  Two honest readings of bitcoin coexist: a tail-risk asset (no cashflow, regulation-killable, 80%-drawdown-prone) and a reserve-asset candidate (fixed supply, network effects, dollar-debasement hedge). Sizing differs by an order of magnitude. The right allocation depends on which reading you believe — and what happens to the portfolio if you're wrong.