Frostline launch film, cut five

A 64 second animatic with sound. Every chapter now shows the one line an agent types. Headphones help.

0:00 / 1:04

What the film sells

One sentence: every agent gets its own iPhone. Apple's simulator is one window on one Mac, drawn for a person. Frostline is an iPhone simulator on Linux that an agent drives with code. The film gives four reasons to believe it, and each is something the Mac simulator does not do.

The four reasons

  • It runs where agents run. Linux, thirty six to a small box, drawing only when looked at.
  • One call acts and checks. When the check fails, the answer says what it saw and what to try.
  • Time is under control. Stop an animation and step it a frame at a time.
  • So is everything around the app. Record the network once and replay it on every run. Launch every variant in one call and find the one that breaks.

Network: replay leads, hold follows

Replay is the feature a team pays for. A flow that passed yesterday passes today, with no backend and no flake, which is what makes CI on agents trustworthy. Holding a request in mid flight is the better picture and a real debugging tool, so it gets the last two seconds of the chapter. I would build replay first.

What changed from cut four

  • Cold phones are white halftone dots on black. Dot size carries the picture.
  • The opening phone is larger and runs off the bottom of the frame.
  • Screens slide like real navigation. No more double exposure between chapters.
  • The box of phones pops in as a ripple and leaves the same way. No grey ghosts.
  • Stop time is a split frame. Phone on the left, words and the frame count on the right at equal weight. The bars under the number are the spring curve.
  • The network is a cassette. It records, rewinds, plays three runs and holds.
  • Variants peel off like cards. Dark flips over, the Duo unfolds, and they stack back when done.

What is real today

Shipping or in review: Linux, the box of thirty six, drawing on demand, the act and check call with a typed failure, zoom, saved state restore, the variant matrix. Drafted and proven on a lab kit: frame stepping. Not built yet: network record, replay and hold as agent calls. A record and replay proxy exists only as an internal test tool. The contrast figure on the dark variant is illustrative.

Beat sheet

TimeCaptionThe agent typesWhat you see
0:00Nobody is lookingA cursor types the line and grows into a frozen pixel phone. Now you are. It thaws and the ground turns to paper.
0:09Agents only glancePull back to thirty six phones in one box, dark until an agent looks.
0:16Look closerlook({ zoom })A card lifts out of the phone and sharpens from 1x to 3x.
0:21Act and checktap(…, { expect })The tap fails. A result tray says what it saw, the log line and what to try. Restore, run again, passed.
0:31Stop timestep()A glass sheet stops mid air. Three slow steps, then eight fast. The ticks are the spring curve.
0:40Record, replay, holdnet.replay()Three requests land on a tape. The server goes offline and three runs pass from the tape. A fourth is held in flight.
0:48Every variantmatrix()Light, dark, compact and Duo on iOS 26 and 27. Three pass. Brackets land on the one that does not.
0:54Open source soonBack to the box, cut to black, the name and the line. You can stop looking now.

Grade these

  • Is it clear in ten seconds what this is and who it is for?
  • Does the code line under each caption help, or is it one thing too many?
  • Act and check, with the failure in the middle.
  • The network chapter. Replay first, hold second.
  • Every variant, with one failing.