OpenProse Homeric Register

This is a skin layer. It requires prose.md to be loaded first. All execution semantics, state management, and VM behavior are defined there. This file only provides keyword translations.

An alternative register for OpenProse that draws from Greek epic poetry—the Iliad, the Odyssey, and the heroic tradition. Programs become quests. Agents become heroes. Outputs become glory won.

How to Use

1. Load prose.md first (execution semantics)
2. Load this file (keyword translations)
3. When parsing .prose files, accept Homeric keywords as aliases for functional keywords
4. All execution behavior remains identical—only surface syntax changes

Design constraint: Still aims to be "structured but self-evident" per the language tenets—just self-evident through an epic lens.

Complete Translation Map

Core Constructs

Composition & Binding

Control Flow

Error Handling

Session Properties

Shared appendix

Use shared-appendix.md for unchanged keywords and the common comparison pattern.

Recommended Homeric rewrite targets:

• session sample -> trial
• parallel sample -> host
• loop sample -> ordeal
• try/catch/finally sample -> venture / should ruin come / in the end
• choice sample -> crossroads / path

# Homeric
should **has security issues**:
  trial "Fix security"
or should **has performance issues**:
  trial "Optimize"
otherwise:
  trial "Approve"

Reusable Blocks

# Functional
block review(topic):
  session "Research {topic}"
  session "Analyze {topic}"

do review("quantum computing")

# Homeric
book review(topic):
  trial "Research {topic}"
  trial "Analyze {topic}"

do review("quantum computing")

Fixed Iteration

# Functional
repeat 12:
  session "Complete task"

# Homeric
12 labors:
  trial "Complete task"

Immutable Binding

# Functional
const config = { model: "opus", retries: 3 }

# Homeric
fate config = { muse: "opus", persist: 3 }

The Case For Homeric

1. Universal recognition. Greek epics are foundational to Western literature.
2. Heroic framing. Transforms mundane tasks into glorious trials.
3. Natural fit. Heroes face trials, receive tidings, win glory—maps cleanly to agent/session/output.
4. Gravitas. When you want programs to feel epic and consequential.
5. Fate vs decree. const as fate (unchangeable) vs let as decree (declared but mutable) is intuitive.

The Case Against Homeric

1. Grandiosity mismatch. "12 labors" for a simple loop may feel overblown.
2. Western-centric. Greek epic tradition is culturally specific.
3. Limited vocabulary. Fewer distinctive terms than Borges or folk.
4. Potentially silly. Heroic language for mundane tasks risks bathos.

Key Homeric Concepts

Alternatives Considered

For hero (agent)

For trial (session)

For host (parallel)

Verdict

Preserved for benchmarking. The Homeric register offers gravitas and heroic framing. Best suited for:

• Programs that feel like epic undertakings
• Users who enjoy classical references
• Contexts where "glory" as output feels appropriate

May cause unintentional bathos when applied to mundane tasks.