Independent software · Thomas HolbirdAn evolving project

From information
to understanding.

A personal platform for learning, research, and putting ideas to work.

well.education connects study tools, source-linked reporting, and AI orchestration in one workspace. A project built through the work of using it, questioning it, and making it better.

Explore the project
learn01
research02
connect03
build04
A connected way of thinking.
Conceived, built, and continually refined.Read the engineering story 01 / Introduction

Good tools make room
for better thinking.

The interesting part starts after you have the information.

You still have to make sense of it. Find the connection. Practice the difficult part. Decide what deserves your attention and turn a decision into work you can follow.

Originally called Brain, this project began as a way to coordinate AI agents across software projects. It has grown into a personal environment for studying, reading, researching, and building, with shared infrastructure underneath.

well.education is its public identity: a place to see the system, understand its design, and follow the thinking behind the work.

One platform.

Learning systems / Research workflows / Knowledge connections / Agent orchestration

Built around the
way work actually happens.

Different tools. A common thread:
make the work easier to understand.

Learning systems

Practice with
a reason to return.

Course guides, question banks, and review tools bring the material and the work of learning it into the same place. Learn mode gives immediate feedback; saved attempts make it possible to revisit where understanding broke down.

Implemented across LSAT preparation, Spanish, and university coursework, with concept-level review and authored study materials.

Explore the learning system
Learning workspaceIllustrative workflow
Reasoning & retention

Understanding takes practice.

01Read the materialGuides, concepts, and worked examples↗
02Put it to the testPractice with immediate feedback↗
03Return to the gapReview attempts and revisit concepts↺
A learning loop, with the history attached.

Many tools.
One considered system.

The interface is only the visible part. Behind it are task queues, persistent state, model runtimes, and a clear separation between public work and private activity.

01 / EXPERIENCE

A shared workspace

Study · research · knowledge · projects

02 / COORDINATION

A persistent control plane

FastAPI · SQLite · task state · event streams

03 / EXECUTION

Workers & model runtimes

Project-aware execution, local inference,
and service integrations.

04 / RECORD

Work that leaves a trail

Attempts, notes, evidence, task outcomes,
and published artifacts.

The details
are the work.

A project like this is an exercise in connecting systems and taking responsibility for what happens between them.

Read the project case study
01

Full-stack product development

Python services, a custom web interface, persistent data, and native app surfaces, developed together around actual workflows.

02

AI systems integration

Agent execution, local model runtimes, streaming responses, and tool access connected to the surrounding application.

03

Evidence and evaluation

Source attribution, saved learning attempts, and inspectable run histories make the output something you can return to and question.

04

Operation beyond the prototype

Deployments, authentication, worker boundaries, and regression checks are part of the product’s design and ongoing maintenance.

Built by curiosity.
Refined by use.

Thomas HolbirdCreator · well.education

This is a working project and an ongoing education in building systems.

The work spans product design, application development, AI integration, and deployment. It is developed with AI-assisted engineering, with the choices about what to build, how it should behave, and what deserves another iteration remaining central to the project.

The platform connects private tools with public projects such as News Unfiltered. The case study follows the implementation in detail, from the learning experience to the worker architecture and the decisions that hold them together.

Read about the development approach
The next question is the beginning.

Stay well.educated.

Explore the work. Follow the reasoning.
Start a conversation about what comes next.

Discuss the project