Portfolio defense field guide

One claim, one proof path

For each competency, link a problem, artifact, runnable command, result, failure evidence, and limitation. Prefer a fixed-test checksum and recompute command over a badge or proficiency percentage.

Case-study questions

• What production decision did the work support?
• Which constraints shaped the selection rule and architecture?
• What baseline and fixed test set made comparison fair?
• Where did the system fail, what is mitigated, and what remains uncertain?
• What is public, what is private, and how was sanitization verified?

Ninety-second defense

Open with the problem and constraint. Trace the hybrid signal path. Show one measured comparison, one failure card, the human-review boundary, and the exact reproduction route. Close with the honest claim and next experiment. Add captions and a transcript.

Release audit

Clone cleanly, follow the README, run tests/demo/recompute commands, inspect Git history and generated files for private residue, verify licenses/provenance, and open every evidence link. Optional external feedback may improve communication; it is not certification.