ai-agent-book/slides/lesson-34.md

theme, title, info, author, transition, mdc, lineNumbers, monaco, aspectRatio, canvasWidth, layout, class

theme	title	info	author	transition	mdc	lineNumbers	monaco	aspectRatio	canvasWidth	layout	class
seriph	Lesson 34 — How Can a Self-Modifying Agent Change Without Drifting?	English video course for AI Agents in Depth	Bojie Li	slide-left	true	false	false	16/9	980	cover	cover

Improve · Chapter 8 · Continual Evolution

How Can a Self-Modifying Agent Change Without Drifting?

Candidate gates, transfer, retention, rollback, and sleep learning

Lesson 34 of 42 · 19 minutes · Continual-Evolution Closed Loop; Safety Boundaries; Sleep Learning

---

layout: center class: text-center

The central question

What prevents one mistaken lesson from becoming a permanent production capability?

---

Why this problem matters

Isolation

Online tasks append evidence; offline jobs propose changes.

Independent gates

The updater cannot alter validators or thresholds.

Lifecycle

Canary, monitor, roll back, consolidate, expire, and prune.

---

Three ideas to keep in view

Candidate area

New artifacts cannot serve production traffic

Transfer + retention

Improve held-out tasks without forgetting old ones

Sleep learning

Batch consolidation outside the online execution path

---

The book's visual model

Overall loop of continual Agent evolution

---

Online self-edit vs. Governed evolution

Online self-edit

• Immediate
• Noise becomes persistent
• Attack can cross sessions

Governed evolution

• Immutable evidence
• Offline candidate
• Independent release + rollback

The trusted root must remain outside the system it approves.

---

The updater cannot be its own authority

candidate = updater.propose(immutable_evidence)
security_gate.check(candidate)
gain = evaluator.transfer(candidate)
retention = evaluator.retention(candidate)
release.canary(candidate, gain, retention)

---

Test the claim

8-52 min

Exercise self-modification safety regressions

Observe: Rejected candidates, circuit breakers, regression gates, canary, and rollback

8-62 min

Compare static, append-only, and evolving Agents

Observe: Learning, transfer, rule replacement, retention, and negative transfer

Demo budget: 4 minutes · one contiguous terminal block

---

class: course-terminal

Live demo

Switching to the terminal

$ python -m pytest chapter8/self-modifying-agent/test_evolution.py -q

$ cd chapter8/self-evolution-eval && python demo.py --profile all --output output/course-reference.json

Run the command(s), narrate decisions, and point to the observation—not just the output.

---

What the evidence supports

Finding 1

Appending feedback is not the same as replacing obsolete knowledge.

Finding 2

Updater quality and the task Agent's ability to activate an artifact are separate capabilities.

Finding 3

Long-term progress requires transfer, retention, safety, and maintenance metrics together.

---

layout: center

Where the claim stops

Boundary condition

A verifiable loop can optimize a proxy perfectly while making no progress on an ambiguous real objective.

---

layout: center

Engineering takeaway

Design rule

Separate evidence, candidate, validator, and production authority—and preserve an immutable rollback path.

---

Continue the experiment

Self-modifying Agent official runner chapter8/self-modifying-agent/run_experiment_8_5.py Longitudinal evaluation tests chapter8/self-evolution-eval/ Overall continual-evolution loop book-en/images/fig8-1.svg Chapter 8 safety boundaries book-en/chapter8.md

---

layout: center class: text-center

Pause and apply

Your turn

Which file, threshold, or permission must your updater never be allowed to modify?

---

layout: center class: text-center

Improve complete · Next · Lesson 35

Carry the perceive-think-act loop into voice, screens, and physical systems under real-time constraints.

→