Skip to content
AH HA Solutions
  • Home
  • LuminousPath
  • The Path
  • Newsletter
  • Consulting
  • Case Studies
  • About
  • Contact

LuminousPath Monthly · July 2026

Foundation & Security

Roles, access, and the architecture behind the platform.

LuminousPath July Year One cover: Foundation and Security. A lit path enters the gate of a layered stone fortress, with a faint trail climbing the mountain beyond.

The Foundation

Next.js, Supabase, secure authentication, and role-based access.

Access by Design

Protected student accounts, private password setup, and controlled platform entry.

July was not about adding features to the LuminousPath prototype. It was about replacing the prototype with a foundation strong enough to hold real students.

The original Alpha did its job. It showed what an AI tutor built for neurodivergent college students could look and sound like. It gave us a place to test the idea.

The Beta needs something different. It needs secure accounts, separate user roles, protected student information, and a structure built to grow. July was about laying that foundation.

From Prototype to Platform

The Alpha ran as one large web page backed by a small server.

The Beta runs on Next.js, TypeScript, and Supabase, with a real database behind it. Students, intake workers, and enterprise administrators each get their own experience, scoped to their role.

This matters because LuminousPath will hold personal information: how a student learns, what overwhelms them, what helps them recover. That kind of data needs security built into the architecture from day one, not added later.

Building Student Access Around Security

July introduced a new account process for students.

Staff no longer create or hand out temporary student passwords. The platform creates the account, keeps it inactive until intake is complete, then sends the student a private link. The student sets their own password from there.

Students don't get into the tutoring platform before intake is done. Staff access follows its own rules, and disabling a staff account never touches the student records tied to their past work.

How a student account opens

  1. Platform creates the account
  2. Account stays inactive during intake
  3. Student receives a private link
  4. Student sets their own password

This is a security-first foundation. There's more to build before Beta testing opens.

Personalization, Restored

July also brought back several access and comfort features: color themes, tutor voice, spoken responses, colorblind-friendly displays, and a plain-text mode without emoji or decorative symbols.

These exist for one reason. Students shouldn't have to adapt themselves to the platform. The platform should adapt to them.

Students shouldn't have to adapt themselves to the platform. The platform should adapt to them.

What's Ahead

The foundation is taking shape, but the Beta isn't finished. Next up: designing the intake experience, then building the tutoring session itself, then the living profile that learns from every session after that.

We're building in order. Secure access before student use. Intake before personalized tutoring. Personalized tutoring before long-term adaptation. Skipping steps gets you a faster demo and a weaker platform.

LuminousPath This Fall

We're joining two national conversations about neurodiversity, education, and technology this fall.

  • October We're attending the NeuroTech Frontiers Summit.
  • November We're presenting LuminousPath at the 2026 College Autism Summit. Our poster introduces the platform, the student need behind it, and the research questions guiding where it goes next.

August Focus: Designing the Intake

August is about the doorway students will walk through to enter LuminousPath: the intake experience.

Intake at LuminousPath will happen in two stages. First, an intake worker opens a record from the student's support request. Then the intake worker and student sit down together for a guided conversation, one question at a time, about how the student approaches learning.

The conversation is meant to feel like a conversation, not an intake form.

From those answers, the platform will build a first-draft teaching profile.

August is where we work out that design, before any student sits down for it. That means deciding which questions belong in the conversation, how each one earns its place in the teaching profile, how the platform handles conflicting answers, and where a human still needs to step in.

The goal isn't to label a student. It's to understand how they learn before the first tutoring session begins.

July built the foundation. August starts shaping the door.

See all issues · Return to the path

AH HA Solutions

© 2026 AH HA Solutions LLC. All rights reserved. LuminousPath™ is a trademark of AH HA Solutions LLC.

  • AH HA Solutions
  • Contact