ECE 57000 — August 28, 2026
Using prohibited help—or sharing or receiving assessment content—will result in an F in the course under the syllabus policy.
The syllabus is required reading. Quiz questions may assess syllabus content.
AI and agents can scale your intelligence—but the results will reflect the quality of your judgments.
Goal: AI should optimize your thinking—not replace it.
Scaling reliable agentic software engineering
| Mode | Best suited to | Concrete examples |
|---|---|---|
| AI chat | Simple information gathering, explanation, summarization, and one-off synthesis | Claude chat; ChatGPT chat |
| AI agent | Inspecting artifacts, using tools, editing files, running checks, and pursuing a multi-step outcome | Claude Code; Codex |
Implementation capacity can grow faster than the judgment needed to direct it.
Paraphrase of Davis, MAGE, pp. 4, 18–23
Is there a third approach that preserves both leverage and reliability? What would it require?
Discussion framing by Inouye; engineering problem informed by Davis, MAGE, Part 1
Repeated reconstruction creates churn—even when each local change looks plausible.
Paraphrase of Davis, MAGE, pp. 28–45
MAGE = Model-Based Agentic Software Engineering, a method developed by James C. Davis for engineering large software systems with coding agents.
Model consequential knowledge → give obligations authority → convert recurring lessons into engineering capital
“A model is a purposeful reduction of a system. It preserves the information one engineering question needs and suppresses the detail that question does not.” — James C. Davis, MAGE, p. 38
Definition and Modeling Principle from Davis, MAGE, §2.1.1, p. 38 and Part 2
| Engineering question | Example model |
|---|---|
| How is the system divided and connected? | Architecture, component, or dependency model |
| What can happen, and in what order? | State machine, workflow, scenario, or use-case model |
| What must or must not happen? | Policy, invariant, permission, privacy, or security model |
| What counts as acceptable evidence? | Measurement, metric, threshold, or assurance model |
| Who owns a decision or artifact? | Ownership, decision, or provenance model |
| How do facts connect across the system? | System knowledge graph |
Examples adapted from Davis, MAGE, Part 2
Models can state what should hold, but representation alone does not make the work follow the model. Alignment gives selected obligations consequence.
| Mechanism | Role | Simple example |
|---|---|---|
| Constraint | Restrict action | A sandbox forbids a dangerous operation |
| Sensor | Produce evidence | A scan reports exposed endpoints |
| Validator | Judge evidence | A test checks required behavior |
| Gate | Control admission | CI blocks a release that fails checks |
Agents remain free within permitted bounds; work that violates a governed obligation does not pass.
Paraphrase of Davis’s Alignment Principle: Davis, MAGE, pp. 4–6 and Part 3
Paraphrase of Davis’s governance-conversion loop: Davis, MAGE, pp. 4–6 and Part 4
Model consequential knowledge → give obligations authority → delegate work → inspect evidence → convert recurring lessons
Summary of Davis, MAGE, “MAGE on One Page,” p. 6
Scale your intelligence beyond software engineering
AI and agents can scale your intelligence—but the results will reflect the quality of your judgments.
Offload work that does not require your attention so you can invest it where your judgment creates the most value.
To scale your intelligence, externalize the thinking that matters and engineer a system that can apply it reliably, test the results, and learn from corrections.
Instructor synthesis by Inouye; relationship inspired by Davis’s Modeling, Alignment, and governance-conversion loop in MAGE