xoonya 3.1.0 → 3.1.2

package/PUBLIC_DEMO_SCRIPT.md

@@ -1,79 +1,79 @@
-# xoonya Public Demo Script
-
-Use this script when you need a short external-facing walkthrough of `xoonya` that does not depend on milestone history.
-
-## Goal
-
-Show the proof side of the public stack in one compact flow:
-
-1. package is live
-2. proof center is understandable
-3. runtime handoff review is concrete
-4. proof-side integration posture is narrow and explicit
-
-## Recommended order
-
-### 1. Release posture
-
-Run:
-
-```bash
-xoonya-release --center --summary
-xoonya-release --candidate --summary
-```
-
-Or inspect:
-
-- `/v1/release-center/summary`
-- `/v1/release-candidate/summary`
-
-### 2. Proof center posture
-
-Inspect:
-
-- `/v1/proof-center/summary`
-- `/v1/proof-center/result-package-handoff/review/summary`
-
-Key sentence to say out loud:
-
-`xoonya` is the proof-native completion layer, not a second runtime.
-
-### 3. Public proof walkthrough
-
-Run:
-
-```bash
-node examples/partner_proof_walkthrough.js
-```
-
-Then, if you want the broader package tour:
-
-```bash
-node examples/package_quickstart.js
-```
-
-### 4. Partner adoption path
-
-Open:
-
-- `PARTNER_READY_PATH.md`
-- `integrations/PROOF_INTEGRATION_PROCESS.md`
-
-Key sentence to say out loud:
-
-Proof-adjacent integrations stay narrow and reviewable instead of absorbing commerce logic.
-
-### 5. Stack positioning
-
-Open:
-
-- `CARRIED_HANDOFF_DEMO.md`
-- `WHY_XYTARA_XOONYA.md`
-
-Key sentence to say out loud:
-
-`xoonya` receives carry from `xytara`, reviews it, and emits deterministic proof-native completion.
-
-## Good ending line
-
-`xoonya` is the public proof system: receive carry, review posture, emit proof, verify the final bundle.
+# xoonya Public Demo Script
+
+Use this script when you need a short external-facing walkthrough of `xoonya` that does not depend on milestone history.
+
+## Goal
+
+Show the proof side of the public stack in one compact flow:
+
+1. package is live
+2. proof center is understandable
+3. runtime handoff review is concrete
+4. proof-side integration posture is narrow and explicit
+
+## Recommended order
+
+### 1. Release posture
+
+Run:
+
+```bash
+xoonya-release --center --summary
+xoonya-release --candidate --summary
+```
+
+Or inspect:
+
+- `/v1/release-center/summary`
+- `/v1/release-candidate/summary`
+
+### 2. Proof center posture
+
+Inspect:
+
+- `/v1/proof-center/summary`
+- `/v1/proof-center/result-package-handoff/review/summary`
+
+Key sentence to say out loud:
+
+`xoonya` is the proof-native completion layer, not a second runtime.
+
+### 3. Public proof walkthrough
+
+Run:
+
+```bash
+node examples/partner_proof_walkthrough.js
+```
+
+Then, if you want the broader package tour:
+
+```bash
+node examples/package_quickstart.js
+```
+
+### 4. Partner adoption path
+
+Open:
+
+- `PARTNER_READY_PATH.md`
+- `integrations/PROOF_INTEGRATION_PROCESS.md`
+
+Key sentence to say out loud:
+
+Proof-adjacent integrations stay narrow and reviewable instead of absorbing commerce logic.
+
+### 5. Stack positioning
+
+Open:
+
+- `CARRIED_HANDOFF_DEMO.md`
+- `WHY_XYTARA_XOONYA.md`
+
+Key sentence to say out loud:
+
+`xoonya` receives carry from `xytara`, reviews it, and emits deterministic proof-native completion.
+
+## Good ending line
+
+`xoonya` is the public proof system: receive carry, review posture, emit proof, verify the final bundle.