loudmouth-ai 0.1.0 → 0.2.0

package/extensions/open-prose/skills/prose/alts/homer.md

@@ -1,346 +0,0 @@
----
-role: experimental
-summary: |
-  Homeric register for OpenProse—an epic/heroic alternative keyword set.
-  Heroes, trials, fates, and glory. For benchmarking against the functional register.
-status: draft
-requires: prose.md
----
-
-# 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
-
-| Functional | Homeric | Reference |
-|------------|---------|-----------|
-| `agent` | `hero` | The one who acts, who strives |
-| `session` | `trial` | Each task is a labor, a test |
-| `parallel` | `host` | An army moving as one |
-| `block` | `book` | A division of the epic |
-
-### Composition & Binding
-
-| Functional | Homeric | Reference |
-|------------|---------|-----------|
-| `use` | `invoke` | "Sing, O Muse..." — calling upon |
-| `input` | `omen` | Signs from the gods, the given portent |
-| `output` | `glory` | Kleos — the glory won, what endures |
-| `let` | `decree` | Fate declared, spoken into being |
-| `const` | `fate` | Moira — unchangeable destiny |
-| `context` | `tidings` | News carried by herald or messenger |
-
-### Control Flow
-
-| Functional | Homeric | Reference |
-|------------|---------|-----------|
-| `repeat N` | `N labors` | The labors of Heracles |
-| `for...in` | `for each...among` | Among the host |
-| `loop` | `ordeal` | Repeated trial, suffering that continues |
-| `until` | `until` | Unchanged |
-| `while` | `while` | Unchanged |
-| `choice` | `crossroads` | Where fates diverge |
-| `option` | `path` | One road of many |
-| `if` | `should` | Epic conditional |
-| `elif` | `or should` | Continued conditional |
-| `else` | `otherwise` | The alternative fate |
-
-### Error Handling
-
-| Functional | Homeric | Reference |
-|------------|---------|-----------|
-| `try` | `venture` | Setting forth on the journey |
-| `catch` | `should ruin come` | Até — divine ruin, disaster |
-| `finally` | `in the end` | The inevitable conclusion |
-| `throw` | `lament` | The hero's cry of anguish |
-| `retry` | `persist` | Enduring, trying again |
-
-### Session Properties
-
-| Functional | Homeric | Reference |
-|------------|---------|-----------|
-| `prompt` | `charge` | The quest given |
-| `model` | `muse` | Which muse inspires |
-
-### Unchanged
-
-These keywords already work or are too functional to replace sensibly:
-
-- `**...**` discretion markers — already work
-- `until`, `while` — already work
-- `map`, `filter`, `reduce`, `pmap` — pipeline operators
-- `max` — constraint modifier
-- `as` — aliasing
-- Model names: `sonnet`, `opus`, `haiku` — already poetic
-
----
-
-## Side-by-Side Comparison
-
-### Simple Program
-
-```prose
-# Functional
-use "@alice/research" as research
-input topic: "What to investigate"
-
-agent helper:
-  model: sonnet
-
-let findings = session: helper
-  prompt: "Research {topic}"
-
-output summary = session "Summarize"
-  context: findings
-```
-
-```prose
-# Homeric
-invoke "@alice/research" as research
-omen topic: "What to investigate"
-
-hero helper:
-  muse: sonnet
-
-decree findings = trial: helper
-  charge: "Research {topic}"
-
-glory summary = trial "Summarize"
-  tidings: findings
-```
-
-### Parallel Execution
-
-```prose
-# Functional
-parallel:
-  security = session "Check security"
-  perf = session "Check performance"
-  style = session "Check style"
-
-session "Synthesize review"
-  context: { security, perf, style }
-```
-
-```prose
-# Homeric
-host:
-  security = trial "Check security"
-  perf = trial "Check performance"
-  style = trial "Check style"
-
-trial "Synthesize review"
-  tidings: { security, perf, style }
-```
-
-### Loop with Condition
-
-```prose
-# Functional
-loop until **the code is bug-free** (max: 5):
-  session "Find and fix bugs"
-```
-
-```prose
-# Homeric
-ordeal until **the code is bug-free** (max: 5):
-  trial "Find and fix bugs"
-```
-
-### Error Handling
-
-```prose
-# Functional
-try:
-  session "Risky operation"
-catch as err:
-  session "Handle error"
-    context: err
-finally:
-  session "Cleanup"
-```
-
-```prose
-# Homeric
-venture:
-  trial "Risky operation"
-should ruin come as err:
-  trial "Handle error"
-    tidings: err
-in the end:
-  trial "Cleanup"
-```
-
-### Choice Block
-
-```prose
-# Functional
-choice **the severity level**:
-  option "Critical":
-    session "Escalate immediately"
-  option "Minor":
-    session "Log for later"
-```
-
-```prose
-# Homeric
-crossroads **the severity level**:
-  path "Critical":
-    trial "Escalate immediately"
-  path "Minor":
-    trial "Log for later"
-```
-
-### Conditionals
-
-```prose
-# Functional
-if **has security issues**:
-  session "Fix security"
-elif **has performance issues**:
-  session "Optimize"
-else:
-  session "Approve"
-```
-
-```prose
-# Homeric
-should **has security issues**:
-  trial "Fix security"
-or should **has performance issues**:
-  trial "Optimize"
-otherwise:
-  trial "Approve"
-```
-
-### Reusable Blocks
-
-```prose
-# Functional
-block review(topic):
-  session "Research {topic}"
-  session "Analyze {topic}"
-
-do review("quantum computing")
-```
-
-```prose
-# Homeric
-book review(topic):
-  trial "Research {topic}"
-  trial "Analyze {topic}"
-
-do review("quantum computing")
-```
-
-### Fixed Iteration
-
-```prose
-# Functional
-repeat 12:
-  session "Complete task"
-```
-
-```prose
-# Homeric
-12 labors:
-  trial "Complete task"
-```
-
-### Immutable Binding
-
-```prose
-# Functional
-const config = { model: "opus", retries: 3 }
-```
-
-```prose
-# 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
-
-| Term | Meaning | Used for |
-|------|---------|----------|
-| Kleos | Glory, fame that outlives you | `output` → `glory` |
-| Moira | Fate, one's allotted portion | `const` → `fate` |
-| Até | Divine ruin, blindness sent by gods | `catch` → `should ruin come` |
-| Nostos | The return journey | (not used, but could be `finally`) |
-| Xenia | Guest-friendship, hospitality | (not used) |
-| Muse | Divine inspiration | `model` → `muse` |
-
----
-
-## Alternatives Considered
-
-### For `hero` (agent)
-
-| Keyword | Rejected because |
-|---------|------------------|
-| `champion` | More medieval than Homeric |
-| `warrior` | Too martial, not all tasks are battles |
-| `wanderer` | Too passive |
-
-### For `trial` (session)
-
-| Keyword | Rejected because |
-|---------|------------------|
-| `labor` | Good but reserved for `repeat N labors` |
-| `quest` | More medieval/RPG |
-| `task` | Too plain |
-
-### For `host` (parallel)
-
-| Keyword | Rejected because |
-|---------|------------------|
-| `army` | Too specifically martial |
-| `fleet` | Only works for naval metaphors |
-| `phalanx` | Too technical |
-
----
-
-## 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.

package/extensions/open-prose/skills/prose/alts/kafka.md

@@ -1,373 +0,0 @@
----
-role: experimental
-summary: |
-  Kafka register for OpenProse—a bureaucratic/absurdist alternative keyword set.
-  Clerks, proceedings, petitions, and statutes. For benchmarking against the functional register.
-status: draft
-requires: prose.md
----
-
-# OpenProse Kafka 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 the works of Franz Kafka—The Trial, The Castle, "In the Penal Colony." Programs become proceedings. Agents become clerks. Everything is a process, and nobody quite knows the rules.
-
-## How to Use
-
-1. Load `prose.md` first (execution semantics)
-2. Load this file (keyword translations)
-3. When parsing `.prose` files, accept Kafka 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 a bureaucratic lens. (The irony is intentional.)
-
----
-
-## Complete Translation Map
-
-### Core Constructs
-
-| Functional | Kafka | Reference |
-|------------|-------|-----------|
-| `agent` | `clerk` | A functionary in the apparatus |
-| `session` | `proceeding` | An official action taken |
-| `parallel` | `departments` | Multiple bureaus acting simultaneously |
-| `block` | `regulation` | A codified procedure |
-
-### Composition & Binding
-
-| Functional | Kafka | Reference |
-|------------|-------|-----------|
-| `use` | `requisition` | Requesting from the archives |
-| `input` | `petition` | What is submitted for consideration |
-| `output` | `verdict` | What is returned by the apparatus |
-| `let` | `file` | Recording in the system |
-| `const` | `statute` | Unchangeable law |
-| `context` | `dossier` | The accumulated file on a case |
-
-### Control Flow
-
-| Functional | Kafka | Reference |
-|------------|-------|-----------|
-| `repeat N` | `N hearings` | Repeated appearances before the court |
-| `for...in` | `for each...in the matter of` | Bureaucratic iteration |
-| `loop` | `appeal` | Endless re-petition, the process continues |
-| `until` | `until` | Unchanged |
-| `while` | `while` | Unchanged |
-| `choice` | `tribunal` | Where judgment is rendered |
-| `option` | `ruling` | One possible judgment |
-| `if` | `in the event that` | Bureaucratic conditional |
-| `elif` | `or in the event that` | Continued conditional |
-| `else` | `otherwise` | Default ruling |
-
-### Error Handling
-
-| Functional | Kafka | Reference |
-|------------|-------|-----------|
-| `try` | `submit` | Submitting for processing |
-| `catch` | `should it be denied` | Rejection by the apparatus |
-| `finally` | `regardless` | What happens no matter the outcome |
-| `throw` | `reject` | The system refuses |
-| `retry` | `resubmit` | Try the process again |
-
-### Session Properties
-
-| Functional | Kafka | Reference |
-|------------|-------|-----------|
-| `prompt` | `directive` | Official instructions |
-| `model` | `authority` | Which level of the hierarchy |
-
-### Unchanged
-
-These keywords already work or are too functional to replace sensibly:
-
-- `**...**` discretion markers — the inscrutable judgment of the apparatus
-- `until`, `while` — already work
-- `map`, `filter`, `reduce`, `pmap` — pipeline operators
-- `max` — constraint modifier
-- `as` — aliasing
-- Model names: `sonnet`, `opus`, `haiku` — retained (or see "authority" above)
-
----
-
-## Side-by-Side Comparison
-
-### Simple Program
-
-```prose
-# Functional
-use "@alice/research" as research
-input topic: "What to investigate"
-
-agent helper:
-  model: sonnet
-
-let findings = session: helper
-  prompt: "Research {topic}"
-
-output summary = session "Summarize"
-  context: findings
-```
-
-```prose
-# Kafka
-requisition "@alice/research" as research
-petition topic: "What to investigate"
-
-clerk helper:
-  authority: sonnet
-
-file findings = proceeding: helper
-  directive: "Research {topic}"
-
-verdict summary = proceeding "Summarize"
-  dossier: findings
-```
-
-### Parallel Execution
-
-```prose
-# Functional
-parallel:
-  security = session "Check security"
-  perf = session "Check performance"
-  style = session "Check style"
-
-session "Synthesize review"
-  context: { security, perf, style }
-```
-
-```prose
-# Kafka
-departments:
-  security = proceeding "Check security"
-  perf = proceeding "Check performance"
-  style = proceeding "Check style"
-
-proceeding "Synthesize review"
-  dossier: { security, perf, style }
-```
-
-### Loop with Condition
-
-```prose
-# Functional
-loop until **the code is bug-free** (max: 5):
-  session "Find and fix bugs"
-```
-
-```prose
-# Kafka
-appeal until **the code is bug-free** (max: 5):
-  proceeding "Find and fix bugs"
-```
-
-### Error Handling
-
-```prose
-# Functional
-try:
-  session "Risky operation"
-catch as err:
-  session "Handle error"
-    context: err
-finally:
-  session "Cleanup"
-```
-
-```prose
-# Kafka
-submit:
-  proceeding "Risky operation"
-should it be denied as err:
-  proceeding "Handle error"
-    dossier: err
-regardless:
-  proceeding "Cleanup"
-```
-
-### Choice Block
-
-```prose
-# Functional
-choice **the severity level**:
-  option "Critical":
-    session "Escalate immediately"
-  option "Minor":
-    session "Log for later"
-```
-
-```prose
-# Kafka
-tribunal **the severity level**:
-  ruling "Critical":
-    proceeding "Escalate immediately"
-  ruling "Minor":
-    proceeding "Log for later"
-```
-
-### Conditionals
-
-```prose
-# Functional
-if **has security issues**:
-  session "Fix security"
-elif **has performance issues**:
-  session "Optimize"
-else:
-  session "Approve"
-```
-
-```prose
-# Kafka
-in the event that **has security issues**:
-  proceeding "Fix security"
-or in the event that **has performance issues**:
-  proceeding "Optimize"
-otherwise:
-  proceeding "Approve"
-```
-
-### Reusable Blocks
-
-```prose
-# Functional
-block review(topic):
-  session "Research {topic}"
-  session "Analyze {topic}"
-
-do review("quantum computing")
-```
-
-```prose
-# Kafka
-regulation review(topic):
-  proceeding "Research {topic}"
-  proceeding "Analyze {topic}"
-
-invoke review("quantum computing")
-```
-
-### Fixed Iteration
-
-```prose
-# Functional
-repeat 3:
-  session "Attempt connection"
-```
-
-```prose
-# Kafka
-3 hearings:
-  proceeding "Attempt connection"
-```
-
-### Immutable Binding
-
-```prose
-# Functional
-const config = { model: "opus", retries: 3 }
-```
-
-```prose
-# Kafka
-statute config = { authority: "opus", resubmit: 3 }
-```
-
----
-
-## The Case For Kafka
-
-1. **Darkly comic.** Programs-as-bureaucracy is funny and relatable.
-2. **Surprisingly apt.** Software often *is* an inscrutable apparatus.
-3. **Clean mappings.** Petition/verdict, file/dossier, clerk/proceeding all work well.
-4. **Appeal as loop.** The endless appeal process is a perfect metaphor for retry logic.
-5. **Cultural resonance.** "Kafkaesque" is a widely understood adjective.
-6. **Self-aware.** Using Kafka for a programming language acknowledges the absurdity.
-
-## The Case Against Kafka
-
-1. **Bleak tone.** Not everyone wants their programs to feel like The Trial.
-2. **Verbose keywords.** "In the event that" and "should it be denied" are long.
-3. **Anxiety-inducing.** May not be fun for users who find bureaucracy stressful.
-4. **Irony may not land.** Some users might take it literally and find it off-putting.
-
----
-
-## Key Kafka Concepts
-
-| Term | Meaning | Used for |
-|------|---------|----------|
-| The apparatus | The inscrutable system | The VM itself |
-| K. | The protagonist, never fully named | The user |
-| The Trial | Process without clear rules | Program execution |
-| The Castle | Unreachable authority | Higher-level systems |
-| Clerk | Functionary who processes | `agent` → `clerk` |
-| Proceeding | Official action | `session` → `proceeding` |
-| Dossier | Accumulated file | `context` → `dossier` |
-
----
-
-## Alternatives Considered
-
-### For `clerk` (agent)
-
-| Keyword | Rejected because |
-|---------|------------------|
-| `official` | Too generic |
-| `functionary` | Hard to spell |
-| `bureaucrat` | Too pejorative |
-| `advocate` | Too positive/helpful |
-
-### For `proceeding` (session)
-
-| Keyword | Rejected because |
-|---------|------------------|
-| `case` | Overloaded (switch case) |
-| `hearing` | Reserved for `repeat N hearings` |
-| `trial` | Used in Homeric register |
-| `process` | Too technical |
-
-### For `departments` (parallel)
-
-| Keyword | Rejected because |
-|---------|------------------|
-| `bureaus` | Good alternative, slightly less clear |
-| `offices` | Too mundane |
-| `ministries` | More Orwellian than Kafkaesque |
-
-### For `appeal` (loop)
-
-| Keyword | Rejected because |
-|---------|------------------|
-| `recourse` | Too legal-technical |
-| `petition` | Used for `input` |
-| `process` | Too generic |
-
----
-
-## Verdict
-
-Preserved for benchmarking. The Kafka register offers a darkly comic, self-aware framing that acknowledges the bureaucratic nature of software systems. The irony is the point.
-
-Best suited for:
-
-- Users with a sense of humor about software complexity
-- Programs that genuinely feel like navigating bureaucracy
-- Contexts where acknowledging absurdity is welcome
-
-Not recommended for:
-
-- Users who find bureaucratic metaphors stressful
-- Contexts requiring earnest, positive framing
-- Documentation that needs to feel approachable
-
----
-
-## Closing Note
-
-> "Someone must have slandered Josef K., for one morning, without having done anything wrong, he was arrested."
-> — *The Trial*
-
-In the Kafka register, your program is Josef K. The apparatus will process it. Whether it succeeds or fails, no one can say for certain. But the proceedings will continue.