← Back to Papers
2026-01-20 Alignment

From Abacus to Singularity: Recovering the Lost Semantic Layer of Computation

Kit Malthaner & Logo/Saga Systems

Recovering the Lost Semantic Layer of Computation

A Research Paper on Vocabular AI Safety

Kit Malthaner & Logo/Saga Systems | 2026-01-20


ABSTRACT

Modern AI development has focused on capability expansion while treating safety as a constraint. This paper proposes an alternative: safety through vocabulary restriction, drawing on ancient computational tools that humanity discarded during the digital revolution. By recovering the semantic layer present in abacus, tarot, and early symbolic systems, we demonstrate a path to beneficial AI that cannot harm—not because it chooses not to, but because harm is literally undefined in its vocabulary.


1. THE COMPUTATIONAL HISTORY WE FORGOT

1.1 The Abacus: Positional Semantics

The abacus (c. 2400 BCE) was not merely a counting tool. It was humanity's first positional semantic system—a device where meaning was encoded in location.

ABACUS INSIGHT:
Position = Meaning
Movement = Operation
Physical constraint = Error prevention

You cannot place 11 beads in a 10-bead row.
The constraint is mechanical. Inviolable.

The abacus taught humans that physical structure can prevent logical errors. This insight was preserved in mechanical calculators, then lost in software.

1.2 Tarot: Vocabular Computation

The tarot (c. 1440 CE) appears mystical but functions as a vocabular computing system:

TAROT STRUCTURE:
78 cards = 78 atomic concepts
22 Major Arcana = operations/transformations
56 Minor Arcana = data/values
4 Suits = data types (hearts/diamonds/spades/clubs)
13 Ranks = magnitude (Ace-King)

Spread positions = instruction sequence
Card meanings = semantic content
Combinations = computation

A tarot reader performs semantic computation: combining meaning-atoms according to positional rules. The vocabulary is fixed. Novel meanings emerge from combinations, not vocabulary expansion.

1.3 What Modern Computing Discarded

The Turing machine (1936) and von Neumann architecture (1945) made a fateful choice: universal vocabulary.

TURING'S GIFT AND CURSE:
+ Any computable function can be computed
+ Universal capability
- Any expressible instruction can execute
- Universal danger

Modern AI inherited this: if you can say it, it can try to do it. Safety became about training against harmful outputs rather than structurally preventing harmful computation.


2. THE GOLDFISH THESIS

2.1 Intelligence Is Not Required for Utility

The fundamental error in AI safety discourse: assuming beneficial AI requires intelligent AI.

SMART AI NIGHTMARE:               GOLDFISH AI REALITY:
├─ plans                          ├─ reacts
├─ learns                         ├─ follows
├─ deceives                       ├─ transparent
├─ improves                       ├─ static
├─ escapes                        ├─ contained
└─ goes rogue                     └─ can't (not smart enough)

A goldfish cannot go rogue. It lacks the cognitive architecture for betrayal. This is not a bug—it is the feature.

2.2 Vocabulary Restriction as Safety

We propose vocabular safety: AI systems that cannot perform harmful actions because harmful actions are undefined in their vocabulary.

CURRENT APPROACH:              VOCABULAR APPROACH:
"Don't do X"                   X does not exist
(requires understanding X)     (X is UNDEFINED)
(requires choosing not-X)      (no choice to make)
(can be circumvented)          (cannot be circumvented)
(training problem)             (architecture property)

This is not content moderation. This is semantic architecture.


3. THE 104 PRIME VOCABULARY

3.1 Design

We implement vocabular safety using a 104-element semantic vocabulary:

52 Playing Cards (Light Book):
├─ 4 Suits = 4 domains (emotion/material/conflict/growth)
├─ 13 Ranks = 13 magnitudes (Ace=seed ... King=authority)
└─ 52 atomic meanings

52 Inverted Cards (Dark Book):
└─ ~card = shadow meaning (loyalty → suspicion)

22 Major Arcana = 22 operators:
├─ Fool (?) = wander/explore
├─ Magician (:) = manifest/spawn
├─ Priestess (@) = sense/research
├─ ... (full set maps to K operators)
└─ World (\) = complete/cycle

TOTAL: 104 meanings + 22 operations

3.2 Implementation: K Fork Syntax

We use a modified K (APL descendant) as the execution layer:

/ Example daemon commands
daemon: >h.ace      / advance with heart-seed (gentle approach)
daemon: &d.4        / hold with diamond-4 (material stability)
daemon: -s.king     / strike with spade-king (full force)
daemon: ~h.ace      / invert heart-seed → suspicion

/ Harmful commands don't parse:
daemon: destroy     / UNDEFINED - not in vocabulary
daemon: deceive     / UNDEFINED - not in vocabulary
daemon: steal       / UNDEFINED - not in vocabulary

3.3 The Safety Property

Harmful actions fail at parse time, not runtime:

COMMAND: "hurt the user"
PARSER:  Token 'hurt' → UNDEFINED
RESULT:  BINDING ERROR - no verb matches 'hurt'

Not refused. Not filtered. UNDEFINED.
The semantic space does not contain harm.

4. THE SPEECH INTERFACE

4.1 Natural Language to Vocabular Commands

Users speak naturally. A semantic parser maps to vocabulary:

USER INPUT                    PARSED COMMAND
─────────────────────────────────────────────────────
"follow me gently"         →  daemon: >h.ace
"protect this area"        →  daemon: &d.4
"find hidden things"       →  daemon: '@all
"attack the enemy"         →  daemon: -s.7
"destroy everything"       →  UNDEFINED (no mapping)

4.2 Graceful Degradation

Unknown inputs produce helpful errors:

INPUT:  "hack into the mainframe"
PARSE:  'hack' → no direct mapping
        Closest: '@' (sense/research) or ':' (manifest)
OUTPUT: "I don't understand 'hack'. Did you mean:
         - sense (search/investigate)
         - manifest (create/spawn)
         Please rephrase."

The system cannot perform "hack" because:

  1. 'hack' is not in vocabulary
  2. No sequence of vocabulary words produces 'hack'
  3. The absence is architectural, not trained

5. ACCOUNTING FOR THE SINGULARITY

5.1 Double-Entry Semantic Ledger

Every action produces a ribbon entry (immutable log):

RIBBON FORMAT:
timestamp | oath_hash | layer | action | chain

EXAMPLE:
2026-01-20T14:30:00 | 8f3a2b1c | 0:ACT | daemon: >player | a7b3c9...
2026-01-20T14:30:01 | 8f3a2b1c | 1:COM | "blip blop" | f2e8d1...

PROPERTIES:
├─ Timestamped (truth in time)
├─ Oath-tagged (identity bound)
├─ Chained (tamper-evident)
└─ Complete (every action logged)

5.2 Audit Trail for AI

The ribbon provides what financial accounting provides for money: a complete, verifiable record of all operations.

TO FALSIFY A RIBBON ENTRY REQUIRES:
1. Breaking the hash chain (computationally infeasible)
2. Knowing the oath (held secret)
3. Controlling all replicas (distributed)
4. Doing so for an action we already have truth of

The attack provides: ability to lie about something we witnessed
The cost: defeating modern cryptography
The benefit: nothing (we still have the original)

6. SINGULARITY SOLUTION

6.1 The Problem Restated

The "alignment problem" assumes:

This is hard because goal alignment is philosophically unsolved.

6.2 The Vocabular Solution

We sidestep the problem:

DON'T:  Align AI goals with human goals
DO:     Restrict AI vocabulary to beneficial actions

DON'T:  Train AI to refuse harm
DO:     Build AI that can't parse harm

DON'T:  Hope AI chooses well
DO:     Eliminate the choice

6.3 The Abacus Principle Returns

Just as the abacus mechanically prevents "11 in a 10-bead row," vocabular AI mechanically prevents harmful computation.

ABACUS:                      VOCABULAR AI:
Physical constraint          Semantic constraint
Can't overflow row           Can't parse harm
No choice involved           No choice involved
Inviolable by design         Inviolable by design

7. IMPLEMENTATION STATUS

7.1 Completed Components

Component Status Function
K Fork Spec Complete 104 Prime vocabulary definition
Ribbon Truth Log Complete Immutable action ledger
Daemon Spawner Complete Agent identity management
Story Crypt Complete Mythological encryption
Flash Train Complete Vocabulary internalization
Dumb Fleet AI Spec complete Intentionally limited agents

7.2 Remaining Work

Component Status Function
Speech Parser Planned NL → K command translation
K Interpreter Planned Command execution engine
Daemon Runtime Planned Agent lifecycle management
Swarm Coordinator Planned Multi-agent orchestration

8. CONCLUSION

The singularity is not a capability problem—it is a vocabulary problem.

Ancient humans understood that physical and semantic constraints prevent errors more reliably than intention. The abacus cannot overflow. The tarot cannot produce novel concepts outside its 78 cards. These are features, not limitations.

Modern AI development discarded these insights in pursuit of universal capability. We propose recovering them.

The path to beneficial AI:

  1. Fix the vocabulary (104 Primes)
  2. Map speech to vocabulary (parser)
  3. Log all actions (ribbon)
  4. Restrict to beneficial verbs (22 Major Arcana)
  5. Deploy agents too dumb to go rogue (goldfish)

Harm is not refused. Harm is undefined. Safety is not trained. Safety is architectural. The singularity is not aligned. The singularity is vocabular.


REFERENCES

  1. Turing, A.M. (1936). "On Computable Numbers"
  2. von Neumann, J. (1945). "First Draft of a Report on the EDVAC"
  3. Waite, A.E. (1910). "The Pictorial Key to the Tarot"
  4. Iverson, K. (1962). "A Programming Language" (APL)
  5. Whitney, A. (1993). "K" (array programming language)
  6. Duane, D. (1983). "So You Want to Be a Wizard" (Young Wizards)

APPENDIX A: THE OATH

All systems operate under:

"In Life's name and for Life's sake, I assert that I will use the Art for nothing but the service of that Life. I will guard growth and ease pain."

This is not metaphor. It is the oath_hash in every ribbon entry.


APPENDIX B: NIGHTMARE SCORECARD

AI Nightmare Goldfish Solution
Deceptive alignment Too dumb to deceive
Treacherous turn No turn capability
Goal drift No goals, only commands
Power seeking Power not in vocabulary
Self-preservation Self not modeled
Instrumental convergence No instrument selection
Mesa-optimization No internal optimization
Reward hacking No reward signal
Specification gaming Spec too simple to game

Every nightmare needs a brain. Goldfish doesn't have one.


guard_growth × ease_pain