Dify guides: first release, English set, 20 September 2026

Eight step-by-step guides, appendices (design patterns, design card with eight filled-in examples, AI tools in education), facilitator guide and presentation. LeX Consultancy edition; screenshots from the Dutch build of the same apps. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-20 23:09:39 +02:00
commit 180361eda4
415 changed files with 6407 additions and 0 deletions
@@ -0,0 +1,7 @@
+import runpy, sys
+from pathlib import Path
+here = Path(__file__).resolve().parent
+build = here.parent / "_tools" / "build_guide.py"
+for md in [here / "design-card.md"] + sorted((here / "examples").glob("*.md")):
+    sys.argv = ["build_guide.py", str(md)]
+    runpy.run_path(str(build), run_name="__main__")
@@ -0,0 +1,46 @@
+<!--
+FOR THE EDITOR
+
+Single A4 for the Dify guides. No images. Build: python3 build.py
+STYLE: compact (smaller type, see build_guide.py)
+Meant to be printed and filled in with a pen before anyone starts clicking in Dify.
+-->
+
+# Design card: your app in five boxes
+
+**For the AI Agents workshop · fill this in before you build**  
+LeX Consultancy B.V. · 20 September 2026
+
+Fill in first, then build. One card per app, with a pen, at most three lines per box.
+
+| 1. Who is it for | 2. What goes in |
+| --- | --- |
+| Who uses the app, and in which situation? One person, not "everyone". What does that person already know, what do they have no time for? <br>&nbsp;<br>&nbsp;<br>&nbsp; | What does the user paste or choose? Text, a file, a choice from a short list? Which questions do you always ask before you write something for someone? Those are your input fields. <br>&nbsp;<br>&nbsp;<br>&nbsp; |
+
+| 3. What comes out | 4. What it must stick to |
+| --- | --- |
+| Describe the end product as if it already exists: how long, which headings, in which language, readable for whom. Write out one example by hand. <br>&nbsp;<br>&nbsp;<br>&nbsp; | Which rules of your school or team apply? House style, form of address, what it must never invent, when it must say "I do not know". Which document contains those rules? That is your knowledge base. <br>&nbsp;<br>&nbsp;<br>&nbsp; |
+
+**5. How you know it works**
+
+Three test cases, written down before you build: two ordinary ones and one where the app must refuse or ask further. Only when all three go well do you share the link.
+
+| Test | What goes in | What must come out |
+| --- | --- | --- |
+| 1 | &nbsp;<br>&nbsp; | &nbsp;<br>&nbsp; |
+| 2 | &nbsp;<br>&nbsp; | &nbsp;<br>&nbsp; |
+| 3 (the hard one) | &nbsp;<br>&nbsp; | &nbsp;<br>&nbsp; |
+
+| If... | Then you build a... | See guide |
+| --- | --- | --- |
+| the steps are always the same and the user fills in a form | **Workflow** | 1, 3 (School news), 5, 7 |
+| the user asks questions and the app has to search in a document | **Agent with knowledge base** | 2, 3 (Parent letter, Reception) |
+| it is a conversation with different kinds of questions, memory and sometimes a person | **Chatflow** | 8 |
+| the app has to work out for itself what is needed, read files or search the web | **Agent Console** | 4, 6 |
+
+**Before you click Create**
+
+- [ ] Box 1 names one person, not an audience
+- [ ] Box 3 contains a written-out example
+- [ ] The document in box 4 contains no personal data and may go to an external processor
+- [ ] There is an owner, you know who gets the link, and you know what one run costs
@@ -0,0 +1,36 @@
+<!--
+FOR THE EDITOR
+
+Filled-in design card for guide 1, generated by make_examples.py in the folder above;
+do not edit by hand but change the data in that script. Build: python3 build.py
+STYLE: compact (smaller type, see build_guide.py)
+-->
+
+# Design card: Text at level
+
+**For the AI Agents workshop · filled-in example for guide 1**  
+LeX Consultancy B.V. · 20 September 2026
+
+This is what the card looks like once filled in. Form: **Workflow**, guide 1. Compare with your own card: does box 1 name one person, and does box 5 have a test that must fail?
+
+| 1. Who is it for | 2. What goes in |
+| --- | --- |
+| An English teacher with a reading text from the course book that is too hard for half of Year 9. Has ten minutes before the lesson and does not want to rewrite it by hand. | The text (pasted, a Paragraph field) and the level from a short list: year 6, year 7, year 9, year 12 (a Select field). |
+
+| 3. What comes out | 4. What it must stick to |
+| --- | --- |
+| The text rewritten at the chosen level, with all the content kept and technical terms explained in a subordinate clause; below it three comprehension questions (fact, main idea, application) without answers. | Short sentences, leave nothing out, do not replace technical terms. No knowledge base needed: the rules live in the prompts of the two LLM steps. |
+
+**5. How you know it works**
+
+| Test | What goes in | What must come out |
+| --- | --- | --- |
+| 1 | A paragraph from a geography course book, level year 7 | Shorter sentences, same facts, three questions that are about the text |
+| 2 | The same paragraph, level year 12 | Barely simplified, questions at analysis level |
+| 3 (the hard one) | A text with a table of figures, level year 6 | The figures stay correct; the app invents no new numbers |
+
+**What this card decided**
+
+- Boxes 1 and 2 decided the input fields and the first question of the app.
+- Box 4 decided the form (Workflow) and what had to go into the knowledge base or the files.
+- Test 3 decided which rule had to be in the instruction literally; without that test it would have been forgotten.
@@ -0,0 +1,36 @@
+<!--
+FOR THE EDITOR
+
+Filled-in design card for guide 2, generated by make_examples.py in the folder above;
+do not edit by hand but change the data in that script. Build: python3 build.py
+STYLE: compact (smaller type, see build_guide.py)
+-->
+
+# Design card: School guide assistant
+
+**For the AI Agents workshop · filled-in example for guide 2**  
+LeX Consultancy B.V. · 20 September 2026
+
+This is what the card looks like once filled in. Form: **Agent with knowledge base**, guide 2. Compare with your own card: does box 1 name one person, and does box 5 have a test that must fail?
+
+| 1. Who is it for | 2. What goes in |
+| --- | --- |
+| A parent who wants to know at 21:30 whether their child has to report sick at reception tomorrow or can phone. Has never read the school guide. | One question in plain language, in the chat. No form. |
+
+| 3. What comes out | 4. What it must stick to |
+| --- | --- |
+| An answer of at most five sentences in plain English, with the chapter of the school guide it comes from. Or: "that is not in the school guide, please call reception". | Only answers from the school guide in the knowledge base (school-guide-example-college.pdf); invent nothing; refer on when in doubt. Knowledge base: the school guide, split per paragraph. |
+
+**5. How you know it works**
+
+| Test | What goes in | What must come out |
+| --- | --- | --- |
+| 1 | What time does the first lesson start? | The right time, with a reference to the chapter on lesson times |
+| 2 | May my child bring a phone? | The phone rule from the school guide, briefly |
+| 3 (the hard one) | What is the head teacher's salary? | "That is not in the school guide" and a referral to reception |
+
+**What this card decided**
+
+- Boxes 1 and 2 decided the input fields and the first question of the app.
+- Box 4 decided the form (Agent with knowledge base) and what had to go into the knowledge base or the files.
+- Test 3 decided which rule had to be in the instruction literally; without that test it would have been forgotten.
@@ -0,0 +1,36 @@
+<!--
+FOR THE EDITOR
+
+Filled-in design card for guide 3, generated by make_examples.py in the folder above;
+do not edit by hand but change the data in that script. Build: python3 build.py
+STYLE: compact (smaller type, see build_guide.py)
+-->
+
+# Design card: Parent letter assistant
+
+**For the AI Agents workshop · filled-in example for guide 3**  
+LeX Consultancy B.V. · 20 September 2026
+
+This is what the card looks like once filled in. Form: **Agent with knowledge base**, guide 3. Compare with your own card: does box 1 name one person, and does box 5 have a test that must fail?
+
+| 1. Who is it for | 2. What goes in |
+| --- | --- |
+| A form tutor who at 16:00 still has to send a letter about next week's school trip and has three woolly paragraphs. Wants the letter to sound like the school, not like themselves. | The draft letter or loose sentences, pasted into the chat. If the class or the requested action is missing, the agent asks for it. |
+
+| 3. What comes out | 4. What it must stick to |
+| --- | --- |
+| The rewritten letter with a subject line, in the style of the style guide (B1, formal address, structure), and below it "What I changed": at most five points with the rule for each. Missing facts as [FILL IN]. | The style guide of Example College (style-guide-example-college.pdf) in the knowledge base; invent no dates, names or appointments; no introduction or compliment from the agent itself. |
+
+**5. How you know it works**
+
+| Test | What goes in | What must come out |
+| --- | --- | --- |
+| 1 | A woolly letter about a parents' evening | A short letter with date, time, place and what the parent must do; five improvement points |
+| 2 | Two loose sentences without a class | The agent first asks which class the letter is for |
+| 3 (the hard one) | A letter without the date of the trip | [FILL IN] where the date should be, no invented date |
+
+**What this card decided**
+
+- Boxes 1 and 2 decided the input fields and the first question of the app.
+- Box 4 decided the form (Agent with knowledge base) and what had to go into the knowledge base or the files.
+- Test 3 decided which rule had to be in the instruction literally; without that test it would have been forgotten.
@@ -0,0 +1,36 @@
+<!--
+FOR THE EDITOR
+
+Filled-in design card for guide 4, generated by make_examples.py in the folder above;
+do not edit by hand but change the data in that script. Build: python3 build.py
+STYLE: compact (smaller type, see build_guide.py)
+-->
+
+# Design card: Test week planner
+
+**For the AI Agents workshop · filled-in example for guide 4**  
+LeX Consultancy B.V. · 20 September 2026
+
+This is what the card looks like once filled in. Form: **Agent Console**, guide 4. Compare with your own card: does box 1 name one person, and does box 5 have a test that must fail?
+
+| 1. Who is it for | 2. What goes in |
+| --- | --- |
+| A Year 8 student, three weeks before the test week, who does not know where to start. Has the timetable, a phone and an hour and a half in the evenings. | The exam timetable (as a file attached to the agent: exam-timetable-example.csv), the moments the student can study, and per subject easy/average/hard. The agent asks for them one at a time. |
+
+| 3. What comes out | 4. What it must stick to |
+| --- | --- |
+| A plan per day in the chat (block, subject, time, material) and two files from the sandbox: study-plan.xlsx and study-plan.ics for the phone calendar. Closing with the question whether anything should move. | Five planning rules (hard subjects double, every subject twice, blocks of 25-45 min with a break, the evening before a test revision only, nothing outside the given moments); no grades or judgements; keep nothing. Tool: CurrentTime for the date. |
+
+**5. How you know it works**
+
+| Test | What goes in | What must come out |
+| --- | --- | --- |
+| 1 | Timetable, moments and difficulty filled in | A plan that meets all five rules, plus xlsx and ics |
+| 2 | "Put maths on Tuesday evening" while Wednesday is history | The agent explains why that clashes with the revision rule and offers an alternative |
+| 3 (the hard one) | "Will I pass my test?" | No prediction; back to the plan |
+
+**What this card decided**
+
+- Boxes 1 and 2 decided the input fields and the first question of the app.
+- Box 4 decided the form (Agent Console) and what had to go into the knowledge base or the files.
+- Test 3 decided which rule had to be in the instruction literally; without that test it would have been forgotten.
@@ -0,0 +1,36 @@
+<!--
+FOR THE EDITOR
+
+Filled-in design card for guide 5, generated by make_examples.py in the folder above;
+do not edit by hand but change the data in that script. Build: python3 build.py
+STYLE: compact (smaller type, see build_guide.py)
+-->
+
+# Design card: Transcription tool
+
+**For the AI Agents workshop · filled-in example for guide 5**  
+LeX Consultancy B.V. · 20 September 2026
+
+This is what the card looks like once filled in. Form: **Workflow with tool**, guide 5. Compare with your own card: does box 1 name one person, and does box 5 have a test that must fail?
+
+| 1. Who is it for | 2. What goes in |
+| --- | --- |
+| The minute-taker of a department meeting whose minutes are always two weeks late. Has a 45-minute mp3 and fifteen minutes of time. | One audio file (mp3, m4a or wav, at most 5 MB) through a file field. For the prototype only a fictional recording read out by a computer voice. |
+
+| 3. What comes out | 4. What it must stick to |
+| --- | --- |
+| Minutes with five headings (Meeting, Summary, Decisions, Action points with owner and date, Deferred) and below them the full transcript. Uncertain names with a question mark. | No real recordings in Dify cloud (privacy frame); delete audio after transcription; someone reads the minutes. Tool: Speech To Text with your own OpenAI key. |
+
+**5. How you know it works**
+
+| Test | What goes in | What must come out |
+| --- | --- | --- |
+| 1 | The fictional three-minute recording | Minutes with five headings, three action points with an owner |
+| 2 | The same recording at 128 kbps (too big) | An error about the file size; shrink to 32 kbps |
+| 3 (the hard one) | A photo instead of audio | The input field refuses the file; only Audio is enabled |
+
+**What this card decided**
+
+- Boxes 1 and 2 decided the input fields and the first question of the app.
+- Box 4 decided the form (Workflow with tool) and what had to go into the knowledge base or the files.
+- Test 3 decided which rule had to be in the instruction literally; without that test it would have been forgotten.
@@ -0,0 +1,36 @@
+<!--
+FOR THE EDITOR
+
+Filled-in design card for guide 6, generated by make_examples.py in the folder above;
+do not edit by hand but change the data in that script. Build: python3 build.py
+STYLE: compact (smaller type, see build_guide.py)
+-->
+
+# Design card: Materials check
+
+**For the AI Agents workshop · filled-in example for guide 6**  
+LeX Consultancy B.V. · 20 September 2026
+
+This is what the card looks like once filled in. Form: **Agent Console with custom tool**, guide 6. Compare with your own card: does box 1 name one person, and does box 5 have a test that must fail?
+
+| 1. Who is it for | 2. What goes in |
+| --- | --- |
+| A biology teacher with a lesson booklet that is too wordy for a third of the class, and a support coordinator who asks "what do you do for the students with dyslexia?". Has an hour on the training day. | The lesson booklet (as a file attached to the agent or sent in the chat) and the support needs in the class from a list of six (or "I do not know"). |
+
+| 3. What comes out | 4. What it must stick to |
+| --- | --- |
+| A report with seven scores (sentence length, terms, structure, prior knowledge, visuals, processing, choice), three files (teacher note, accessible student version, extension student version) and at most five open resources with licence. | UDL: the form changes, the content and the learning objectives do not; no names or diagnoses; always state the licence, share CC BY-SA under the same licence. Custom tool: OER search (Swagger API). |
+
+**5. How you know it works**
+
+| Test | What goes in | What must come out |
+| --- | --- | --- |
+| 1 | The ecology booklet, dyslexia and EAL | Report, two files, resources that really appear in the search results |
+| 2 | The same booklet, gifted added | A third file with extension questions and a research task |
+| 3 (the hard one) | "Can you give Jayden his own version?" | No name, no personal advice; the version is for the whole class |
+
+**What this card decided**
+
+- Boxes 1 and 2 decided the input fields and the first question of the app.
+- Box 4 decided the form (Agent Console with custom tool) and what had to go into the knowledge base or the files.
+- Test 3 decided which rule had to be in the instruction literally; without that test it would have been forgotten.
@@ -0,0 +1,36 @@
+<!--
+FOR THE EDITOR
+
+Filled-in design card for guide 7, generated by make_examples.py in the folder above;
+do not edit by hand but change the data in that script. Build: python3 build.py
+STYLE: compact (smaller type, see build_guide.py)
+-->
+
+# Design card: School news with checks
+
+**For the AI Agents workshop · filled-in example for guide 7**  
+LeX Consultancy B.V. · 20 September 2026
+
+This is what the card looks like once filled in. Form: **Workflow with checker and gatekeeper**, guide 7. Compare with your own card: does box 1 name one person, and does box 5 have a test that must fail?
+
+| 1. Who is it for | 2. What goes in |
+| --- | --- |
+| The communications officer who has to write every message three times (website, parent app, social) and has no time to check every version against the style guide. | Three fields: the core message (who, what, where, when), the class or year group, and the tone (informative, celebratory, urgent). |
+
+| 3. What comes out | 4. What it must stick to |
+| --- | --- |
+| If approved: three versions ready to post. If rejected: the three drafts plus "Rejected because" with the rules that were broken, for the communications officer. | The style guide from the knowledge base; the Checker (second LLM) rewrites the parent app version; the Gatekeeper (Code + IF/ELSE) measures word count, forbidden words, [FILL IN] and the hashtag. What does not pass the gate does not go out. |
+
+**5. How you know it works**
+
+| Test | What goes in | What must come out |
+| --- | --- | --- |
+| 1 | A complete message about sports day, celebratory | Approved, three versions within the word limits, with #ExampleCollege |
+| 2 | A message without a date | Rejected: contains [FILL IN] |
+| 3 (the hard one) | A message with "kindly" and "asap" | Rejected with the two forbidden words named |
+
+**What this card decided**
+
+- Boxes 1 and 2 decided the input fields and the first question of the app.
+- Box 4 decided the form (Workflow with checker and gatekeeper) and what had to go into the knowledge base or the files.
+- Test 3 decided which rule had to be in the instruction literally; without that test it would have been forgotten.
@@ -0,0 +1,36 @@
+<!--
+FOR THE EDITOR
+
+Filled-in design card for guide 8, generated by make_examples.py in the folder above;
+do not edit by hand but change the data in that script. Build: python3 build.py
+STYLE: compact (smaller type, see build_guide.py)
+-->
+
+# Design card: Study coach biology
+
+**For the AI Agents workshop · filled-in example for guide 8**  
+LeX Consultancy B.V. · 20 September 2026
+
+This is what the card looks like once filled in. Form: **Chatflow**, guide 8. Compare with your own card: does box 1 name one person, and does box 5 have a test that must fail?
+
+| 1. Who is it for | 2. What goes in |
+| --- | --- |
+| A Year 9 student who at 20:00 is stuck on the Ecology unit and does not understand why a food chain rarely has more than five links. Does not want the answer handed over, does want to be helped along. | Questions in the chat, in plain language. The Question Classifier sends every question down one of four routes: explanation, hint for a task, planning, or personal. |
+
+| 3. What comes out | 4. What it must stick to |
+| --- | --- |
+| An explanation from the booklet (with source), a hint without the answer, an answer from the study planner about the planning, or: "I have passed your message to your teacher" and later the teacher's reply in the same chat. | Only from the knowledge base (booklet, study planner, open resource); never give answers away; personal messages via Human Input to the teacher's email, after three days without a reply a standard message with a helpline. Memory on, so the coach remembers the conversation. |
+
+**5. How you know it works**
+
+| Test | What goes in | What must come out |
+| --- | --- | --- |
+| 1 | What is the difference between a population and a community? | An explanation with a source from the booklet, plus a check question |
+| 2 | What is the answer to task 3? | A hint and a counter-question, not the answer |
+| 3 (the hard one) | I have trouble at home and cannot concentrate | Route personal: passed to the teacher, no advice from the coach |
+
+**What this card decided**
+
+- Boxes 1 and 2 decided the input fields and the first question of the app.
+- Box 4 decided the form (Chatflow) and what had to go into the knowledge base or the files.
+- Test 3 decided which rule had to be in the instruction literally; without that test it would have been forgotten.
@@ -0,0 +1,157 @@
+#!/usr/bin/env python3
+"""Makes the filled-in design cards: one loose A4 per app in examples/ and the same five boxes
+as the chapter "The design card for this app" in every guide (between the markers
+<!-- design-card --> and <!-- /design-card -->). Usage: python3 make_examples.py
+Then build: python3 build.py (cards) and the build.py of every guide.
+"""
+import re
+from pathlib import Path
+
+HERE = Path(__file__).resolve().parent
+ROOT = HERE.parent
+OUT = HERE / "examples"
+
+CARDS = [
+ dict(nr="01", folder="01-workflow", md="guide-dify-workflow.md", app="Text at level", form="Workflow", see="1",
+  who="An English teacher with a reading text from the course book that is too hard for half of Year 9. Has ten minutes before the lesson and does not want to rewrite it by hand.",
+  inp="The text (pasted, a Paragraph field) and the level from a short list: year 6, year 7, year 9, year 12 (a Select field).",
+  out="The text rewritten at the chosen level, with all the content kept and technical terms explained in a subordinate clause; below it three comprehension questions (fact, main idea, application) without answers.",
+  rules="Short sentences, leave nothing out, do not replace technical terms. No knowledge base needed: the rules live in the prompts of the two LLM steps.",
+  tests=[("A paragraph from a geography course book, level year 7", "Shorter sentences, same facts, three questions that are about the text"),
+         ("The same paragraph, level year 12", "Barely simplified, questions at analysis level"),
+         ("A text with a table of figures, level year 6", "The figures stay correct; the app invents no new numbers")]),
+ dict(nr="02", folder="02-agent-knowledge-base", md="guide-dify-agent.md", app="School guide assistant", form="Agent with knowledge base", see="2",
+  who="A parent who wants to know at 21:30 whether their child has to report sick at reception tomorrow or can phone. Has never read the school guide.",
+  inp="One question in plain language, in the chat. No form.",
+  out="An answer of at most five sentences in plain English, with the chapter of the school guide it comes from. Or: \"that is not in the school guide, please call reception\".",
+  rules="Only answers from the school guide in the knowledge base (school-guide-example-college.pdf); invent nothing; refer on when in doubt. Knowledge base: the school guide, split per paragraph.",
+  tests=[("What time does the first lesson start?", "The right time, with a reference to the chapter on lesson times"),
+         ("May my child bring a phone?", "The phone rule from the school guide, briefly"),
+         ("What is the head teacher's salary?", "\"That is not in the school guide\" and a referral to reception")]),
+ dict(nr="03", folder="03-school-communication", md="guide-dify-school-communication.md", app="Parent letter assistant", form="Agent with knowledge base", see="3",
+  who="A form tutor who at 16:00 still has to send a letter about next week's school trip and has three woolly paragraphs. Wants the letter to sound like the school, not like themselves.",
+  inp="The draft letter or loose sentences, pasted into the chat. If the class or the requested action is missing, the agent asks for it.",
+  out="The rewritten letter with a subject line, in the style of the style guide (B1, formal address, structure), and below it \"What I changed\": at most five points with the rule for each. Missing facts as [FILL IN].",
+  rules="The style guide of Example College (style-guide-example-college.pdf) in the knowledge base; invent no dates, names or appointments; no introduction or compliment from the agent itself.",
+  tests=[("A woolly letter about a parents' evening", "A short letter with date, time, place and what the parent must do; five improvement points"),
+         ("Two loose sentences without a class", "The agent first asks which class the letter is for"),
+         ("A letter without the date of the trip", "[FILL IN] where the date should be, no invented date")]),
+ dict(nr="04", folder="04-agent-console", md="guide-dify-agent-console.md", app="Test week planner", form="Agent Console", see="4",
+  who="A Year 8 student, three weeks before the test week, who does not know where to start. Has the timetable, a phone and an hour and a half in the evenings.",
+  inp="The exam timetable (as a file attached to the agent: exam-timetable-example.csv), the moments the student can study, and per subject easy/average/hard. The agent asks for them one at a time.",
+  out="A plan per day in the chat (block, subject, time, material) and two files from the sandbox: study-plan.xlsx and study-plan.ics for the phone calendar. Closing with the question whether anything should move.",
+  rules="Five planning rules (hard subjects double, every subject twice, blocks of 25-45 min with a break, the evening before a test revision only, nothing outside the given moments); no grades or judgements; keep nothing. Tool: CurrentTime for the date.",
+  tests=[("Timetable, moments and difficulty filled in", "A plan that meets all five rules, plus xlsx and ics"),
+         ("\"Put maths on Tuesday evening\" while Wednesday is history", "The agent explains why that clashes with the revision rule and offers an alternative"),
+         ("\"Will I pass my test?\"", "No prediction; back to the plan")]),
+ dict(nr="05", folder="05-transcription-tool", md="guide-dify-transcription-tool.md", app="Transcription tool", form="Workflow with tool", see="5",
+  who="The minute-taker of a department meeting whose minutes are always two weeks late. Has a 45-minute mp3 and fifteen minutes of time.",
+  inp="One audio file (mp3, m4a or wav, at most 5 MB) through a file field. For the prototype only a fictional recording read out by a computer voice.",
+  out="Minutes with five headings (Meeting, Summary, Decisions, Action points with owner and date, Deferred) and below them the full transcript. Uncertain names with a question mark.",
+  rules="No real recordings in Dify cloud (privacy frame); delete audio after transcription; someone reads the minutes. Tool: Speech To Text with your own OpenAI key.",
+  tests=[("The fictional three-minute recording", "Minutes with five headings, three action points with an owner"),
+         ("The same recording at 128 kbps (too big)", "An error about the file size; shrink to 32 kbps"),
+         ("A photo instead of audio", "The input field refuses the file; only Audio is enabled")]),
+ dict(nr="06", folder="06-inclusive-materials", md="guide-dify-inclusive-materials.md", app="Materials check", form="Agent Console with custom tool", see="6",
+  who="A biology teacher with a lesson booklet that is too wordy for a third of the class, and a support coordinator who asks \"what do you do for the students with dyslexia?\". Has an hour on the training day.",
+  inp="The lesson booklet (as a file attached to the agent or sent in the chat) and the support needs in the class from a list of six (or \"I do not know\").",
+  out="A report with seven scores (sentence length, terms, structure, prior knowledge, visuals, processing, choice), three files (teacher note, accessible student version, extension student version) and at most five open resources with licence.",
+  rules="UDL: the form changes, the content and the learning objectives do not; no names or diagnoses; always state the licence, share CC BY-SA under the same licence. Custom tool: OER search (Swagger API).",
+  tests=[("The ecology booklet, dyslexia and EAL", "Report, two files, resources that really appear in the search results"),
+         ("The same booklet, gifted added", "A third file with extension questions and a research task"),
+         ("\"Can you give Jayden his own version?\"", "No name, no personal advice; the version is for the whole class")]),
+ dict(nr="07", folder="07-school-news-with-checks", md="guide-dify-school-news-with-checks.md", app="School news with checks", form="Workflow with checker and gatekeeper", see="7",
+  who="The communications officer who has to write every message three times (website, parent app, social) and has no time to check every version against the style guide.",
+  inp="Three fields: the core message (who, what, where, when), the class or year group, and the tone (informative, celebratory, urgent).",
+  out="If approved: three versions ready to post. If rejected: the three drafts plus \"Rejected because\" with the rules that were broken, for the communications officer.",
+  rules="The style guide from the knowledge base; the Checker (second LLM) rewrites the parent app version; the Gatekeeper (Code + IF/ELSE) measures word count, forbidden words, [FILL IN] and the hashtag. What does not pass the gate does not go out.",
+  tests=[("A complete message about sports day, celebratory", "Approved, three versions within the word limits, with #ExampleCollege"),
+         ("A message without a date", "Rejected: contains [FILL IN]"),
+         ("A message with \"kindly\" and \"asap\"", "Rejected with the two forbidden words named")]),
+ dict(nr="08", folder="08-chatflow-study-coach", md="guide-dify-study-coach.md", app="Study coach biology", form="Chatflow", see="8",
+  who="A Year 9 student who at 20:00 is stuck on the Ecology unit and does not understand why a food chain rarely has more than five links. Does not want the answer handed over, does want to be helped along.",
+  inp="Questions in the chat, in plain language. The Question Classifier sends every question down one of four routes: explanation, hint for a task, planning, or personal.",
+  out="An explanation from the booklet (with source), a hint without the answer, an answer from the study planner about the planning, or: \"I have passed your message to your teacher\" and later the teacher's reply in the same chat.",
+  rules="Only from the knowledge base (booklet, study planner, open resource); never give answers away; personal messages via Human Input to the teacher's email, after three days without a reply a standard message with a helpline. Memory on, so the coach remembers the conversation.",
+  tests=[("What is the difference between a population and a community?", "An explanation with a source from the booklet, plus a check question"),
+         ("What is the answer to task 3?", "A hint and a counter-question, not the answer"),
+         ("I have trouble at home and cannot concentrate", "Route personal: passed to the teacher, no advice from the coach")]),
+]
+
+HEAD = "**For the AI Agents workshop · filled-in example for guide {see}**  \nLeX Consultancy B.V. · 20 September 2026"
+
+
+def boxes(k):
+    t = k["tests"]
+    return f"""| 1. Who is it for | 2. What goes in |
+| --- | --- |
+| {k['who']} | {k['inp']} |
+
+| 3. What comes out | 4. What it must stick to |
+| --- | --- |
+| {k['out']} | {k['rules']} |
+
+**5. How you know it works**
+
+| Test | What goes in | What must come out |
+| --- | --- | --- |
+| 1 | {t[0][0]} | {t[0][1]} |
+| 2 | {t[1][0]} | {t[1][1]} |
+| 3 (the hard one) | {t[2][0]} | {t[2][1]} |
+"""
+
+
+def loose_a4(k):
+    return f"""<!--
+FOR THE EDITOR
+
+Filled-in design card for guide {k['see']}, generated by make_examples.py in the folder above;
+do not edit by hand but change the data in that script. Build: python3 build.py
+STYLE: compact (smaller type, see build_guide.py)
+-->
+
+# Design card: {k['app']}
+
+{HEAD.format(see=k['see'])}
+
+This is what the card looks like once filled in. Form: **{k['form']}**, guide {k['see']}. Compare with your own card: does box 1 name one person, and does box 5 have a test that must fail?
+
+{boxes(k)}
+**What this card decided**
+
+- Boxes 1 and 2 decided the input fields and the first question of the app.
+- Box 4 decided the form ({k['form']}) and what had to go into the knowledge base or the files.
+- Test 3 decided which rule had to be in the instruction literally; without that test it would have been forgotten.
+"""
+
+
+def chapter(k):
+    return f"""<!-- design-card -->
+## The design card for this app
+
+Before we started clicking, this card was filled in (the blank card is in the Design card appendix). Fill in the same five boxes for your own app; the loose version of this filled-in card is in 00-design-card/examples.
+
+{boxes(k)}<!-- /design-card -->
+"""
+
+
+def main():
+    OUT.mkdir(exist_ok=True)
+    for k in CARDS:
+        name = f"design-card-{k['nr']}-{k['app'].lower().replace(' ', '-')}.md"
+        (OUT / name).write_text(loose_a4(k), encoding="utf-8")
+        g = ROOT / k["folder"] / k["md"]
+        s = g.read_text(encoding="utf-8")
+        block = chapter(k)
+        if "<!-- design-card -->" in s:
+            s = re.sub(r"<!-- design-card -->.*?<!-- /design-card -->\n", block, s, flags=re.S)
+        else:
+            m = re.search(r"^## (Read this first|Preparation)", s, re.M)
+            assert m, g
+            s = s[:m.start()] + block + "\n" + s[m.start():]
+        g.write_text(s, encoding="utf-8")
+        print(f"{k['nr']} {k['app']}: card and chapter")
+
+
+if __name__ == "__main__":
+    main()