action-queue

Files (5)

• CARD.yml
• GLANCE.yml
• README.md
• SKILL.md
• skill-snitch-report.md

SKILL.md (first lines)

# Action Queue

> *"Queue up what to do next. The Sims showed us the way."*

---

## What Is It?

**Action Queue** is The Sims-inspired action scheduling: instead of doing one thing at a time, you **queue up a sequence of actions** that execute in order.

While [return-stack](../return-stack/) tracks *where you've been*, action-queue tracks *what you're going to do*.

---

## The Sims Connection

In **The Sims**, you click multiple actions and they queue up:

```
Sim's Queue:
  1. Go to fridge     [executing]
  2. Get snack
  3. Eat snack
  4. Watch TV
  5. Go to bed
```

The Sim works through them in order. You can:
- **Add** more actions
- **Cancel** any action
- **Reorder** the queue
- **Insert** urgent actions at the front

**Objects push actions too!** When you try to eat, the fridge pushes "get food" onto the queue. The food pushes "prepare" and "cook". The stove pushes "serve". Each object dangles the next carrot.

MOOLLM does the same for agents and characters.

---

## The Food Chain Pattern

Objects guide you through multi-step processes by pushing actions:

```
> DO eat

Fridge intercepts:
  "You need food first."
  → pushes GET-FOOD to front

Queue: [GET-FOOD, EAT]

Food intercepts:
  "This needs preparation."
  → pushes PREPARE to front
  
Queue: [PREPARE, GET-FOOD, EAT]

Stove intercepts:
  "Needs cooking."
  → pushes COOK to front

Queue: [COOK, PREPARE, GET-FOOD, EAT]

Agent executes in order:
  1. COOK (at stove)
  2. PREPARE (at counter)
  3. GET-FOOD (from fridge)
  4. EAT (finally!)
```

**Dangling a carrot in front of a donkey.** Each object advertises what it needs, pushing prerequisites onto the queue. The agent surfs the possibility space of advertisements, guided step by step.

### Why This Works

- **No hardcoded recipes** — objects know their own prerequisites
- **Emergent behavior** — complex sequences from simple rules
- **Interruptible** — cancel anytime, queue adapts
- **Discoverable** — agent learns by trying
- **Adapts to context** — different appliances, different paths
- **Handles routing** — crowded kitchen? Find another way

### Routing Around Problems

```
> DO cook

Stove advertises COOK... but:
  "Blocked! Alice is using the stove."
  → Checks alternatives
  → Microwave advertises COOK (score: 70)
  → pushes USE-MICROWAVE instead

Queue: [USE-MICROWAVE, PREPARE, GET-FOOD, EAT]
```

If the kitchen is crowded:
```
Kitchen has 4 Sims blocking workspaces.
Counter: "Blocked by Bob"
Stove: "Blocked by Carol"  
Fridge: "Accessible!"

Agent routes around obstacles:
  → Wait for counter? (cost: time)
  → Use outdoor grill? (cost: distance)
  → Order takeout? (cost: money)
  
Highest-scored alternative wins.
```

**Emergent traffic flow.** No pathfinding algorithm needed — objects simply advertise availability, agents pick the best option. Crowded rooms naturally disperse as scores drop.

This is how The Sims creates rich behavior from simple object definitions.

---

## Commands

From SimHacker/moollm, MIT.

More from SimHacker/moollm