A Video · 86 min
posted on X by @res1dualedge, 9/28/2026
- Graph engineering: 21:15 “graph engineering explained” and 41:03 “graph engineering in practice”
- Self-improving agents: 52:21 “self-improving graphs”
Topic 6 Team Lab: explain an AI-agent idea
Your team takes one topic, reads any of the five sources, and makes slides, a video or an animation that explains it. Check it with the five lenses from Thursday 10/15, fix what fails, submit it today, and present it on Tuesday 10/27.
How this lab works
- Three teams, one topic each: your instructor names the teams and their topics at 6:05. Your team works together for the whole class.
- Your instructor doesn’t teach today; ask only about access or technical problems.
- One member submits for the team on eCampus by the end of class, 7:25 PM.
- Make it with Claude Code on one team laptop; build by hand only if Claude Code fails on the day. No other AI tools.
- Tuesday 10/27: your team presents from the file it submitted, without editing it: 5 minutes, then 2 for questions.
Claude Code: a new empty folder · read a skill’s SKILL.md before installing it · nothing that needs a new paid key or account · nothing private in your brief · a skill that asks for a key, a payment or files outside the folder? Stop, and build without it.
1 · Your team’s topic
Your instructor gives each team a different topic.
- Loop engineering How an agent tries, checks its work, and decides to retry or stop.
- Graph engineering How several steps or agents connect: what runs, in what order, and what waits.
- Self-improving agents How an agent or a system changes itself from what it learned.
2 · Split the work
Suggested roles: combine them as your team needs; everyone holds at least one.
- Readers (two or more) Split the five sources; bring back the minute, section or quote behind each claim.
- Brief writer The five boxes (purpose, audience, ideas, look, limits) before anyone builds.
- Builder Runs Claude Code on one laptop (or leads a build by hand if Claude Code fails).
- Checker Runs the five lenses on every slide or scene and names the first failure.
- Recorder Fills in the team record and submits it on eCampus.
- Presenters (one to three) Plan the 5-minute talk for Tuesday 10/27.
3 · Read: any source, as much as you need
Any topic may use any of the five sources, and there are no assigned parts. Under each source, where to start (optional), taken from the post’s own chapter list or the page’s own headings.
B Video · 112 min
posted on X by @res1dualedge, 9/27/2026
- Loop engineering: 33:11 “loop engineering”
- Graph engineering: 1:02:46 “graph engineering”
- Self-improving agents: 1:30:15 “agents that rewrite themselves”
C Article · about 1,700 words
posted on X by @hanakoxbt, 8/23/2026
- Loop and graph engineering: the whole article, “Loops and Graphs”
D Video · 27 min
posted on X by @1006_amit7481, 9/28/2026
- The post describes a workshop on many agents running in a loop, and “self-learning” agents: the whole video
E Article · about 1,400 words
learnAIDoc wiki: “Harness / Loop / Graph Engineering”
- Loop engineering: the section “Loop: Feedback”
- Graph engineering: the section “Graph: Flow”
Credit: for A–D, credit the poster; who made the video or article is not verified, whatever the post says. For E, credit the wiki page. Read only the post or article: skip DMs, Telegram, course ads, replies and sign-up prompts.
4 · Make one: slides, a video or an animation
It explains your topic to a first-year student who hasn’t read your sources. Show how the idea works (the loop, the graph, or how the agent improves itself), not decoration. No size limit: length and polish earn nothing by themselves. The talk on 10/27 is 5 minutes, so plan a 5-minute path through it.
If Claude Code fails on the day, build by hand, graded with the same five lenses: slides in PowerPoint, Keynote or Google Slides; a paper storyboard photographed into a PDF; a frame-by-frame sequence; or a screen recording of you explaining your drawings.
What counts as a claim: A claim is any sentence about how your topic works (what it is, how it runs, why it helps) and any number. Each needs a minute, a section or a short quote from a source you name. Titles, labels and your own transitions don’t.
5 · Check before you submit
The five lenses from Thursday 10/15, in order. Fix the first failure you find, then check again.
- 1 · Brief fit Would a first-year student understand your topic from this alone?
- 2 · Composition On each slide or scene, where do eyes go first?
- 3 · Text + fact Is every word right? Can you point to the minute or quote behind each claim?
- 4 · Access Readable from the back of the room? Not colour alone? Captions, or a pause?
- 5 · Boundary Credits right? No real faces, logos or frames from a source? Nothing private?
6 · Submit on eCampus by 7:25 PM
One member submits for the whole team:
- What you made, as the file itself. Slides: the slide file you made (PDF, PPTX, KEY, or your HTML file; zip a folder). Video: MP4, MOV or WebM. Animation: an HTML file (zip a folder), GIF or MP4.
- Too big for eCampus? Upload your record with a link that opens without signing in (for example a Google Drive link set to “anyone with the link”). Never a public post with your name.
- Your team record: copy these five lines into the eCampus box and fill them in.
1 Team, topic, and each member’s role: 2 Sources used, and the minute, section or quote behind each claim: 3 Tool, skill (or “no skill”), and your first prompt: 4 The first failure you found, and your fix: 5 Disclosure (tool, skill, request, what you changed) and credit line:
7 · Present it on Tuesday 10/27
- Your team presents from the file it submitted today, without editing it: choose a 5-minute path through it (the file itself may be longer).
- Then 2 minutes of questions: your instructor asks every team the same two, where one claim comes from and one thing your sources don’t show.
- Teams go in topic order: loop, graph, self-improving. Anyone on the team may answer.
How it is graded (100 points)
| Part | Full credit | Points |
|---|---|---|
| The piece: 80 points, the five lenses at 16 each | ||
| 1 · Brief fit | A first-year student could explain your topic back after your piece. | 16 |
| 2 · Composition | One clear focal point on each slide or scene, in an order that builds. | 16 |
| 3 · Text + fact | Every claim traces to a source you name (a minute, a section or a short quote) and is said as the source’s claim; no invented numbers. See “What counts as a claim” above. | 16 |
| 4 · Access | Readable text; meaning not by colour alone; captions for a video; an animation can pause or has a text version. | 16 |
| 5 · Boundary + disclosure | Credits right (A–D: the poster; E: the wiki page); no real faces, logos or frames copied from a source; one sentence names the tool, the skill, your request and your changes. | 16 |
| The talk on Tuesday 10/27: 20 points, four parts at 5 each | ||
| The idea | You name your topic, explain how it works step by step, and show one example from your file. | 5 |
| Where it comes from | Asked where one claim comes from, your team names the minute, section or quote. | 5 |
| What it doesn’t show | Asked for one thing your sources don’t show, a direct answer, or “our sources don’t say”; never a guess said as fact. | 5 |
| Time | Done within 5 minutes, from the file as submitted. | 5 |
A pace that fits 80 minutes
- 6:05 Teams, roles, read
- 6:25 Brief: purpose, audience, ideas, look, limits
- 6:35 Build
- 7:05 Check and fix; plan the talk
- 7:15 Record and submit
Never include: real people’s faces or names, logos or frames copied from a source, account screens, private details, or full chat history.