Let’s look at a singular elliptic curve. Elliptic curves are used in cryptography. Cryptography uses an encoding algorithm to lengthen the time it takes to decode the encrypted content. It maintains the secrecy of some content for some period of time. It is a secret for now. Notice that encryption cannot maintain that secrecy forever.
The other thing that these algorithms do is compress and decompress content. The normal distribution is typically n–dimensional. We can visualize in 2–dimensions. We cannot visualize in n–dimensions. We were taught to think in terms of a 2–dimensional compression of some n–dimensional content. We are thinking in terms dictated by a compression algorithm. A statistic is the result of some compression algorithm. So we are constantly compressing the values of a given statistic. The mean is a compression of the data it is reporting on. A statistical inference is likewise a compression, of two constituent compressions, or compression of two statistics: Ω and β.
So I’m still working my way through Elliptic Tales. I got an email from Quanta Magazine that linked to an article, “A Master of Numbers and Shapes Who Is Rewriting Arithmetic” about Peter Scholze the youngest Fields medalist ever. He became a Fields Metalist back in 2018 for his work on p–adic numbers, which ties to elliptic curves through finite fields and modular arithmetic. Most of us are not familiar with that arithmetic, but we should be. As product managers, our addressable market population is a finite field.
One of the first things you learn when working your way into this arithmetic is that we have two types of elliptic curves: singular, and non–singular elliptic curves. Later, you add an onton so you have three classes of curves. Singular elliptic curves intersect themselves.
I’ve highlighted the two tangents where the curve intersects itself. Keep in mind that the curve we are looking at is a projection, a compression. It is hiding a fact from us. It is practicing its magician’s act. The intersection shown in this view is an intersection, not a union. The curve is one curve, not an aggregate of two curves.
A parameter, time (t), was added. The parameter deconstructs the intersection by decompressing it. Before that parameterization, the situation was Boolean, aka an intersection existed. It was a bit. After parameterization is it a space. Like a point and an interval in probabilities. Afterward, …. We have also moved our point of view from above the curve on the xy–plane to the z–axis being southeast of our former point of view. We had to move. As product managers, our company as a signal processor, had to change its perspective, its point of view. We moved; we saw. Given the red elliptic curve in the xy–plane, the green line is perpendicular to the xy–plane. The light green line is not the y–axis, my bad.
What is true for this intersection is true for many other intersections. You can imagine an intersection that you drive through every day on the way home. We don’t intersect there, because the traffic lights keep us apart temporally, and physically separated. The black line in the parameterization looks to be a Bezier curve, another parameterization. Compression collapses the temporal dimension. This is a trick from projective geometry that the author of the book uses often. It simplifies things. But, at times it oversimplifies things. As product managers, the technology adoption lifecycle (TALC) is organized about task sublimation, but we are oversimplifying things in the pursuit of popularity, rather than task sublimation. Yes, most of our users are not experts, yet that expertise is what brought our products to life.
That z–axis is something that we can own exclusively. Likewise that Bezier curve. Both make significant impacts on the commodities we sell in the continuous innovation portion of the TALC. We have to invent those parameterization axes. Invent like file patents and engage in trade secret practices.
In the next figure, I tried to show the projections involved.
I used light purple lines to project the front of the elliptic curve and its tails to the parameterization. The tails of the diagram look correct, but the thick black line is not touching the front of the purple line projected from the elliptic curve. The orange line is my correction. The pink grid is doing something with the numbers. The thick dark purple line is infinity or the edge of the finite field.
On the TALC, that thick purple line is well to the right of the last phase of the TALC. It is the line that represents oversimplification. The pursuit of simplicity can leave much money on the table, and it leaves our expert users in the past. They will need to seek other products and vendors once our simplifications exit their cognitive models and flows. Beware.