Converge
Open the app

Week 24 · Season 7 · Alive

Running for real

You can monitor FRIDAY for real people, catch drift early, swap its model with a gate and a canary, run an incident and write a blameless postmortem, and keep its logs private and its labels honest.

Open week 24 in the app

This week

  • Green tests, angry users: monitoring
  • The slow leak: drift
  • Swap the engine mid-flight: migration and canary releases
  • 2:07 a.m.: incidents and blameless postmortems
  • Logs that leak: privacy and AI rules
  • Go deeper: SLOs, error budgets, shadow traffic, EU AI Act

How you learn

Read a week of FRIDAY's log for quiet failures, score drift by hand, and rehearse the incident routine before a real one happens.

What you build

Dashboards and alerts for FRIDAY: four signals and an SLO on one screen, alarms that wake you only for real problems, logs with private data removed, and a runbook you've practised.

Stretch: Move FRIDAY to a new model behind a gate, shadow traffic and a canary, with a rollback rule written first, and write up what you saw.

What you ship

Project 7: The public demo. FRIDAY live for strangers, with a system diagram, a cost sheet and a demo you can defend.

  • OPS.md with four signals, an SLO and two alert rules, plus a dashboard
  • Redacted logs with a 30-day timer, and tests that prove it
  • A runbook and a blameless postmortem of a practice incident

Lessons

  1. Green tests, angry users

    After this deck you can explain why FRIDAY can pass every test and still fail real people, name the four golden signals of monitoring, and use quiet user signals and an online eval to find what's going wrong.

    12 minFull access

  2. The slow leak

    After this deck you can explain drift (the world moves, FRIDAY stays the same), compare this week's questions with last month's using one drift score, and set an alarm that rings for a real slide, not for one bad day.

    12 minFull access

  3. Swap the engine mid-flight

    After this deck you can plan a model migration: pin a dated model, gate the new one on your own test cases slice by slice, and roll it out as a canary release with a rollback rule written first.

    12 minFull access

  4. 2:07 a.m.

    After this deck you can run an incident in the right order (take charge, stop the harm, tell people, take notes, then find the cause) and write a blameless postmortem that fixes the system instead of blaming a person.

    12 minFull access

  5. Logs that leak

    After this deck you can find personal data in FRIDAY's logs, apply redaction before anything is written, keep less for less time, and explain the basics of the GDPR and the EU AI Act (with official sources).

    12 minFull access

  6. Go deeper: budgets, shadows and the rulebook

    After this deck you can write a service level objective for FRIDAY, turn it into an error budget and a burn-rate alarm, test a new model with shadow traffic, and find your way around the official EU AI Act sources.

    12 minFull accessGo deeper · optional

Labs

Python in the browser, next to the lessons.

Weekend build

Hand-picked official docs, papers and talks.