AI Persistent Storage Layer, landing page animation, 1200 x 675 prototype

A, Corrected. The stores keep their labels, shrink to chips and drop straight down into a distinct destination below the store band. The band is a neutral carbon tier and a true occluder for the whole arrival. Brand Red and the TiDB logo fire together as one beat at the last chip's landing, and the finished layer settles up into place under the four categories at that same moment. The layer's six capabilities then reveal as one row, in the order your source deck writes them.

Revision 4, 2026-07-31. Your four notes: the gap between the Agent Harness and the category row opens from 20px to 32px, taken from the ratio in your own source deck; the closing line now reads Resumable agent workflows; the falling boxes no longer stop dead in mid air part-way down (they were finishing the drop in the first third of their window and then holding still for three quarters of a second) and the four columns now fall left to right instead of in a scattered order; and the systems counter is never covered again, on any frame. Pace, landing times and the payoff are unchanged.

Revision 2, 2026-07-29 evening. Four changes from Ramnath's notes: each store now drops straight down onto its own word instead of turning left or right (the layer's word order was re-ordered to match the stores, which is what removes the turn); the empty space and the long arrows between the categories and the layer close up at the payoff, so the finished frame keeps the same spacing rhythm top and bottom; Full-text and Files are out of the animation, so all four capability words now animate together; and the bottom tier carries the +2pt type with the rule a little higher, one click from the original.

C, Spec as written. The client's animation notes run verbatim: move down 20 to 30px, scale down, lose borders and labels, dissolve into the red container in the band the stores already occupy, brand leading and logo trailing. Shown for an honest comparison, not as a recommendation.

Pace. Recommended (11.0s) is the default, because at the specced 7 seconds the consolidation shifts pass faster than a viewer can follow. Client 7s is the original timing, unchanged, so the budget stays one click away and the comparison is explicit. Variant C is always the client's 7s spec, so the pace toggle does not apply to it.

Bottom tier. +2pt is the default and applies your note: the front wall of the layer grows 6px, the horizontal rule moves up 4px, and the four capability labels go from 15px to 17px with slightly larger icons. Original is the version you already saw, so the two are one click apart. Variant C is the client spec, so the tier change does not apply to it.

Inspect any frame. Append ?t=6.2 to the file URL to freeze the timeline at that exact second of whichever pace is active (?p=fast selects Client 7s) with all page chrome hidden. ?v=C selects the variant, ?b2=0 shows the original bottom tier, ?rm=1 forces the reduced motion fallback.