Turning brittle notebooks into signed pipelines

Our Tokyo cohort starts every residency by printing the dependency closure of a notebook—not to shame authors, but to show which cells silently reach production tables. That single ritual already halves the “works on my laptop” tickets we see during intake.

The second week focuses on packaging: converting exploratory cells into callable modules while preserving markdown commentary legal teams expect. We keep the prose adjacent to the code so risk reviewers can follow intent without opening a separate wiki.

By week four, teams ship a signed artifact bundle: container digest, data snapshot hash, and a changelog written in plain language. Nothing here promises magical speed gains—just fewer midnight pages when an auditor asks why a feature changed shape overnight.

Graduates leave with a template we call the ink ribbon: a thin vertical doc that lists owners, rollback owners, and the exact command used to rebuild the slice. Borrow it, remix it, argue with it—just do not file it untouched.