Red Work Atelier is shifting into a working studio for instructional design, educator-facing AI support, reusable teaching assets, and practical creative-technology experiments.
The old student-facing repository is being retired. The game-oriented pockets stay, but the center of gravity is now educator-to-educator: toolkits, field notes, updates, and artifacts that help learning systems survive contact with actual humans.
Red Work Atelier resources sold through TeacherStore.io will point back here for version notes, bonus materials, corrections, and extra files that do not fit neatly inside a marketplace listing.
The store is the checkout counter. This site is the bench: context, support, updates, and the larger body of work.
Reusable frameworks, checklists, templates, course structures, and design notes for educators and instructional teams.
Guides, workflows, and explainers for educators trying to use AI thoughtfully without becoming prompt-goblin influencers.
A home base for people who buy my educational resources elsewhere and need updates, bonus files, fixes, or companion materials.
The game-oriented work is not gone. It is being reframed as a design laboratory for interaction, motivation, simulation, and learning.
Faculty developers, instructional coaches, curriculum leads, teacher trainers, and the quietly exhausted people translating change into practice.
This site will collect the evidence: built assets, documented processes, design decisions, revisions, and finished pieces that can stand on their own.
In old-school alchemy, rubedo (literally “redness”) was the final stage of the Great Work. Not the “this is a cool idea” stage. Not the “look at this prototype” stage. The actually finished stage. Red meant the experiment survived the chaos and came out whole. Gold, philosopher’s stone, success: whatever metaphor you like. The point was, you didn’t just start something interesting. You finished it.
Which, frankly, remains aspirational around here.
That’s what The Red Work is trying to be. A deliberate push against my extremely well-documented tendency to start seventeen fascinating projects and then wander off because a new idea looked at me funny. Rubedo is the refusal to stop at clever drafts. It’s the grind of integration: tightening systems until they behave, sharpening language until it means one thing, testing in public until reality has its say, and turning a pile of promising parts into something that doesn’t need an apology attached.
For this next version of the site, that means fewer vague intentions and more finished artifacts: usable resources, documented design decisions, AI workflows educators can actually try, and portfolio pieces that show the work instead of merely describing it.
There’s a psychological angle too, if you enjoy that flavor of navel-gazing. Jungian thinkers used alchemy as a metaphor for becoming more whole: less scattered, fewer internal tabs open at once. In that frame, rubedo is the moment the pieces stop fighting and start cooperating. It’s often symbolized as blood-red because it’s not cosmetic. You can’t un-learn it. You can’t pretend it didn’t happen. And you definitely can’t ship around it.
Translation: we don’t worship prototypes. We finish the parts that matter.
(Or at least… that’s the plan.)