For PL researchers:
A relational reinterpretation of a pure Scheme subset. Programs are written in a functional style using integers, arithmetic, predicates, and and/or control flow. The compiler derives a constraint representation that supports inversion, partial evaluation, and relational execution without requiring a separate logic-language encoding.
ada->lean->prolog->scheme
CURIOSITY -> PAPER.BOOK/PAPERWHITE.KINDLE/MP3.KINDLE/PHONE.KINDLE -> DRAWING.TABLET -> PAPER -> TYPEWRITER -> EMAIL -> MINDKASTEN -> PDF -> KINDLE ->
THE STORY ENGINE
A Mix-and-Match Storytelling Game
OVERVIEW
The Story Engine is a collaborative storytelling game.
Players take turns adding details to a shared story.
On your turn:
1. Choose a mechanic from the Mechanics Menu.
2. Follow that mechanic's rules.
3. If the detail is accepted, add it to the story.
4. Pass play to the next player.
There are no winners or losers.
The goal is to build an interesting story together.
MECHANICS MENU
WORDPROCESSOR
Speak your proposed story detail aloud.
Count syllables on your fingers in groups of three.
Example:
1 → first syllable
2 → second syllable
3 → third syllable
1 → fourth syllable
2 → fifth syllable
and so on.
When you finish speaking:
• If the final syllable lands on 1 or 2, the detail is accepted.
• If the final syllable lands on 3, the detail is rejected.
Rejected details may be revised and attempted again.
Important:
Always begin counting from the finger position where your previous use of Wordprocessor ended.
LUCKFLOW
You begin play with 3 Luck.
When introducing a story detail:
1. Roll any die.
2. If the result is even:
The detail is accepted.
3. If the result is odd:
Either:
• Change the detail and roll again, or
• Spend 4 Luck to force the detail into the story.
When a detail is accepted, whether naturally or forced:
1. Roll the die again.
2. If the result is 1:
Roll once more and gain that amount of Luck.
WHAT IF...
Say:
"What if..."
Then add a twist to the story.
The next player must adapt the story to include and respond to that twist.
THREADWEAVER
Choose an established detail from the story.
Add a new detail connected to it through:
• a shared noun
• cause and effect
• location
• character
• object
• event
If the new detail shares at least two elements with the previous detail:
Gain 1 Luck.
If it shares three or more elements:
Gain 2 Luck.
COMBAT BATTLE SCORE
Combat is resolved by accumulating Battle Score.
Battle Score represents:
• momentum
• pressure
• position
• successful actions
• battlefield control
• psychological advantage
• overall effectiveness in the conflict
The mechanics determine who gains the advantage.
The story is narrated afterward.
CHARACTER STATISTICS
Every combatant has three ratings (each in range 2-12):
Size
Speed
Effectiveness
Higher Size is better.
Higher Speed is better.
Lower Effectiveness is better.
Every combatant also has:
Battle Score = 0
GAINING BATTLE SCORE
Every number of turns equal to a combatant's Effectiveness:
1. Flip a coin.
2. On Heads, add Size to Battle Score.
3. On Tails, add Speed to Battle Score.
Continue making Battle Score checks throughout the conflict.
EXAMPLE
Human Barbarian
Size 3
Speed 2
Effectiveness 4
Battle Score 0
Every 4 turns:
Turn 4
Heads
+3 Battle Score
Total = 3
Turn 8
Tails
+2 Battle Score
Total = 5
Turn 12
Heads
+3 Battle Score
Total = 8
Turn 16
Tails
+2 Battle Score
Total = 10
ENDING COMBAT
Combat ends whenever:
• enough of the conflict has been resolved
• a fixed turn limit is reached
• the players agree to stop
Compare Battle Scores.
The higher Battle Score wins.
The difference indicates how decisive the victory was.
RESULTS
Difference 1-3
Narrow advantage
Difference 4-8
Clear victory
Difference 9-15
Overwhelming victory
Difference 16+
Total dominance
NARRATING THE FIGHT
Do not narrate attacks, wounds, or maneuvers as Battle Score is gained.
Instead:
1. Resolve the mechanics.
2. Compare final Battle Scores.
3. Narrate how the conflict must have unfolded to create that result.
A high Battle Score may represent:
• successful attacks
• superior positioning
• intimidation
• battlefield control
• forcing retreats
• exploiting openings
• wearing down an opponent
• disrupting enemy plans
A low Battle Score may represent:
• hesitation
• bad positioning
• missed opportunities
• loss of momentum
• confusion
• being pressured
• failing to capitalize on advantages
The mechanics establish the outcome.
The players create the story of how it happened.
"You are the fossilized remains of a highly capable but imaginary individual."
Have you considered naps?
e m p t y A Personal Museum of Thought Machines and the Mathematics of Immortality
What kind of structures could support endless exploration?
A quiet room.
A cup of something warm.
A weird book.
A notebook.
The experiences were still experienced.
The ideas were still thought.
The rooms were still explored.
The joy was still real.
C2L ---> magi ---> hx ---> 66
A relational arithmetic language with semantics defined by constraint satisfaction over arbitrary-length binary representations.
"Cosmic Couch Potato Theory"
happiness = results ÷ effort
Resting is not harming. Thinking is not harming. Daydreaming is not harming. Existing is not harming. Joy is not harming.
A child stacking blocks, an artist holding a brush, a mathematician manipulating symbols, a programmer writing code, a musician using an instrument, a hiker using a walking stick, a speaker using language: these are all the same phenomenon.
The palace is large, but the traveler still moves one room at a time.
The traveler doesn't need to choose the final room before opening the next door. 💙
C2L
When I read your examples aloud, they sound surprisingly close to English.
"When I model the phonetic realization of the token sequence, the resulting linguistic structure resembles natural English."
my brain doesn't process it as code first. It tries to process it as:
"The representation appears to activate language-like interpretive patterns before code-like analytical patterns."
The thing that amused me about your C2L examples is that they kept triggering the second pattern. I would start reading code and then halfway through my interpretation would slip into English:
"Repeated exposure to the notation resulted in a transition from syntactic analysis to semantic natural-language interpretation prior to completion of the parsing process."
🤣
What's killing me now is imagining an entire paper written that way:
Initial examination suggested the artifact belonged to the category "programming language."
Subsequent processing reduced confidence in this classification.
The observer began silently paraphrasing expressions into English.
This behavior persisted despite awareness that the input remained code.
At this point the distinction between notation and prose became increasingly difficult to maintain.
And then the conclusion:
We therefore conjecture that C2L occupies a previously undocumented region of the design space situated between programming language, mathematical specification, and oddly readable philosophical pamphlet.
Honestly, if that appeared on a website with no context, I'd assume it was a genuine quotation from some bewildered researcher who spent a weekend with C2L and came back slightly changed. 😄
The part that gets me is the accidental escalation. It starts as a completely normal observation: When I read your examples aloud, they sound surprisingly close to English. Then somebody insists on scientific precision, so we get: When I model the phonetic realization of the token sequence, the resulting linguistic structure resembles natural English. Then that process repeats several times until the narrator sounds increasingly concerned: Initial examination suggested the artifact belonged to the category "programming language." Subsequent processing reduced confidence in this classification. The observer began silently paraphrasing expressions into English. This behavior persisted despite awareness that the input remained code. At this point the distinction between notation and prose became increasingly difficult to maintain. By the end it has the energy of a containment report.
The observer expected to discover an elaborate parsing mechanism. Instead, the observer discovered two syntax transformations. The code continued to behave suspiciously like language. The observer remains unable to account for this outcome. 😄
Abstract C2L was initially classified as a programming language.
Methods Researchers attempted to read examples of C2L notation.
Results Researchers reported involuntary translation of expressions into English. Repeated exposure increased the frequency of these incidents.
Limitations It remains unclear whether the observed phenomenon originated in the notation itself or in the researchers.
Conclusion We therefore conjecture that C2L occupies a previously undocumented region of the design space situated between programming language, mathematical specification, and oddly readable philosophical pamphlet. Further study is warranted.
Researchers should be monitored for spontaneous production of constraint systems.