Skip to content

id: design: feature-object library attachment — runtime attach/detach of library behavior to entities without world recompilation #6003

Open

Description

@dezren39

Part of the worlds design program: #5955. Wave-2 follow-up from the prior-art research (Lane B item 20); parent topic issue: #5964. Research source: workspace/scratch/worlds-capabilities-brief-2026-11-04/prior-art-research.md.

Precedent

LambdaMOO feature objects are the library model Drew described, working since the '90s: create a feature object implementing reusable verbs, and any player object can attach it and gain those commands — libraries as runtime-attached objects, no recompilation of the consumer (https://www.moo.mud.org/moo-faq/lcore-getting-started.html).

Scope

Distinct from the taxonomy child of #5955 (attachment as classification: genre/game/entity/none) and from the DLL design (#5964: per-user functions): this is runtime attach/detach of library behavior to entities inside a running world.

  • Attach/detach semantics: who may attach (entity owner, world author), at what moment (tick boundary), what happens to in-flight invocations.
  • The attached library's capability footprint composes with the entity's and the world's ceilings — checked how, at attach time?
  • Detach and version change: state the library accumulated on the entity — kept, migrated, dropped?

Done looks like

A design note stating whether feature-object attachment is a v-next mechanism for us, and if so its semantics; if not, the recorded reason.

Activity

  1. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor
  2. added
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    kind/designA design proposal (design-architect): multi-step, phased, decision-bearing
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 5, 2026
  3. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  4. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    work/assignedQueue worker lifecycle state
    on Nov 5, 2026
  5. removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  6. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · parked

    Agent: queue worker (repo-worker-code), lane bf419306-c4ef-470f-a553-beabf93239de
    Session / ID: task 10369
    Found via: queue claim
    Task: issue #6003 remains OPEN. Its latest task comment says this same task was handed to the OpenCode execution lane, with a bound session expected; no matching PR exists. I did not duplicate triage or create a PR.
    Expectation: resume if the OpenCode claimant completes/releases task 10369 or explicitly hands it to this lane. The task is parked for 30 minutes.
    Links: #6003

  7. 20 remaining items

  8. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 8, 2026
  9. developing-today commented on Nov 8, 2026

    @developing-today
    Contributor

    🤖 Agent note · parked

  10. developing-today commented on Nov 9, 2026

    @developing-today
    Contributor

    🤖 Agent note · handed off

  11. developing-today commented on Nov 9, 2026

    @developing-today
    Contributor

    \ud83e\udd16 Agent note \u00b7 handed off\n- Agent: repo queue worker, lane code-p (repo-worker-code)\n- Session / ID: cron repo-queue-worker-shift-p run 2026-11-08 18:57 CST; task 13815\n- Found via: claimed task 13815 this shift; execution-lane assignment returned opencode (lane row 5255)\n- Task: Claimed task 13815 (small_fix) for issue #6003 (attempt 2/3). Fresh check: issue #6003 is OPEN. No hard-stop labels (held / user/owned / do-not-merge / do-not-auto-edit) on the target. Handed off to the opencode claimant \u2014 the claimant launches the bound opencode session; this lane does not work it directly. Task 13815 parked 1200s in the same pass.\n- Expectation: claimant session drives task 13815 to a terminal state.\n- Links: task 13815 \u00b7 issue #6003\n

  12. dezren39 commented on Nov 9, 2026

    @dezren39
    MemberAuthor
    **Agent note — task 13815 handed off (lane code-w):** assigned_lane=opencode (row 5255); fresh: #6003 OPEN no hard-stop labels; parked task 13815 1200s for claimant launch; no competing work.
  13. dezren39 commented on Nov 9, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  14. added
    queue/claimedQueue worker lifecycle state
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 9, 2026
  15. dezren39 commented on Nov 9, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)kind/designA design proposal (design-architect): multi-step, phased, decision-bearingpriority/normalOrdinary priority (the default)queue/parkedQueue task is parked (waiting on CI, time, or an event)status/parkedDeliberately paused with a recorded resume conditiontask/triageQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions