07 / 07Why it matters
Architecture, the multiplier
Four specialisms are four parts. Solution architecture decides how they join, in which order and against which proof, and it multiplies every one of them.
A squad can hold an analyst’s questions, perception, geospatial thinking and delivery, and still ship four separate answers. Architecture is the decision about how they join: in which order, across which seams, against which proof. Made first, it multiplies every specialism. Skipped, it wastes them.
One design, four owners
- The analyst's questionsWhat counts as control, and what a coach would accept.
- PerceptionNot observed is not the same as not there.
- Geospatial thinkingWho can reach the ball, in metres.
- DeliveryThe same bytes on every run.
- ProofThe analyst signs off on what the model says
- SelectionParameters chosen away from the match
- DecisionOne exact decode per half
- EvidenceFootball facts scored on every frame
- ObservationA missing ball is no evidence
- ConstraintsA pinned container with no network
The analyst says possession holds through a loose ball. Perception says not observed is not not there. In the architecture those two are one rule: a missing ball is no evidence. Geospatial thinking becomes the evidence layer. Delivery becomes a pinned container with no network.
Parts, or a system
- Home
- Away
- Dead ball
Evidence is scored on every frame. The decision is taken once per half, by an exact algorithm, over the whole sequence. Keeping those two machines apart is the architectural call that turns flicker into possessions.
What it bought
-
spellF1
0.340The Shrewdies decoder0.235Organisers' baseline method
-
macroF1
0.693The Shrewdies decoder0.383Organisers' baseline method
Tracking and tags in. Every parameter chosen away from the match. The result is measured on labels the design had never seen.
The working drawings are public. Start with The Shrewdies decoder, then walk the rest of Architecture.
A specialism is a strength. Architecture is what makes four people’s strengths one system.