03 The constraint
Limits
The prompt has no budget.
Ten models, ten captures, one laptop. Every frame on this site ran on a free tier. Eight finished. Two were cut. The file is done; the compute is not.
- Models
- 10
- Finishes
- 8
- Cut
- 2
- Paid tiers
- 0
- Operators
- 1
Built between rate limits.
KESTREL was built after midnight, on free tiers, between queues. No paid models. No API credits. No team. One operator, a laptop, and whatever the free plan would give before the window closed.
The proof run is the receipt: ten models, eight finishes, one stopped at the plan, one killed at the five-hour limit. The prompt was not the bottleneck. The budget was.
The models that gate the real work sit behind a card: longer contexts, reasoning tiers, agents that do not flinch. Those runs cost money this project does not have. So the work goes on in the gaps. A free window. A queue. A build that may not finish.
The prompt was not the bottleneck. The budget was.From the field notes
Four hard edges.
Free tiers only
Every frame came from a free plan, a trial, or a window. No paid tier is in the loop.
One operator
No lab, no team, no second box. Ten runs shared one laptop and one clock.
One run per model
Frames are captures, not benchmarks. A different day can produce a different result.
Time, not policy
Two of the ten runs did not finish. Neither was a refusal: one stopped at the plan, one hit a provider limit.
Put compute behind it.
The file is free. The compute is not. Support goes to model credits and run time. Nothing else.
0x8d4a012b743b68e2773d21080fdf9f5c27706082
BEP20 only. Another chain or another asset is lost. No promises, no product, no refunds.