05Family 01 of 05
On the pitch
One architecture went from the board to the pitch. This page is the why: the constraints it was drawn under and the call each one forced. The what, with its numbers, is the study below.
- 1architecture fielded and measured
- 4hard constraints
- 9calls they forced
Constraints first
We did not choose an architecture and then defend it. We wrote down what the Initial Challenge would not allow, and the design space shrank to one column. The rules themselves are read as engineering requirements in The rules are the architecture.
From constraints to bytes
The same four constraints are visible in the running system. Inputs are read-only and nothing leaves the machine. The container is pinned and has no network. Two runs give the same bytes. The whole match fits inside the time a laptop CPU allows.
How an architect chooses here
- Write the constraints before the options. Compute, labels, time, reproducibility. They are inputs to the design, on the board first.
- Strike, then choose. Every option that violates one is out, however fashionable. The choice is made among what is left.
- Name the constraint in every call. If no constraint forced a choice, it is a preference, and it is not written up as a call.
- Choose away from the match. A design selected on the data it is graded on has proved nothing.
The architecture that survived, its evidence, its decode and its measured result are one study: The Shrewdies decoder.
In this family1
-
The architecture we fielded, end to end: football evidence on every frame, an exact Viterbi decode per half, and every parameter chosen away from the match.
- Fielded
- Geospatial
- Viterbi
- CPU-only