Where things stand (5 November 2026)

A catch-up for Adarsh. The founder meeting planned for 28 October never happened, so nothing in FOUNDER-MEETING-PREP-2026-10-28.md was shown, decided or asked. The founder's email of 5 November answers some of it. This note says what's live, what's waiting, and which of the meeting's questions are still open. The new work (courses, professors, payments, pages) is in COURSES-PLAN-2026-11-05.md.

The one-minute version

The live site, thnkrr.com, runs the release of 25 October. It shows the waitlist only, and sign-up is closed. The private test copy, dev.thnkrr.com, runs everything since then, including the fixes from the 27 October test pass and the nine product calls of 28 October. None of that has reached the live site yet.

Three things are stuck, and none of them is code:

• GitHub's automatic tests haven't run since 27 October. Every run fails with "recent account payments have failed or your spending limit needs to be increased". The 28 October fixes went into dev/pilot without the tests running, so they need a test run before any release to the live site. Someone has to fix the card in GitHub's Billing & plans.
• The team screens (D-89) are still waiting for your check. These are the screens for adding schools, inviting staff and creating join links: server pull request #59 and website #39, both into dev/pilot since 27 October. Professor invites build on them, so they come first in the courses plan.
• The founder's to-do list from October is still open: moderators, the Child Safety Lead, the lawyer, the first school, and the support@ mailbox. See "Still open" below.

What's where

The unheld meeting: what the 5 November email answered

The meeting prep had 17 questions to decide, 10 calls to confirm, and a list of names and paperwork to ask for. The email answers these six questions:

• Professors (question 3). Yes, they get their own accounts. Thnkrr signs them, then they set themselves up. On whether professors can only reply to students who ask first: the plan keeps all contact inside the course, in spaces our team can see, with no private messages.
• Following a page (8). Yes, with a follower count. The count has to be switchable on and off until Obsinto (our compliance advisers) confirms it's fine on under-18 accounts.
• Schools posting to feeds (9). Yes. Posts go only to followers, newest first, with no ranking. Who at a school does the posting is still open; the plan suggests the page admins.
• What pages should have (10). Programs and courses come first.
• College pages (11). We run them, but they're built from the professors and mentors who join, not set up by hand. A committed college links to its page. The page lists that college's professors, their courses and its mentors.
• Mentor chat preconditions (12), partly. Background checks for mentors and professors happen on Thnkrr's side under their contracts, and we add a "verified" badge staff can switch on. The grooming check is still needed before mentor chat goes on in the live site.

The email also answers one of the "ask" items: we don't need to know which professors are coming.

Still open (carry these forward)

These still need the founder. Put them alongside the courses questions, so the founder gets one list rather than two.

Paths not built yet:

• What a student's account becomes after high school (1).
• Whether a student can become a mentor later (2).
• Teachers on a personal email (4).
• Mentors whose college isn't on our list (5). The college-pages work makes this one more pressing.
• Hiding someone from suggestions while they're under review (6).
• Catching someone who bullies now and then (7).

Turning things on for the pilot:

• How the first school's students get in (13).
• A person checks every photo and video before it shows (14).
• The longest allowed video (15).
• Deleting original video files after 30 days (16).
• Who can suspend and who can ban (17).

The 28 October calls, built and on dev, needing the founder's yes (18–27):

• Chats are never deleted. The lawyer and the Privacy Notice need this one.
• Warnings name the content.
• Appeals are tied to the decision.
• A held self-harm post comforts and never scolds.
• A student can block their mentor.
• Like works on one tap.
• The urgent list puts the most serious cases first.
• The Child Safety Lead sees care referrals.
• Teachers can see their own school's student profiles.
• A declined request keeps looking pending to the sender, and a student a mentor declined waits 30 days before asking again.

Names:

• Two moderators.
• The Child Safety Lead (is it Vidhi?) and their backup, and who files reports with NCMEC and the Indian police.
• The Grievance Officer for India.
• The Safety Admin.
• A counsellor for the reviewers.

Paperwork:

• Registering with NCMEC.
• The five abuse-image lists.
• The Thorn and Hive emails.
• The WebPurify quote.
• The lawyer's work: Terms, Privacy Notice and Community Guidelines, now including "chats are kept for good", plus the new course items in the courses plan.

The first school. The email says "our first school pilot runs on" courses, which is new. We still need:

• Which school, and when.
• How many students.
• The school agreement, with its named parent checker and care contact.

Small things only the founder controls:

• The support@ mailbox.
• GitHub billing.

Sources

• notes/FOUNDER-MEETING-PREP-2026-10-28.md (the unheld meeting's questions).
• notes/POST-PILOT-2026-10-29.md (cross-school visibility, deferred).
• notes/PRODUCTION-PLAN-2026-10-09.md §A1 (steps 31 onward).
• The founder's email of 5 November 2026.
• GitHub, checked 5 November 2026: open pull requests in both repos; the latest test runs and their failure message.
• Git, checked 5 November 2026: dev/pilot against main in both repos.