Skip to content

Character Instances #13

Closed
Closed

Description

@omesser

Depends on: #7, #12

Why

A Character Instance is a Character plus a user-given name and a stable id. Instances
differ in personality and behavior, never in knowledge — Memory is shared.

Scope

  • Spawn an Instance from a Character, supplying a name; generate a stable id.
  • Dismiss an Instance.
  • Run several Instances at once, each with its own overlay window, position, and current
    Behavior.
  • List Instances and their names.

Acceptance criteria

  • Spawning asks for a name and generates an id.
  • Several Instances run at once without visible performance cost.
  • Instances are independently positionable and independently playing Behaviors.
  • A second Instance already knows the user, because Memory is shared.
  • Dismissing an Instance removes its overlay and leaves Memory untouched.

Tests

Engine tests cover per-Instance Behavior independence. Window management is manual.


Spec: docs/SPEC.md · migrated from docs/issues/0013-character-instances.md

Activity

  1. omesser commented on Sep 1, 2026

    @omesser
    OwnerAuthor

    Landed in #163. Two acceptance criteria did not, and both already have homes — recording that here so this issue reading COMPLETED does not imply otherwise.

    Not met

    "List Instances and their names." Roster::list() works and is tested, but nothing surfaces it: crates/mcp-server/src/main.rs still passes roster: &[] into the dispatch context, so list_instances answers empty. Owned by #15, whose scope names it outright — "Identity — list Character Instances and their names" — and by #18 for the menu. The startup line is the only listing today, and it goes to stderr.

    "A second Instance already knows the user, because Memory is shared." Memory is genuinely one file for every Instance now: Roster holds one Arc<MemoryManifest>, and memory::shared_path() points it at the same file the MCP server writes. But director::Context has no memory field and nothing reads Memory into the Character Prompt, so no buddy recites a fact — with one Instance or five. Owned by #144, which folds recall lines into ambient wakes and adds write-backs from turns.

    So the sharing is structural and the reciting is not built. README step 27 says so rather than claiming the buddy remembers.

    What did land

    Grab, Throw and Poke route to the Instance under the cursor, one gesture at a time; per-Instance Director, seed, wake clock and hit-test rectangle; art keyed by Character so two of one encode once; dismissal plumbed end to end, with no caller until #18.

    Verified by scripts/verify-overlay.sh (all machine checks, single Instance) and by hand with three Instances — two Character loads for three buddies, three sprites drawn at three positions, three Directors picking independently.

  2. added this to the V1 milestone on Sep 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions