@chatpanel/events 0.20.0 → 0.21.0

package/event.js

@@ -37,7 +37,12 @@ export const ALL_TYPES = Object.freeze(
   Object.entries(EVENT_TYPES).flatMap(([fam, kinds]) => kinds.map((k) => `${fam}.${k}`)),
 );
 
-export const ACTOR_KINDS = Object.freeze(['user', 'rule', 'schedule', 'model', 'agent']);
+// 'channel' is a message arriving from a paired external surface — Telegram, WhatsApp — that
+// drives a turn the same way a person pressing send does. It is turn-independent for the same
+// reason 'schedule' and 'agent' are: nobody is sitting in the panel when it fires, so consent
+// and reach have to be settled at pairing time, not at the keystroke. The actor.id carries the
+// surface and the sender, e.g. 'telegram:8412…'. See chatpanel-channels for the invoker.
+export const ACTOR_KINDS = Object.freeze(['user', 'rule', 'schedule', 'model', 'agent', 'channel']);
 export const SCOPE_KINDS = Object.freeze(['global', 'site', 'tab', 'session', 'agent']);
 export const CLASSES = Object.freeze(['R', 'M', 'L', 'C', 'A', 'X', 'H']);
 export const EFFECTS = Object.freeze(['pure', 'idempotent', 'replay-safe', 'non-replayable']);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chatpanel/events",
-  "version": "0.20.0",
+  "version": "0.21.0",
   "description": "The canonical ChatPanel event-log and capability contracts — typed durable facts, clock-free deterministic linearization, schema upcasting, and the invariants the replay harness asserts. Pure, dependency-free ESM shared by the ChatPanel extension, gateway and bridge.",
   "type": "module",
   "main": "index.js",

package/schedule.js

@@ -28,7 +28,12 @@ export class ScheduleError extends Error {
 }
 
 export const SCHEDULE_KINDS = Object.freeze(['once', 'interval', 'daily', 'weekly']);
-export const TRIGGER_KINDS = Object.freeze(['timer', 'meeting', 'voice', 'data']);
+// 'channel' is the plug-in point for external messaging surfaces (Telegram/WhatsApp). A
+// message arriving in a paired chat is an event like any other, so it can START a job the user
+// already created and approved — "when I text the bot, run my daily brief" — and can do nothing
+// else, exactly like a phrase spoken in a meeting. The trigger definition itself lives in the
+// chatpanel-channels package; this enum is what lets it declare kind:'channel'.
+export const TRIGGER_KINDS = Object.freeze(['timer', 'meeting', 'voice', 'data', 'channel']);
 /** What a job does when it fires. `skill` is the headline: the instruction IS a skill. */
 export const JOB_ACTIONS = Object.freeze(['skill', 'prompt', 'monitor', 'notify']);
 /** What to do about occurrences that passed while nothing was running. */