← Latest papers
💻 computer science

Yeo's Theorem for Locally Colored Graphs: the Path to Sequentialization in Linear Logic

This paper presents a modular approach to sequentialization in linear logic by generalizing Yeo's theorem for locally colored graphs, utilizing a "cusp minimization" lemma to extract splitting vertices and recover sequent calculus derivations from proof nets without altering their underlying graph structure.

Original authors: Rémi Di Guardia, Olivier Laurent, Lorenzo Tortora de Falco, Lionel Vaux Auclair

Published 2026-03-04
📖 5 min read🧠 Deep dive

Original authors: Rémi Di Guardia, Olivier Laurent, Lorenzo Tortora de Falco, Lionel Vaux Auclair

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are trying to solve a giant, complex jigsaw puzzle. But here's the twist: the pieces aren't just shapes; they are logical arguments, and the picture they form is a mathematical proof. In the world of Linear Logic, these puzzles are called Proof Nets.

For decades, mathematicians have known how to build these puzzles from a set of instructions (called a "sequent calculus derivation"). But the hard part has always been the reverse: looking at a finished, messy puzzle and figuring out exactly what instructions were used to build it. This process is called Sequentialization.

This paper is like a new, super-smart guide that tells you exactly how to take apart any valid proof net, piece by piece, until you get back to the original instructions. And the secret weapon they use? A clever trick involving colors and a theorem named after a mathematician called Yeo.

Here is the breakdown of their discovery, using simple analogies:

1. The Problem: The Tangled Knot

Imagine a proof net as a web of strings connecting different points. Some strings are "solid," some are "dashed," and some are "dotted."

  • The Rule: In a valid proof net, you shouldn't be able to trace a loop (a cycle) that follows a specific pattern, like "solid-dashed-solid-dashed." If you can find such a loop, the proof is broken (it's a logical fallacy).
  • The Goal: We want to find a "cut point." If you cut this specific point, the whole web falls apart into smaller, manageable pieces, and none of those pieces are connected to the cut point by more than one color of string.

2. The Secret Sauce: "Local Coloring"

Usually, mathematicians color an entire string one color. But the authors realized that in these logical webs, the "color" of a string might look different depending on which end of the string you are looking at.

  • The Analogy: Imagine a rope. From the left side, it looks red. From the right side, it looks blue.
  • The "Cusp": If you walk along a path and you hit a knot where the rope looks the same color coming in and going out (e.g., red-in, red-out), that's a cusp. It's a "traffic jam" in the logic.
  • The Goal: The authors want to find a point where you never get stuck in a traffic jam. They call this a Splitting Vertex. If you find one, you can safely cut the web there.

3. The Magic Trick: "Cusp Minimization"

How do they find this magical cutting point? They use a strategy they call Cusp Minimization.

  • The Metaphor: Imagine you are walking through a maze full of dead ends (cusps). You want to find a path with no dead ends.
  • The Trick: If you get stuck in a loop with dead ends, the authors show you a way to "shrink" the loop. You take a shortcut that bypasses the dead ends, creating a smaller loop with fewer dead ends.
  • The Result: If you keep shrinking these loops, eventually you either find a loop with zero dead ends (which proves the proof is broken) or you run out of loops entirely. If you run out of loops, you know you must have found a "Splitting Vertex"—a safe place to cut.

4. Why This is a Big Deal

Before this paper, proving that you could break down a proof net required very complicated, heavy machinery. You often had to redraw the graph or change its structure to make the math work.

  • The Innovation: This new method is modular and non-invasive. It's like having a pair of scissors that can cut the web in different ways depending on what you need, without ever having to glue the web back together or redraw it.
    • Need to cut at a specific type of logical junction? Just change the "coloring rules" slightly.
    • Need to cut at the very end of the proof? Change the rules again.
    • Need to handle complex "Additive" logic (where choices are made)? They generalized the theorem to handle those too.

5. The "Yeo" Connection

The paper is named after Yeo's Theorem, a known result in graph theory (the math of networks). The authors didn't just use Yeo's theorem; they upgraded it.

  • Original Yeo: "If you have a network with no bad loops, there is a safe cutting point."
  • New "Yeo-style" Theorem: "If you have a network with local colors (where the color depends on the direction), and no bad loops, there is a safe cutting point that we can choose specifically."

Summary: What Did They Actually Do?

They took a very difficult problem in computer science and logic (how to reverse-engineer a proof) and solved it using a fresh perspective on graph theory.

  1. They invented a way to look at logical proofs as colored maps.
  2. They proved that if the map is valid, there is always a "safe exit" (a splitting vertex).
  3. They showed that you can find this exit by looking for the "least tangled" path (cusp minimization).
  4. They demonstrated that this single, elegant idea works for simple proofs, complex proofs with choices, and even proofs with "mixing" rules.

In a nutshell: They found a universal "key" that can unlock any valid logical proof, turning a tangled mess of logic back into a clear, step-by-step instruction manual, all by looking at the colors of the connections.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →