Kept the draw branch alive if Portugal pressure stalled.
Project Turtle / first score-cloud postgame analysis / July 2, 2026
Portugal vs Croatia
The first Turtle cloud was not a mature model, but it did one thing correctly: it kept the 1-1, 2-1, and 3-1 family alive after match state showed Portugal pressure and Croatia scoring threat.
Four-score card1-1, 2-1, 3-1, 3-2
Result2-1 landed
SupportOver 2.5 live
Postgame lessonEvidence, not proof
Pregame / postgame analysis
The first hit stays in one match file.
Pregame analysisCloud: 1-1, 2-1, 3-1, 3-2.
The useful pre-match idea was not that Portugal must win by a particular margin. It was that Croatia were credible to score, while Portugal had enough pressure and attacking volume to keep the winning branch alive.
This made 1-1 the draw branch, 2-1 the central Portugal branch, 3-1 the pressure-extension branch, and 3-2 the fourth danger score. Those four scores describe a single family: Portugal control, Croatia score once or twice, and the match does not require an unrelated clean-sheet story.
Over 2.5 was only a support layer. It aligned with the 2-1 and 3-1 branches, but it was not allowed to replace the exact-score cloud.
Postgame analysisFinal score: Portugal 2-1 Croatia.
The 2-1 branch landed, so this file records an exact-branch hit. The important postgame analysis is procedural: Turtle wrote down a small score cloud before settlement and then let the match judge it.
The carry-forward rule is restraint. One hit does not prove edge. It proves that the score-orbital format can preserve the right branch when the data and live state point to a narrow favorite win with both teams scoring.
Postgame analysis board
The branch map was simple and useful.
Portugal win plus Croatia scoring threat. This is the branch that landed.
Same thesis with one more Portugal goal.
Rule carried forward
When a score cloud lands, Turtle records it as postgame analysis, not as proof of a finished system. The next model must still pass data mining, branch selection, and postgame analysis.