Faculty Defense and Artifact Lineage
Subtitle: Make the line from notebooks → model → reflection inspectable — that is the credential.
Opening provocation¶
Faculty are not scoring vibes. They trace lineage: which notebook produced which rule, which reflection caught which blind spot, which revision followed.
1. Defense arc (15 minutes)¶
5 min — Model: ontology, two scenarios, one non-obvious insight.
10 min — Challenge: Porter (differentiation), Taleb (tails), behavioral (bias), MCP (scope/ethics).
Bring one slide or page max; the artifact should speak.
2. Lineage package¶
Assemble for submission:
Notebook index — ordered paths and what each contributes.
SAMWISE — eight prompts engaged (can be excerpts).
Change log — three revisions with why.
3. What “done” looks like¶
Simulation runs with documented assumptions.
At least three scenarios (baseline / optimized / stress) from integration work.
MCP or documented substitute per lecture 7.
Honest about what you refused to optimize.
Bridge to the notebook¶
08_defense_prep.ipynb holds a checklist and space for your one-page influence report final text — export-ready.
Lecture checklist¶
Lineage narrative: reviewer can replay your build without guessing.
Top three faculty objections anticipated with responses grounded in the model.
Explicit statement of ethical limits on persuasion and automation.