Season 5 · Weeks 17–19 · 3 weeks
Season 5: Shield.
The villain arrives: a normal-looking email that gives FRIDAY orders. Learn how attacks work, lock FRIDAY in a box, ship to real people.
The villain arrives: a perfectly normal-looking email that gives FRIDAY orders. Learn how prompt injection works and break the lethal trifecta, lock FRIDAY in containers and a sandbox with attack tests in CI, then ship it properly to five real friends and act on what they say (Project 5).
How you learn
Write the attacks yourself, then containers, a sandbox and a CI/CD pipeline you understand line by line.
What you build
FRIDAY defended against a scripted attacker, running in containers, and used by five real friends.
The weeks
- Week 17The letter that gave orders
You can explain prompt injection, break the lethal trifecta, read the OWASP lists for AI apps, and shrink a fooled assistant's blast radius with least privilege.
- Week 18A box with no doors
You can pack an app and its database into containers, run code a model writes in a sandbox with no doors, red-team your own assistant and make it fail safe.
- Week 19Real people
You can interview real users, turn what they say into tests, weigh a feature's cost against its value, add plans and usage limits, and ship through CI/CD with a rollback.
Projects
- Project 5: Five real friends
Five people use FRIDAY for a week; their problems become tests, and the fixes ship through CI/CD. Weeks 17–19.
Skills you prove
Tiles on the periodic table of skills that this season lights up.
- Containers
- Package an app in a container image that runs the same everywhere (week 18)
- Threat model
- Threat-model an agent (lethal trifecta, OWASP) and red-team it (week 17)
- Interviews
- Interview users and find a workflow worth automating (week 19)
- PRD + ROI
- Write a PRD with eval-as-spec and an ROI model (week 19)
Checkpoint test: Shield
After week 19. Your attack tests block a known attack, and five people use FRIDAY.
- Explain the lethal trifecta, and which leg you removed from FRIDAY, in 2 minutes
- Your attack tests run in CI and block a known prompt injection
- FRIDAY starts from a fresh clone with one command, in containers, with its code running in a sandbox
- Five real people used FRIDAY, and you shipped a fix for something they told you