create-githolon 0.100.6 → 0.101.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-githolon",
-  "version": "0.100.6",
+  "version": "0.101.1",
   "type": "module",
   "description": "Scaffold a Nomos domain package: the starter domain + compile config + live e2e. `npm create githolon my-app`.",
   "license": "SEE LICENSE IN LICENSE.md",

package/template/README.md

@@ -12,19 +12,12 @@ The starter in [`domains/todo.ts`](domains/todo.ts) gives a todo list its own du
 
 ```ts
 export const TodoList = aggregate("TodoList", {
-  reference: t.string().merge(Lww),
-  title: t.string().merge(Lww),
+  reference: t.string({ nonempty: true }).fromBirth(),
+  title: t.string({ nonempty: true }).fromBirth(),
 });
 
 export const todoList = birth(TodoList, {
-  payload: z.object({
-    reference: z.string().min(1),
-    title: z.string().min(1),
-  }),
-  key: (facts) => facts.reference,
-  plan: (list, facts) => list
-    .set("reference", facts.reference)
-    .set("title", facts.title),
+  key: "reference",
 });
 ```
 
@@ -51,7 +44,10 @@ npx githolon proof
 
 `compile` emits the law, typed client, and a proof generated from this domain. `proof` drives the real engine locally, births the list, discards its resident copy, restores it from durable custody, verifies the full history again, and reads the business root back.
 
-Make it yours by renaming `TodoList`, changing its fields, and changing the birth payload. Keep the rule: application code supplies business facts; Nomos owns the machinery that makes those facts durable and trustworthy.
+Make it yours by renaming `TodoList` and changing its fields. `.fromBirth()` means the fact is required to
+begin that durable life; its field rule is also the birth validation and generated input type. Nomos derives
+the initial write. Keep the rule: application code supplies business facts; Nomos owns the machinery that
+makes those facts durable and trustworthy.
 
 Useful files:
 

package/template/domains/todo.ts

@@ -4,22 +4,15 @@
  * The app supplies business facts. Nomos gives the aggregate a durable life and owns identity,
  * authorship, local execution, synchronisation, persistence, provenance, and recovery beneath it.
  */
-import { Lww, aggregate, birth, t, z } from "@githolon/dsl";
+import { aggregate, birth, t } from "@githolon/dsl";
 
 export const TodoList = aggregate("TodoList", {
   /** A stable business key the caller already knows. */
-  reference: t.string().merge(Lww),
-  title: t.string().merge(Lww),
-});
+  reference: t.string({ nonempty: true }).fromBirth(),
+  title: t.string({ nonempty: true }).fromBirth(),
+}).owned();
 
 /** The one public creation idea: give a todo list its own durable life. */
 export const todoList = birth(TodoList, {
-  payload: z.object({
-    reference: z.string().min(1),
-    title: z.string().min(1),
-  }),
-  key: (facts) => facts.reference,
-  plan: (list, facts) => list
-    .set("reference", facts.reference)
-    .set("title", facts.title),
+  key: "reference",
 });

package/template/package.json

@@ -11,8 +11,7 @@
   },
   "dependencies": {
     "@githolon/dsl": "^__NOMOS_VERSION__",
-    "@githolon/client": "^__NOMOS_VERSION__",
-    "zod": "^4.4.3"
+    "@githolon/client": "^__NOMOS_VERSION__"
   },
   "devDependencies": {
     "githolon": "^__NOMOS_VERSION__",