1. ROLL SIGNAL —— 极速滑行中 2. BLUE CURRENT —— 巨型文字间的畅游 3. CITY LOOP —— 骑行穿梭全城 4. BREW PAUSE —— 慢下来的咖啡时光
这一波尝试将“人类碎片”融入速度、流水、城市律动与宁静瞬间。
Prompt 在评论区 👇
🤯 AI Visual Systems Vol.17.1: Motion & Pause! Made with ChatGPT-Image2
Strong foreground perspective pulls each subject through the letters!
1. ROLL SIGNAL — roller skating in motion 2. BLUE CURRENT — swimming through oversized type 3. CITY LOOP — cycling across the city 4. BREW PAUSE — slowing down with coffee
This round pushes Human Fragments through speed, water, city rhythm, and a quiet pause.
I verified the cost saving in my own terminal by invoking the same Anthropic model with the same prompt.
The underlying engineering by Ship is actually interesting, and the patterns can be used in any production LLM stack.
Essentially, a trained model is a frozen artifact.
Every request performs the same forward-pass, whether it extracts a date or refactors a module, because the compute decision was made at training time, before the request existed.
Ship makes that decision at inference time instead.
After seeing a request, it searches over executions, involving single models, cascades, ensembles, or harnesses with tools, and serves the cheapest one that will match the reference model's quality.
This is not a basic router, because picking a cheaper model per query doesn't ensure the cheaper model preserves the original's behavior, like output shape, tool-call patterns, and refusals.
Ship measures this equivalence directly.
Outputs stay distributionally indistinguishable from the reference model, not token-identical, since two calls to the same model already differ, but they are indistinguishable in capability and behavior.
Of course, some requests execute cheaply and some cost Ship more than the customer pays, but the price per request is still a flat 50% off either way, so the execution-cost variance moves off the application's bill entirely.
The video below depicts the cost savings and output in my real invocation, and I partnered with the team to put this together.