A Richer Logging Experience Inspired by Jesse Genet and her agent Sylvie

Until recently, Charlotte’s logged record of a homeschool lesson was just a row in a spreadsheet. I logged lessons this way because it powered my own personal Homeschool Dashboard application. I used this system to track my family's homeschooling, follow progress, track time, and get a graphical overview of what was going on. I was doing this long before AI agents were all the vogue and when AI came along, it made sense for me to automate my workflows to match what I was doing at the time. Since this was how I logged lessons in my family homeschool, it was how I wanted Charlotte to do it. So when I built Charlotte, I had her log to my spreadsheets the same way I had always done.

This wans't entirely useless. My spreadsheet system was all I had before AI and I was always happy with it. It records the date, subject, start and end times, and a short description of what was covered. It helps me track hours and gives me a beautiful graphical view of what happened on a particular day and a broad overview of what's going on generally. When Charlotte started logging to my spreadsheets, she could read the lesson plan files directly and log a better description in my spreadsheets than I had often done on my own. I thought this was fantastic, and in a lot of ways it was. But this is a receipt for a lesson, not the lesson’s rich context. A spreadsheet row cannot hold the photographed workbook page, the words from a quick voice note, my child’s surprising observation, the handwriting that was difficult today, or the question that should come back next week. I had built a system that could account for our time and log a short description, but I was discarding much of the material that would help us understand the learning more completely.

When I saw what Jesse Genet was doing with her homeschool agent Sylvie, I realized that I could empower Charlotte with a much richer logging practice which would in turn allow her to do more things. I'm all about Charlotte doing more things, so I was all in!

The important decision was that the lesson log markdown file could be the primary artifact and since it's a text file, it could reasonably hold a lot more content than a row in a spreadsheet. A parent can send a short text or voice note, add photos, or record a screen lesson. The agent turns that loose evidence into a durable account: what was taught, how it went, and what might come next.

That distinction helped me see what Charlotte was missing. A curriculum tells us what was supposed to happen. A plan tells us what we intended to do. A time entry proves that we did something. Only the lesson log can preserve what the lesson became in the hands of a particular child on a particular day.

This is brilliant! Thank you Jesse and Sylvie!

The structure

In Charlotte, every teaching session now gets its own small directory. It contains:

• log.md, the readable account of what we did, how it went, and what comes next
• messages.md, preserving the parent’s original text and transcribed voice notes
• images.md, describing each photo or screenshot and extracting the visible text
• sources/, containing the original images and audio

Logs are organized in folders by date and contain date in the metadata. Original images, text messages, and audio files are preserved, but they're also synthesized into the log entry.

To be clear, Charlotte's new richer logging isn't the same as Jesse and Sylvie's. I did it my own way to serve my own family's needs, however, I think it's now a lot closer to what they're doing, and as I've already said, the inspiration came from them.

I still don't have to give up my spreadsheets!

The best part about this richer logging is that it doesn't need to replace my Homeschool Dashboard (HSD) spreadsheet logging. The spreadsheet logging continues as it always did, it's just not the primary source. So, instead of logging the input directly to spreadsheets, it's logged to our new and improved log, and the HSD spreadsheets are just generated from that. I still get my HSD dashboard and keep logging to spreadsheets, but I also get a richer better log along with it. This separation clarifies both systems. The lesson log can preserve content without being squeezed into cells. The spreadsheet can calculate time without pretending to be the full educational history. It also creates a more useful foundation for the rest of Charlotte. Questions about hours go to the spreadsheet. Questions about what was taught or how it went go to the lesson logs. Weekly MindFeast review slides are generated from a richer more ample base beginning with actual weak spots, discoveries, and memorable ideas from the week. More data logged = better slides for MindFeast!

This is fantastic because MindFeast is built in part on the idea that repeated encounters shape what children remember. A full and more complete lesson log helps us create more valuable MindFeast slides! Something that was confusing can return as a review question. A beautiful image or surprising fact can reappear on the tablet. New slides come directly from our family’s richer learning history.

AI gives us loaves of bread instead of crumbs

The appeal of AI here isn't that it should manage the child or make every educational decision, it's that it can do something useful with the crumbs a parent can realistically provide (and those crumbs become loaves of bread with AI): a sentence, a photo, a screenshot, a voice note. It can organize those fragments, preserve the sources, and return something useful.

I am still testing all of this. Charlotte remains a technical system built around the way our family works, not a finished template that will work for every family, however, I want her to be maximally useful and am working to make her repurposable and useful for any family that wants a homeschool AI agent. If you're technical and would like give Charlotte a try, let me know how it goes.