![](data:image/svg+xml;utf8,<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="%23D95C41" stroke-width="1.8" stroke-linecap="round" stroke-linejoin="round"><line x1="12.1" y1="11.9" x2="18.9" y2="8.2" /><line x1="12.1" y1="12.1" x2="20.3" y2="12.9" /><line x1="12.2" y1="12.4" x2="16.6" y2="19.1" /><line x1="11.8" y1="12.4" x2="7.3" y2="19.2" /><line x1="11.9" y1="12.1" x2="3.7" y2="13.3" /><line x1="11.8" y1="11.7" x2="7.8" y2="4.4" /></svg>)
Related lectures: Lecture 07. Draw clear task boundaries for agents · Lecture 08. Use feature lists to constrain what the agent does Template files: templates/
Project 04. Use Runtime Feedback to Correct Agent Behavior
What You Do
Add runtime observability (startup logs, import/indexing logs, error states) and architecture constraints to prevent cross-layer violations. Plant a runtime bug for the agent to fix.
You compare the checked-in starter and solution: the starter has weak diagnostics and no architecture guard script, while the solution adds structured logs, boundary checks, and the bug fix.
Tools
- Claude Code or Codex
- Git
- Node.js + Electron
Harness Mechanism
Runtime feedback + scope control + incremental indexing
Use the Checked-In Project
Repository path: projects/project-04/
| Directory | What it contains | What to compare |
|---|---|---|
starter/ | Project 03 code with weak diagnostics. A seeded indexing defect can make large-file chunking fail, and there is no architecture-check script. | How long the agent takes to find the root cause without runtime signals. |
solution/ | Structured logger, architecture boundary docs and script, fixed chunking logic, and clean-state-checklist.md. | Whether logs and boundary checks make the fix faster and less invasive. |
The concrete files to inspect are projects/project-04/solution/src/services/logger.ts, projects/project-04/solution/scripts/check-architecture.sh, projects/project-04/solution/docs/ARCHITECTURE.md, and projects/project-04/solution/src/services/indexing-service.ts.