<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Aalore Lab Notebook</title>
    <link>https://aalore.com/lab</link>
    <description>Ideas, system maps, and field notes on education, curriculum, and technology from Aalore — The Education Lab.</description>
    <language>en</language>
    <lastBuildDate>Mon, 14 Sep 2026 09:00:15 GMT</lastBuildDate>
    <atom:link href="https://aalore.com/feed.xml" rel="self" type="application/rss+xml"/>
    
    <item>
      <title>A chapter is a system, not a file.</title>
      <link>https://aalore.com/lab/a-chapter-is-a-system</link>
      <guid isPermaLink="true">https://aalore.com/lab/a-chapter-is-a-system</guid>
      <pubDate>Sun, 13 Sep 2026 00:00:00 GMT</pubDate>
      <description>What changes when learning outcomes become the connective tissue between formats?</description>
      <category>SYSTEM MAP</category>
      <author>Aalore Lab</author>
      <content:encoded><![CDATA[<h3>Start with meaning</h3><p>A chapter holds concepts, examples, explanations and questions. A page layout is one expression of that material. If the layout becomes the only source of truth, every new format starts with extraction and repair.</p><h3>Keep the relationships</h3><p>Give each learning outcome a stable identity. Connect examples, misconceptions and assessments to it. Then a worksheet and an animation can refer to the same concept without copying the entire chapter.</p><h3>Design for change</h3><p>When an explanation changes, the system should tell an editor which resources depend on it. This does not eliminate review. It makes the right review easier to find.</p><h3>A practical first step</h3><p>Choose one chapter. List its outcomes, examples and questions before designing a new format. The relationships you record are the beginning of a reusable content model.</p>]]></content:encoded>
    </item>
    <item>
      <title>Automation needs an editorial checkpoint.</title>
      <link>https://aalore.com/lab/the-editorial-checkpoint</link>
      <guid isPermaLink="true">https://aalore.com/lab/the-editorial-checkpoint</guid>
      <pubDate>Sun, 13 Sep 2026 00:00:00 GMT</pubDate>
      <description>The most useful part of an automated workflow may be where it stops.</description>
      <category>LAB NOTE</category>
      <author>Aalore Lab</author>
      <content:encoded><![CDATA[<h3>Define what good means</h3><p>A production system needs explicit acceptance criteria. For a teaching resource, these might include curriculum fit, age-appropriate language, accurate explanations and answerable questions.</p><h3>Separate checks from judgement</h3><p>Software can check missing fields, inconsistent references and structural requirements. An editor or teacher decides whether an explanation is clear, a question is fair, or an activity is feasible.</p><h3>Make review visible</h3><p>A resource should carry its review state and version. Generated, reviewed and ready to release are different states. Treating them as different makes accountability part of the workflow.</p><h3>Improve the system</h3><p>Repeated corrections are useful evidence. Feed them into the brief, template or validation rules. The goal is not merely faster production, but less avoidable rework.</p>]]></content:encoded>
    </item>
    <item>
      <title>Build for the classroom you have.</title>
      <link>https://aalore.com/lab/the-classroom-you-have</link>
      <guid isPermaLink="true">https://aalore.com/lab/the-classroom-you-have</guid>
      <pubDate>Sun, 13 Sep 2026 00:00:00 GMT</pubDate>
      <description>Language, devices and teacher time belong in the first brief.</description>
      <category>FIELD NOTE</category>
      <author>Aalore Lab</author>
      <content:encoded><![CDATA[<h3>Context is a design input</h3><p>A useful classroom product begins with the board, language, available devices and time a teacher has. These are design constraints to understand early, not details to solve after the product is finished.</p><h3>Let formats cooperate</h3><p>A printed activity may work better for discussion. An animation may make a process easier to see. Digital delivery should support those choices and keep the learning sequence coherent.</p><h3>Design a fallback</h3><p>Consider what happens when the network fails, audio is unavailable or a shared display is difficult to read. A printable explanation or a clear static frame can preserve the lesson.</p><h3>Close the loop</h3><p>Ask teachers what they skipped, changed or explained again. These observations help improve both the content and the system that produces it.</p>]]></content:encoded>
    </item>
  </channel>
</rss>