@almadar/std 5.2.1 → 5.3.0

package/behaviors/exports/organisms/std-healthcare.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-healthcare",
+  "name": "HealthcareApp",
   "version": "1.0.0",
-  "description": "Healthcare organism. Composes molecules via compose: - stdList(Patient): patient registry with CRUD - stdList(Appointment): appointment management - stdWizard(IntakeForm): patient intake wizard - stdDetail(Prescription): prescription browse + view - stdDisplay(Dashboard): clinic dashboard KPIs",
   "orbitals": [
     {
       "name": "PatientOrbital",
@@ -469,6 +468,10 @@
                   [
                     "emit",
                     "PATIENT_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "Patient created successfully"
                   ]
                 ]
               }
@@ -638,6 +641,10 @@
                   [
                     "emit",
                     "PATIENT_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "Patient updated successfully"
                   ]
                 ]
               }
@@ -1074,6 +1081,10 @@
                   [
                     "emit",
                     "PATIENT_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "Patient deleted successfully"
                   ]
                 ]
               },
@@ -1596,6 +1607,10 @@
                   [
                     "emit",
                     "APPOINTMENT_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "Appointment created successfully"
                   ]
                 ]
               }
@@ -1765,6 +1780,10 @@
                   [
                     "emit",
                     "APPOINTMENT_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "Appointment updated successfully"
                   ]
                 ]
               }
@@ -2201,6 +2220,10 @@
                   [
                     "emit",
                     "APPOINTMENT_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "Appointment deleted successfully"
                   ]
                 ]
               },
@@ -4186,6 +4209,10 @@
                     "render-ui",
                     "modal",
                     null
+                  ],
+                  [
+                    "notify",
+                    "Prescription created successfully"
                   ]
                 ]
               }
@@ -5959,5 +5986,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Healthcare organism. Composes molecules via compose: - stdList(Patient): patient registry with CRUD - stdList(Appointment): appointment management - stdWizard(IntakeForm): patient intake wizard - stdDetail(Prescription): prescription browse + view - stdDisplay(Dashboard): clinic dashboard KPIs Cross-orbital connections: - INTAKE_COMPLETE: IntakeFormWizard -> PatientBrowse - PRESCRIBE: AppointmentBrowse -> PrescriptionBrowse (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}

package/behaviors/exports/organisms/std-helpdesk.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-helpdesk",
+  "name": "Helpdesk",
   "version": "1.0.0",
-  "description": "Helpdesk organism. Composes molecules via compose: - stdList(Ticket): CRUD list of support tickets - stdMessaging(Response): messaging thread for ticket responses - stdDisplay(SupportMetrics): read-only metrics dashboard",
   "orbitals": [
     {
       "name": "TicketOrbital",
@@ -463,6 +462,10 @@
                   [
                     "emit",
                     "TICKET_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "Ticket created successfully"
                   ]
                 ]
               }
@@ -631,6 +634,10 @@
                   [
                     "emit",
                     "TICKET_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "Ticket updated successfully"
                   ]
                 ]
               }
@@ -1050,6 +1057,10 @@
                   [
                     "emit",
                     "TICKET_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "Ticket deleted successfully"
                   ]
                 ]
               },
@@ -1474,6 +1485,10 @@
                     "render-ui",
                     "modal",
                     null
+                  ],
+                  [
+                    "notify",
+                    "Response created successfully"
                   ]
                 ]
               }
@@ -3303,5 +3318,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Helpdesk organism. Composes molecules via compose: - stdList(Ticket): CRUD list of support tickets - stdMessaging(Response): messaging thread for ticket responses - stdDisplay(SupportMetrics): read-only metrics dashboard Pages: /tickets (initial), /responses, /metrics Connections: ASSIGN (tickets->responses), RESOLVE (responses->metrics) (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}

package/behaviors/exports/organisms/std-hr-portal.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-hr-portal",
+  "name": "HRPortal",
   "version": "1.0.0",
-  "description": "HR portal organism. Composes molecules via compose: - stdList(Employee): CRUD list of employees - stdWizard(Onboarding): multi-step onboarding wizard - stdList(TimeOff): CRUD list of time-off requests - stdDisplay(OrgChart): read-only org chart dashboard",
   "orbitals": [
     {
       "name": "EmployeeOrbital",
@@ -440,6 +439,10 @@
                   [
                     "emit",
                     "EMPLOYEE_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "Employee created successfully"
                   ]
                 ]
               }
@@ -608,6 +611,10 @@
                   [
                     "emit",
                     "EMPLOYEE_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "Employee updated successfully"
                   ]
                 ]
               }
@@ -1027,6 +1034,10 @@
                   [
                     "emit",
                     "EMPLOYEE_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "Employee deleted successfully"
                   ]
                 ]
               },
@@ -2945,6 +2956,10 @@
                   [
                     "emit",
                     "TIME_OFF_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "TimeOff created successfully"
                   ]
                 ]
               }
@@ -3113,6 +3128,10 @@
                   [
                     "emit",
                     "TIME_OFF_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "TimeOff updated successfully"
                   ]
                 ]
               }
@@ -3532,6 +3551,10 @@
                   [
                     "emit",
                     "TIME_OFF_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "TimeOff deleted successfully"
                   ]
                 ]
               },
@@ -5198,5 +5221,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "HR portal organism. Composes molecules via compose: - stdList(Employee): CRUD list of employees - stdWizard(Onboarding): multi-step onboarding wizard - stdList(TimeOff): CRUD list of time-off requests - stdDisplay(OrgChart): read-only org chart dashboard Pages: /employees (initial), /onboarding, /timeoff, /org-chart Connections: ONBOARD (employees->onboarding), APPROVE_LEAVE (timeoff->orgchart) (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}

package/behaviors/exports/organisms/std-iot-dashboard.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-iot-dashboard",
+  "name": "IoT Dashboard",
   "version": "1.0.0",
-  "description": "IoT dashboard organism. Composes: stdDisplay(SensorReading) + stdList(Device) + stdCircuitBreaker(DeviceAlert)",
   "orbitals": [
     {
       "name": "SensorReadingOrbital",
@@ -2091,6 +2090,10 @@
                   [
                     "emit",
                     "DEVICE_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "Device created successfully"
                   ]
                 ]
               }
@@ -2258,6 +2261,10 @@
                   [
                     "emit",
                     "DEVICE_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "Device updated successfully"
                   ]
                 ]
               }
@@ -2660,6 +2667,10 @@
                   [
                     "emit",
                     "DEVICE_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "Device deleted successfully"
                   ]
                 ]
               },
@@ -3893,5 +3904,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "IoT dashboard organism. Composes: stdDisplay(SensorReading) + stdList(Device) + stdCircuitBreaker(DeviceAlert) Pages: /sensors (initial), /devices, /alerts (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}

package/behaviors/exports/organisms/std-lms.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-lms",
+  "name": "LMS",
   "version": "1.0.0",
-  "description": "Learning management system organism. Composes molecules via compose: - stdList(Course): CRUD list of courses - stdWizard(Enrollment): multi-step enrollment wizard - stdDisplay(Progress): read-only progress dashboard",
   "orbitals": [
     {
       "name": "CourseOrbital",
@@ -438,6 +437,10 @@
                   [
                     "emit",
                     "COURSE_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "Course created successfully"
                   ]
                 ]
               }
@@ -606,6 +609,10 @@
                   [
                     "emit",
                     "COURSE_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "Course updated successfully"
                   ]
                 ]
               }
@@ -1025,6 +1032,10 @@
                   [
                     "emit",
                     "COURSE_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "Course deleted successfully"
                   ]
                 ]
               },
@@ -3864,5 +3875,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Learning management system organism. Composes molecules via compose: - stdList(Course): CRUD list of courses - stdWizard(Enrollment): multi-step enrollment wizard - stdDisplay(Progress): read-only progress dashboard Pages: /courses (initial), /enroll, /progress Connections: ENROLL (courses->enrollment), COMPLETE_LESSON (enrollment->progress) (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}

package/behaviors/exports/organisms/std-logic-training.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-logic-training",
+  "name": "Logic Training",
   "version": "1.0.0",
-  "description": "Logic training organism. Composes: stdDebuggerGame(DebugChallenge) + stdNegotiatorGame(NegotiateChallenge) + stdScoreBoard(TrainingScore)",
   "orbitals": [
     {
       "name": "DebugChallengeOrbital",
@@ -749,5 +748,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Logic training organism. Composes: stdDebuggerGame(DebugChallenge) + stdNegotiatorGame(NegotiateChallenge)         + stdScoreBoard(TrainingScore) Pages: /debugger (initial), /negotiator, /scores (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}

package/behaviors/exports/organisms/std-platformer-app.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-platformer-app",
+  "name": "Platformer App",
   "version": "1.0.0",
-  "description": "Platformer game organism. Composes: stdPlatformerGame(PlatLevel) + stdScoreBoard(PlatScore) + stdInventory(Collectible)",
   "orbitals": [
     {
       "name": "PlatLevelOrbital",
@@ -1260,6 +1259,10 @@
                   [
                     "emit",
                     "ITEM_ADDED"
+                  ],
+                  [
+                    "notify",
+                    "Collectible created successfully"
                   ]
                 ]
               }
@@ -1441,6 +1444,10 @@
                   [
                     "emit",
                     "ITEM_USED"
+                  ],
+                  [
+                    "notify",
+                    "Collectible updated successfully"
                   ]
                 ]
               }
@@ -1603,6 +1610,10 @@
                   [
                     "ref",
                     "Collectible"
+                  ],
+                  [
+                    "notify",
+                    "Collectible deleted successfully"
                   ]
                 ]
               },
@@ -1663,5 +1674,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Platformer game organism. Composes: stdPlatformerGame(PlatLevel) + stdScoreBoard(PlatScore) + stdInventory(Collectible) Pages: /game (initial), /scores, /collectibles (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}

package/behaviors/exports/organisms/std-project-manager.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-project-manager",
+  "name": "ProjectManagerApp",
   "version": "1.0.0",
-  "description": "Project management organism. Composes molecules via compose: - stdList(Task): task management with CRUD - stdList(Sprint): sprint management with CRUD - stdDisplay(Burndown): burndown chart dashboard",
   "orbitals": [
     {
       "name": "TaskOrbital",
@@ -472,6 +471,10 @@
                   [
                     "emit",
                     "TASK_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "Task created successfully"
                   ]
                 ]
               }
@@ -642,6 +645,10 @@
                   [
                     "emit",
                     "TASK_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "Task updated successfully"
                   ]
                 ]
               }
@@ -1095,6 +1102,10 @@
                   [
                     "emit",
                     "TASK_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "Task deleted successfully"
                   ]
                 ]
               },
@@ -1620,6 +1631,10 @@
                   [
                     "emit",
                     "SPRINT_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "Sprint created successfully"
                   ]
                 ]
               }
@@ -1789,6 +1804,10 @@
                   [
                     "emit",
                     "SPRINT_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "Sprint updated successfully"
                   ]
                 ]
               }
@@ -2225,6 +2244,10 @@
                   [
                     "emit",
                     "SPRINT_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "Sprint deleted successfully"
                   ]
                 ]
               },
@@ -3781,5 +3804,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Project management organism. Composes molecules via compose: - stdList(Task): task management with CRUD - stdList(Sprint): sprint management with CRUD - stdDisplay(Burndown): burndown chart dashboard Cross-orbital connections: - ASSIGN_TASK: SprintBrowse -> TaskBrowse - COMPLETE_SPRINT: SprintBrowse -> BurndownDisplay (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}

package/behaviors/exports/organisms/std-puzzle-app.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-puzzle-app",
+  "name": "Puzzle App",
   "version": "1.0.0",
-  "description": "Puzzle game organism. Composes: stdPuzzleGame(PuzzleLevel) + stdScoreBoard(PuzzleScore)",
   "orbitals": [
     {
       "name": "PuzzleLevelOrbital",
@@ -885,5 +884,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Puzzle game organism. Composes: stdPuzzleGame(PuzzleLevel) + stdScoreBoard(PuzzleScore) Pages: /puzzle (initial), /scores (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}

package/behaviors/exports/organisms/std-realtime-chat.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-realtime-chat",
+  "name": "Realtime Chat",
   "version": "1.0.0",
-  "description": "Realtime chat organism. Composes: stdMessaging(ChatMessage) + stdList(Channel) + stdDisplay(OnlineUser)",
   "orbitals": [
     {
       "name": "ChatMessageOrbital",
@@ -344,6 +343,10 @@
                     "render-ui",
                     "modal",
                     null
+                  ],
+                  [
+                    "notify",
+                    "ChatMessage created successfully"
                   ]
                 ]
               }
@@ -1006,6 +1009,10 @@
                   [
                     "emit",
                     "CHANNEL_CREATED"
+                  ],
+                  [
+                    "notify",
+                    "Channel created successfully"
                   ]
                 ]
               }
@@ -1173,6 +1180,10 @@
                   [
                     "emit",
                     "CHANNEL_UPDATED"
+                  ],
+                  [
+                    "notify",
+                    "Channel updated successfully"
                   ]
                 ]
               }
@@ -1575,6 +1586,10 @@
                   [
                     "emit",
                     "CHANNEL_DELETED"
+                  ],
+                  [
+                    "notify",
+                    "Channel deleted successfully"
                   ]
                 ]
               },
@@ -3403,5 +3418,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "Realtime chat organism. Composes: stdMessaging(ChatMessage) + stdList(Channel) + stdDisplay(OnlineUser) Pages: /chat (initial), /channels, /online (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}

package/behaviors/exports/organisms/std-rpg-game.orb

@@ -1,7 +1,6 @@
 {
-  "name": "std-rpg-game",
+  "name": "RPG Game",
   "version": "1.0.0",
-  "description": "RPG game organism. Composes: stdTurnBasedBattle(BattleState) + stdOverworld(WorldZone) + stdInventory(RpgItem) + stdQuest(Mission)",
   "orbitals": [
     {
       "name": "BattleStateOrbital",
@@ -1555,6 +1554,10 @@
                   [
                     "emit",
                     "ITEM_ADDED"
+                  ],
+                  [
+                    "notify",
+                    "RpgItem created successfully"
                   ]
                 ]
               }
@@ -1736,6 +1739,10 @@
                   [
                     "emit",
                     "ITEM_USED"
+                  ],
+                  [
+                    "notify",
+                    "RpgItem updated successfully"
                   ]
                 ]
               }
@@ -1898,6 +1905,10 @@
                   [
                     "ref",
                     "RpgItem"
+                  ],
+                  [
+                    "notify",
+                    "RpgItem deleted successfully"
                   ]
                 ]
               },
@@ -2644,6 +2655,10 @@
                         }
                       ]
                     }
+                  ],
+                  [
+                    "notify",
+                    "Mission updated successfully"
                   ]
                 ]
               },
@@ -3278,5 +3293,6 @@
         }
       ]
     }
-  ]
-}
+  ],
+  "description": "RPG game organism. Composes: stdTurnBasedBattle(BattleState) + stdOverworld(WorldZone)         + stdInventory(RpgItem) + stdQuest(Mission) Pages: /battle, /world (initial), /inventory, /quests Connections: ENCOUNTER_STARTED (world->battle), LOOT_DROPPED (battle->inventory),              QUEST_ACCEPTED (world->quests) (2026-04-08). The canonical source for std behaviors is now the registry `.orb` file at `packages/almadar-std/behaviors/registry/<level>/<name>.orb`, which is generated from this TS source by `tools/almadar-behavior-ts-to-orb/` and consumed by the compiler's embedded loader. Consumers should import behaviors via `.lolo`/`.orb` `uses` declarations and reference them as `Alias.entity` / `Alias.traits.X` / `Alias.pages.X`, applying overrides at the call site (`linkedEntity`, `name`, `events`, `effects`, `listens`, `emitsScope`). The TS `*Params` interface and the exported factory functions remain ONLY as the authoring path for the converter; they are NOT a stable public API and may change without notice. See `docs/Almadar_Orb_Behaviors.md` for the orbital-as-function model and `docs/LOLO_Gaps.md` for the migration plan."
+}