Ladder-based progression

Mentorship-to-community ladder

Guided tracks, cohorts, office hours, and premium learning ladders can now connect into one clearer progression system instead of feeling like unrelated program ideas.

Carry momentum forward after a course or mentorship window ends so users do not drop back into passive browsing.

Back to community

Community-program truth

This community route is useful for participation discovery right now, but saved continuity still depends on public release

Use Mentorship-to-community ladder confidently for public participation discovery, while keeping auth continuity, premium workflow promises, and support follow-through honest until those live paths are fully verified.

Signed-in continuity is active enough to carry community flows into account and workspace surfaces.
Commercial billing is intentionally scheduled later during private beta, so missing Razorpay inputs should not be treated as a blocker here.
Support delivery is still not fully active, so community-route support expectations should stay conservative.

Support registry rows

11

In progress

4

Blocked

3

Support continuity

amitbhawani@gmail.com

Status

In progress

Participation rhythm

Cohort close -> office hours -> guided follow-up

Support bridges

3 handoff layers

Participation loop

1

Bring the learner from one guided program into a lower-friction community rhythm.

2

Use office hours, replay notes, and focused follow-up prompts instead of generic participation asks.

3

Keep the next recommended route visible after every guided touchpoint.

Support and moderation bridges

Connect community follow-up to the same support and success posture as mentorship.
Keep upgrade language secondary to progression and clarity.
Make it obvious when the ladder is still a guided preview rather than a live cohort engine.

Operating note

The community layer now has real public child routes instead of stopping at one overview page. The remaining work is live participation, moderation, and durable continuity, but the public route family now explains the intended participation loops and how they connect back into the rest of the product.