Step 1
Observe
Adult feedback, everyday interactions, and initial assessments establish the starting point.
Packing the adventure bag
Finding the next trail…
Loading Summer School…
Packing the adventure bag
Loading Summer School…
⚙ Behind the adventure
This is a learning project in two ways: the kids practice new skills, while the adults keep improving how lessons are planned, delivered, recorded, and supported by technology.
Current operating mode
Human-led, manually updated, and intentionally simple
The non-technical view
ChatGPT helps turn adult judgment and real-world feedback into a useful next draft. It does not teach the lesson or make the final decisions—the adult remains in the loop from beginning to end.
Step 1
Adult feedback, everyday interactions, and initial assessments establish the starting point.
Step 2
Kevin guides a ChatGPT conversation to shape the four-week curriculum and the next age-appropriate lesson.
Step 3
The plan becomes a printed worksheet for math or a physical whiteboard layout for reading.
Step 4
The lesson happens in person, with room to slow down, repeat, or follow a useful surprise.
Step 5
Post-lesson observations inform the next plan, while approved records are maintained in Notion.
The final step feeds the first: what happened in today’s lesson becomes context for tomorrow’s plan.
Two practical lesson recipes
Each format is short enough to stay focused and flexible enough to respond to what happens in the room.
Math trail
Reading trail
The application stack today
Notion credentials and lesson details stay on the server. ChatGPT is used manually for planning today; the web application does not send lesson data to an AI service.
Source control
The application code and its history live in a private GitHub repository.
Application
App Router server components render public pages and protected family field guides. Tailwind CSS supports the visual system.
Learning records
Approved lesson and progress records are entered manually. The website connection is server-only and read-only today.
Build + hosting
Google builds the production container and Cloud Run serves it at libuit.org. Releases are triggered manually today.
Today · manual and working
Future · ideas, not integrations yet