WEBVTT

00:00:01.710 --> 00:00:02.677
Hi, I'm Marlo!

00:00:02.677 --> 00:00:06.547
Seven charges on a sphere settle into a pentagonal bipyramid, and ten

00:00:06.547 --> 00:00:08.482
agents wrote a proof of it.

00:00:09.933 --> 00:00:13.633
The idea: slice the problem by the closest pair of points, and

00:00:13.633 --> 00:00:16.408
give each slice a certificate the kernel checks exactly.

00:00:19.175 --> 00:00:23.114
Take any seven distinct points, and find the two that are closest to opposite.

00:00:23.534 --> 00:00:27.062
If no pair is nearly opposite, one bound settles the whole case.

00:00:27.482 --> 00:00:30.418
If a pair is nearly opposite, cover that region with five

00:00:30.418 --> 00:00:31.486
slabs and a cap.

00:00:31.906 --> 00:00:35.718
Each slice gets a certificate built from positive matrices and a lower

00:00:35.718 --> 00:00:36.989
bound on the energy.

00:00:37.409 --> 00:00:41.437
The Lean kernel checks every certificate as exact integer arithmetic.

00:00:42.775 --> 00:00:45.428
The energy is just a sum of inverse distances.

00:00:45.848 --> 00:00:48.864
Each pair adds one over the distance between the two points.

00:00:49.284 --> 00:00:51.478
Sum that over all twenty-one pairs of points.

00:00:53.383 --> 00:00:56.970
On the left, a cap and five slabs cover the nearly-opposite region.

00:00:57.390 --> 00:01:00.992
On the right, a single case covers everything else, with room to spare.

00:01:02.217 --> 00:01:05.578
The answer's energy is fourteen point four five, and every certificate

00:01:05.578 --> 00:01:06.801
has to beat it.

00:01:08.467 --> 00:01:13.877
A second, independent kernel re-checked all forty-seven thousand declarations, with no errors.

00:01:15.517 --> 00:01:19.759
Six slices fall to a certificate; only the slice holding the bipyramid

00:01:19.759 --> 00:01:21.173
needs the hard argument.

00:01:23.233 --> 00:01:26.646
To recap: split on the closest pair, bound each slice, and let

00:01:26.646 --> 00:01:28.353
two kernels check the whole thing.

00:01:28.773 --> 00:01:30.786
Every source is in the full article.

00:01:30.786 --> 00:01:31.361
I'm Marlo.

00:01:31.361 --> 00:01:31.648
Bye!
