Computable Structuralism: A Categorical Rewrite Calculus of Mythic Variants
This paper proposes "Computable Structuralism," a formal categorical framework that models mythic and narrative variants as typed rewrite programs on a dual-register state, thereby translating Lévi-Straussian structural analysis into a computable system capable of testing coherence, diagnosing structural failures, and quantitatively bridging anthropology with cultural analytics across diverse storytelling traditions.
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 have a giant library of stories: fairy tales, religious myths, superhero movies, and long TV franchises. Usually, when scholars compare these stories, they look for similarities: "Oh, both Cinderella and Spider-Man have a sad childhood!" or "Both have a magical helper!"
But this paper argues that looking for surface similarities is like judging two cars only by their paint color. It misses how the engines actually work. The authors, led by Juan J. Segura, propose a new way to compare stories that treats them like mathematical puzzles or computer code, but one that still keeps the human meaning of the story intact.
Here is the breakdown of their idea using simple analogies:
1. The Two-Register Machine (The "Social" vs. The "Rules")
The authors suggest that every story runs on a machine with two distinct "registers" (like two tracks on a cassette tape or two lanes on a highway):
- Register X (The Everyday Lane): This is the messy, physical world. It has the characters, the fights, the tools, the money, and the physical actions. Example: A wolf eating a grandmother, or a superhero punching a villain.
- Register Y (The Rulebook Lane): This is the invisible world of laws, taboos, prophecies, and contracts. It's the "why" that makes the action matter. Example: A mother's warning not to talk to strangers, a law requiring superhero registration, or a divine curse.
The Insight: In most stories, the physical action (X) only becomes a "story" when it bumps up against the rules (Y). If a wolf eats a grandma, that's just a tragedy. But if he does it because he broke a taboo, or if the grandma survives because of a prophecy, the story gains its structure. The authors claim you can't understand the story unless you track both lanes simultaneously.
2. The "Transformation" Test (The Magic Trick)
Structuralists (like the famous Claude Lévi-Strauss) believe that stories are related not because they look alike, but because one can be transformed into another through specific rules (swapping roles, inverting values).
The authors turn this into a math test. They imagine two ways to update a story:
- Update A (The Direct Way): You change the story, but you keep the roles the same. (The hero is still the hero; the law is still the law).
- Update B (The Canonical Way): You perform a "magic trick" where you swap things around. Maybe the thing that was a "rule" becomes the "villain," or the "hero" becomes the "victim."
The "Coherence Check":
The paper asks: If I swap the roles (Update B), does the story still make sense mathematically?
They use a concept called a "Natural Transformation" (a fancy math term) which acts like a quality control stamp.
- Pass: If the story still holds together after the swap, the transformation is "legal." The two stories are structurally related.
- Fail: If the story falls apart (e.g., the "law" suddenly acts like a "tool" and breaks the logic), the transformation is "illegal." This failure isn't a mistake; it's a diagnosis. It tells the researcher, "You tried to compare these two things, but they don't actually fit together under these rules."
3. The "Key" (The Story's Fingerprint)
Stories happen in a specific order. If you swap the order of events (e.g., the hero gets the sword after the battle instead of before), the story changes completely.
To capture this, the authors assign every story a "Key" (labeled A through E). Think of this like a fingerprint or a barcode for the story's sequence.
- It doesn't tell you what happens, but how the events are arranged.
- This allows them to quickly compare 80 different stories to see if they share the same "structural rhythm," even if one is about a frog prince and the other is about a space wizard.
4. The Experiment: 80 Stories
The team tested this system on 80 stories:
- 20 Folktales (e.g., Cinderella)
- 20 Religious Myths (e.g., Adam and Eve)
- 20 Superhero stories (e.g., Batman)
- 20 Franchises (e.g., Star Wars)
What they found:
- The "Rulebook" is real: In 74% of the stories, the "Rulebook Lane" (Y) was explicitly named. Whether it was a "taboo," a "law," a "prophecy," or a "contract," the stories relied on these invisible rules to drive the plot.
- The System Works: They could successfully map these different genres onto the same two-track system. A "fairy godmother" in a fairy tale and a "registration law" in a superhero movie both function as the "mediator" or "constraint" in the same mathematical slot.
- It Catches Errors: When they tried to force a story into the wrong slot (like calling a "law" a "tool"), the math broke. This proved the system is strict enough to catch bad comparisons.
The Bottom Line
This paper doesn't try to replace human storytelling or tell us which stories are "better." Instead, it builds a translation tool.
It turns the vague idea of "structural similarity" into a testable, reproducible math problem. It allows researchers to say: "These two stories are related not just because they look alike, but because they follow the same underlying logic of how physical actions interact with social rules."
It's like taking a messy pile of different colored LEGO bricks and realizing they all snap together using the exact same hidden mechanism. The authors have just written down the manual for that mechanism.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.