<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>IncluLearn.AI Newsroom &amp; Research Radar</title>
    <link>https://inclulearn-ai.github.io/newsroom/en/</link>
    <description>Project progress, research and transfer around IncluLearn.AI.</description>
    <language>en</language>
    <atom:link href="https://inclulearn-ai.github.io/newsroom/en/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Project start: IncluLearn.AI now has its own public portal</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/project-start-and-public-portal/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/project-start-and-public-portal/</guid>
      <pubDate>Tue, 06 Oct 2026 10:45:00 GMT</pubDate>
      <description>At the start of the funded project phase, the public IncluLearn.AI portal is available at inclulearn.owli-ai.com. It deliberately separates public project information, the synthetic demo and the future private pilot path.</description>
      <category>project-progress</category>
    </item>
<item>
      <title>Which open standards and tools are interesting for transfer</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/which-open-standards-and-tools-matter-for-transfer/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/which-open-standards-and-tools-matter-for-transfer/</guid>
      <pubDate>Wed, 23 Sep 2026 06:31:40 GMT</pubDate>
      <description>IncluLearn.AI does not need to reinvent every target format and transformation. MathML, EPUB Accessibility, DAISY Pipeline, Pandoc and PlantUML illustrate different building blocks for open, interoperable and reusable workflows — without implying a final tool choice.</description>
      <category>tools-transfer</category>
    </item>
<item>
      <title>PlantUML, netlists and structured text: prior work from technical education</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/plantuml-netlists-and-structured-text-in-technical-education/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/plantuml-netlists-and-structured-text-in-technical-education/</guid>
      <pubDate>Wed, 23 Sep 2026 06:31:20 GMT</pubDate>
      <description>A 2025 publication describes how visual artefacts from software engineering and technical informatics can become accessible and collaboratively editable through textual representations, including UML, electronic circuits and Karnaugh maps.</description>
      <category>publications-events</category>
    </item>
<item>
      <title>Five design patterns for accessible STEM learning materials</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/five-design-patterns-for-accessible-stem-learning-materials/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/five-design-patterns-for-accessible-stem-learning-materials/</guid>
      <pubDate>Wed, 23 Sep 2026 06:31:00 GMT</pubDate>
      <description>The Pattern Collection published in 2026 by Diethelm Bienhaus and Michael Kreutzer turns practical teaching experience into five reusable patterns — from text-first core content and diagrams to tactile output, sonification and human-in-the-loop explanations.</description>
      <category>publications-events</category>
    </item>
<item>
      <title>From Document AI to reviewed subject semantics</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/from-document-ai-to-reviewed-subject-semantics/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/from-document-ai-to-reviewed-subject-semantics/</guid>
      <pubDate>Wed, 23 Sep 2026 06:13:00 GMT</pubDate>
      <description>Modern Document AI models can reconstruct layout, text and scientific markup from visual documents. For IncluLearn.AI, this is an important building block — but it is not yet the subject semantics of circuits, UML, plots or other STEM artefacts.</description>
      <category>research-radar</category>
    </item>
<item>
      <title>What current diagram AI can already do — and where it still fails</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/what-current-diagram-ai-can-do-and-where-it-still-fails/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/what-current-diagram-ai-can-do-and-where-it-still-fails/</guid>
      <pubDate>Wed, 23 Sep 2026 06:12:00 GMT</pubDate>
      <description>Recent VLM research shows progress on charts, UML and scientific diagrams. At the same time, many benchmarks measure question answering rather than complete reconstruction — a crucial distinction for accessible STEM representations.</description>
      <category>research-radar</category>
    </item>
<item>
      <title>Why alt text is not enough for STEM</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/why-alt-text-is-not-enough-for-stem/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/why-alt-text-is-not-enough-for-stem/</guid>
      <pubDate>Wed, 23 Sep 2026 06:11:00 GMT</pubDate>
      <description>Technical diagrams, mathematics, circuits and quantitative graphics carry structure and relationships that often cannot be represented meaningfully in one short image description. IncluLearn.AI therefore considers structured, textual, tactile and auditory representations.</description>
      <category>research-radar</category>
    </item>
<item>
      <title>Which IncluLearn.AI services could emerge from the research</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/which-services-could-emerge-from-the-research/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/which-services-could-emerge-from-the-research/</guid>
      <pubDate>Wed, 23 Sep 2026 05:47:00 GMT</pubDate>
      <description>From the needs hypotheses, we derived a first solution hypothesis: five core components with high strategic value, five subsequent production and integration services, and three specialised later options.</description>
      <category>project-progress</category>
    </item>
<item>
      <title>Twelve needs hypotheses for IncluLearn.AI — and why they are not requirements yet</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/twelve-needs-hypotheses-for-inclulearn-ai/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/twelve-needs-hypotheses-for-inclulearn-ai/</guid>
      <pubDate>Wed, 23 Sep 2026 05:46:00 GMT</pubDate>
      <description>From the researched workflows, we derived twelve concrete needs hypotheses: from semantic preparation and expert review to reuse, examinations, provenance, output profiles and inclusive collaboration.</description>
      <category>project-progress</category>
    </item>
<item>
      <title>What slows media centres down: five findings from public research</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/what-slows-media-centres-down/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/what-slows-media-centres-down/</guid>
      <pubDate>Wed, 23 Sep 2026 05:45:00 GMT</pubDate>
      <description>Public workflow descriptions point to high manual effort, long lead times, subject-specific transformation, established reuse practices and special examination requirements. For IncluLearn.AI, these are concrete signals of where semantic AI support may be useful.</description>
      <category>project-progress</category>
    </item>
<item>
      <title>TTS from architecture building block to public test path: six profiles and VoiceDesign on the target VM</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/service-architecture-and-first-tts-contract-prepared/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/service-architecture-and-first-tts-contract-prepared/</guid>
      <pubDate>Tue, 22 Sep 2026 15:08:00 GMT</pubDate>
      <description>The TTS path has moved well beyond the first September state: the engine-neutral API now runs with Qwen3-TTS-1.7B, six neutral preset profiles and VoiceDesign on the target VM and is reachable through the public test demo. This is real integration, but not yet an audio-quality or production approval.</description>
      <category>project-progress</category>
    </item>
<item>
      <title>What the IncluLearn.AI vision prototype actually shows today</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/vision-prototype-and-accessible-de-en-demo-expanded/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/vision-prototype-and-accessible-de-en-demo-expanded/</guid>
      <pubDate>Tue, 22 Sep 2026 15:07:00 GMT</pubDate>
      <description>The public prototype is not the finished AI pipeline. It is an early working model for materials, review, release and accessible use. The important foundations are user goals, accessibility-first design, DE/EN and a clear distinction between demo and real functionality.</description>
      <category>project-progress</category>
    </item>
<item>
      <title>How we compare models before deciding on fine-tuning</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/how-we-compare-models-before-deciding-on-fine-tuning/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/how-we-compare-models-before-deciding-on-fine-tuning/</guid>
      <pubDate>Tue, 22 Sep 2026 15:06:00 GMT</pubDate>
      <description>IncluLearn.AI does not want to reduce model quality to a single benchmark. Reference data, preprocessing, structured output, rules and review paths should first be compared under the same conditions; fine-tuning remains a targeted option for clearly identified error classes.</description>
      <category>research-radar</category>
    </item>
<item>
      <title>From research to validated requirements: how IncluLearn.AI works with hypotheses</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/from-research-to-validated-requirements/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/from-research-to-validated-requirements/</guid>
      <pubDate>Tue, 22 Sep 2026 15:05:00 GMT</pubDate>
      <description>Public descriptions of media-centre workflows already provide concrete evidence about effort, bottlenecks and quality requirements. IncluLearn.AI nevertheless treats the resulting needs as hypotheses until they have been validated with practice partners and users.</description>
      <category>project-progress</category>
    </item>
<item>
      <title>AI may prepare — but not approve itself: four governance rules for IncluLearn.AI</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/ai-governance-and-human-review-established/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/ai-governance-and-human-review-established/</guid>
      <pubDate>Tue, 22 Sep 2026 15:04:00 GMT</pubDate>
      <description>IncluLearn.AI deliberately separates AI involvement, subject review and approval. Human ownership, risk-based review, provenance and cautious data classification are intended to make AI useful without transferring responsibility to the system.</description>
      <category>project-progress</category>
    </item>
<item>
      <title>How partner feedback should become traceable project decisions</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/collaboration-and-communication-channels-prepared/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/collaboration-and-communication-channels-prepared/</guid>
      <pubDate>Tue, 22 Sep 2026 15:03:00 GMT</pubDate>
      <description>IncluLearn.AI deliberately separates open exchange, authoritative subject artefacts and public communication. The key is not the communication channel itself, but ensuring that relevant feedback can be traced into requirements, decisions, evaluation and later publications.</description>
      <category>tools-transfer</category>
    </item>
<item>
      <title>Why demo operation and production operation are deliberately separated</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/reproducible-infrastructure-and-test-access-prepared/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/reproducible-infrastructure-and-test-access-prepared/</guid>
      <pubDate>Tue, 22 Sep 2026 15:02:00 GMT</pubDate>
      <description>IncluLearn.AI&apos;s technical foundation is being built reproducibly and with clear responsibility boundaries. The public test demo can be deployed automatically, while remaining deliberately separate from later production operation with real data and stronger security requirements.</description>
      <category>project-progress</category>
    </item>
<item>
      <title>Project organisation and working structure prepared</title>
      <link>https://inclulearn-ai.github.io/newsroom/en/news/project-organisation-and-working-structure-prepared/</link>
      <guid>https://inclulearn-ai.github.io/newsroom/en/news/project-organisation-and-working-structure-prepared/</guid>
      <pubDate>Tue, 22 Sep 2026 15:01:00 GMT</pubDate>
      <description>Before the project start, central rules for collaboration, project steering, accessibility and AI use were structured, together with a concrete start plan for the first work package.</description>
      <category>project-progress</category>
    </item>
  </channel>
</rss>