create-githolon 0.108.7 → 0.110.1

package/index.mjs

@@ -17,7 +17,7 @@ var NOMOS_VERSION = (() => {
 var args = process.argv.slice(2);
 if (args.includes("-h") || args.includes("--help")) {
   process.stdout.write(
-    "create-githolon \u2014 scaffold a Nomos business-law package\n\nUsage:\n  npm create githolon <dir>        (or: npx create-githolon <dir>)\n\nScaffolds one durable business root, one atomic multi-aggregate intent,\none generated application, and a one-page explanation into <dir>\n(default: my-holon-app). The generated\nproof exercises the real local engine.\n\nFlags:\n  --no-git    skip git init\n"
+    "create-githolon \u2014 scaffold a Nomos business-law package\n\nUsage:\n  npm create githolon <dir>        (or: npx create-githolon <dir>)\n\nScaffolds one durable business root, one atomic multi-aggregate intent,\none generated application, and a one-page explanation into <dir>\n(default: my-holon-app). Compile emits the law and application.\n\nFlags:\n  --no-git    skip git init\n"
   );
   process.exit(0);
 }
@@ -67,8 +67,8 @@ Nomos in one page: ${path.join(rel, "README.md")}
 Next:
   cd ${rel}
   npm install
-  npm run compile             # law + generated business application + proof
-  npm run proof               # drives the business language in the real local engine
+  npm run compile             # law + generated business application
+  npm run typecheck           # check the authored TypeScript
 
 The starter exposes one intent: commissionAsset(businessFacts).
 Identity, authorship, persistence, synchronisation, provenance, and recovery stay underneath it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-githolon",
-  "version": "0.108.7",
+  "version": "0.110.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/CLAUDE.md

@@ -16,16 +16,18 @@ Model the business language. Do not recreate Nomos as application infrastructure
 
 ```bash
 npm run compile
-npm run proof
+npm run typecheck
 # After the first deployed model, prove the candidate over copied real custody too:
-npx githolon proof --upgrade
+npx githolon test
 ```
 
-`compile` is the evolution gate. `proof` exercises the emitted candidate in the real local kernel, including
-cold custody restore. `proof --upgrade` resolves the workspace already bound in `nomos.project.ts`, copies
-its custody into a disposable local kernel, replays the candidate over the exact history, promotes it only
-in that copy, and cold-opens the result. If history changes meaning, it stops for an explicit
-`--acceptance-reason`; never invent one. Never make deployment the first place a candidate law is executed.
+`compile` is the evolution gate. `typecheck` checks the authored TypeScript.
+`githolon test` resolves the workspace already bound in `nomos.project.ts`, copies
+its custody into a disposable local kernel, verifies the existing chain under its recorded eras, derives
+the candidate's current-frontier transition, promotes it only in that copy, and cold-opens the result.
+Stable-id retirements, retypes, or rebinds stop for an explicit `--acceptance-reason`; never invent one.
+Whole-history simulation is an explicitly requested counterfactual and is never an adoption gate. Never
+make deployment the first place a candidate law is executed.
 
 If either command exposes framework implementation machinery, treat that as a Nomos defect rather than
 teaching the application to handle it.

package/template/README.md

@@ -56,12 +56,10 @@ The development loop is one path:
 ```bash
 npm install
 npm run compile
-npm run proof
+npm run typecheck
 ```
 
-`compile` emits the law and generated business application. `proof` drives the same business language in the
-real local engine, discards resident state, restores it from durable custody, verifies its history, and reads
-the business world back.
+`compile` emits the law and generated business application. `typecheck` checks the authored TypeScript.
 
 From the second compile onward, `compile` also compares the candidate with the committed
 `nomos.identity.usda`. Additions and inferred renames pass automatically. A removal, contract change, or
@@ -82,18 +80,19 @@ export const evolveAssetName = evolution(Asset, "name")
 ```
 
 These files are discovered by compile and editor checks but are never loaded as application plans. Keep the
-updated identity file beside the domain source, run `proof`, and deploy only those locally proven bytes.
+updated identity file beside the domain source, then compile and typecheck before deployment.
 
 Before upgrading an existing application, run the history-shaped proof as well:
 
 ```bash
-npx githolon proof --upgrade
+npx githolon test
 ```
 
 It uses the workspace binding in `nomos.project.ts` (or accepts a workspace/local-ledger argument), copies
-that custody into the local kernel, exercises the candidate against its exact history, promotes only in the
-copy, and proves a cold restart. The source is never modified. If the candidate deliberately changes an old
-business outcome, the command names the differences and requires an accountable `--acceptance-reason`.
+that custody into the local kernel, verifies the chain under its recorded eras, derives the candidate's
+current-frontier transition, promotes only in the copy, and proves a cold restart. The source is never
+modified. Stable-id retirements, retypes, or rebinds require an accountable `--acceptance-reason`.
+Whole-history simulation is available only as an explicit counterfactual and never gates adoption.
 
 Useful files:
 
@@ -102,7 +101,7 @@ Useful files:
 - [`nomos.project.ts`](nomos.project.ts): typed business-law authoring input; it emits the readable USDA law closure and its `.law.usdz` package;
 - [`nomos.application.ts`](nomos.application.ts): application-composition authoring input; only the emitted `.application.usda` travels;
 - `build/application/__APP_DART_NAME___application/`: the sole Flutter application dependency;
-- `build/__APP_NAME__.proof.mts`: the generated local proof.
+- `build/__APP_NAME__.reception.mjs`: the application's TypeScript Reception (drive it from vitest with `@githolon/testing`).
 
 If application code needs to understand workspaces, event sourcing, JWTs, signatures, retries, topology,
 serialization, or merge algorithms, a framework concern has leaked out of Nomos.

package/template/package.json

@@ -6,7 +6,6 @@
   "description": "A Nomos business application: public intents over private atomic consequences.",
   "scripts": {
     "compile": "githolon compile ./nomos.project.ts && githolon compile ./nomos.application.ts",
-    "proof": "githolon proof",
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {

package/template/tsconfig.json

@@ -11,8 +11,7 @@
   },
   "include": [
     "domains/**/*.ts",
-    "build/*.client.d.mts",
-    "build/*.proof.mts",
+    "build/*.reception.d.mts",
     "test/**/*.mts"
   ]
 }