@hogsend/core 0.14.0 → 0.17.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hogsend/core",
-  "version": "0.14.0",
+  "version": "0.17.0",
   "type": "module",
   "license": "MIT",
   "repository": {
@@ -32,7 +32,7 @@
     "drizzle-orm": "^0.45.2",
     "iana-db-timezones": "^0.3.0",
     "zod": "^4.4.3",
-    "@hogsend/db": "^0.14.0"
+    "@hogsend/db": "^0.17.0"
   },
   "devDependencies": {
     "@types/node": "latest",

package/src/types/journey.ts

@@ -1,6 +1,44 @@
+import type { CriteriaBuilder } from "../conditions/builder.js";
 import type { DurationObject } from "../duration.js";
 import type { PropertyCondition } from "./conditions.js";
 
+/**
+ * The builder surface available to a journey `where` function — property
+ * terminals only. Trigger/exit conditions evaluate against the TRIGGERING
+ * event's properties; counts, windows, and engagement belong in bucket
+ * criteria or `ctx.history`, not here.
+ */
+export type JourneyWhereBuilder = Pick<CriteriaBuilder, "prop">;
+
+/**
+ * Authoring form of `trigger.where` / `exitOn[].where`: the stored data form
+ * (`PropertyCondition[]`), or a builder function resolved ONCE at
+ * `defineJourney` time into the byte-identical POJOs —
+ * `where: (b) => b.prop("score").lte(6)`. The function never executes
+ * per-user, so conditions stay introspectable data everywhere downstream
+ * (registry, admin routes, Studio).
+ */
+export type JourneyWhere =
+  | PropertyCondition[]
+  | ((b: JourneyWhereBuilder) => PropertyCondition | PropertyCondition[]);
+
+/**
+ * What `defineJourney` ACCEPTS. The stored {@link JourneyMeta} (registry,
+ * schema, HTTP) keeps plain `PropertyCondition[]` — only the authoring
+ * surface widens.
+ */
+export interface JourneyMetaInput
+  extends Omit<JourneyMeta, "trigger" | "exitOn"> {
+  trigger: {
+    event: string;
+    where?: JourneyWhere;
+  };
+  exitOn?: Array<{
+    event: string;
+    where?: JourneyWhere;
+  }>;
+}
+
 export interface JourneyMeta {
   id: string;
   name: string;