create-githolon 0.45.0 → 0.47.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-githolon",
-  "version": "0.45.0",
+  "version": "0.47.0",
   "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/docs/08-births.md

@@ -76,3 +76,19 @@ relation models your policy; `creator` is the convention `birthChild` uses.)
 - **Don't hand-roll a second recipe *builder*** across your domains — keep the recipe inline (it's small)
   or share one tiny helper *in your own code*; the framework deliberately keeps **one** birth verb.
 - **Don't put a clock/random in the plan** — `bornAt` rides the payload (the timestamp doctrine).
+
+## Prove it — the 30-second loop
+
+Every compile validates your genesis recipe statically (child domain composed in the package? seed
+directive exists? recipe payload satisfies its schema? every plan returns an **array** of ops) and prints
+any problem as a `⚠ births` warning **containing the fix**. Then:
+
+```bash
+npx githolon compile      # ⚠ births warnings = fix these first (the message says how)
+npx githolon proof        # OFFLINE: drives your .births() directive on the real kernel, folds the
+                          # child through its OWN gate, reads the seed back, verify_chain green
+```
+
+A red proof names the exact genesis step the child's gate refused. The most common first-timer halt: a
+plan that returns a fluent builder — builders record themselves, so end the plan with `return [];`.
+A complete working two-domain births package to copy: `bench/scale/fixtures/estate-birth` (nomos2 repo).