xoonya 1.26.0 → 2.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/FINAL_CONTRACT.md CHANGED
@@ -409,7 +409,7 @@ The public API of `xoonya` should center on:
409
409
 
410
410
  Optional profile helpers may be added separately.
411
411
 
412
- ## What Should Be Carried Forward From Older Shoonya Lineage
412
+ ## What Should Be Carried Forward From Older Proof Lineage
413
413
 
414
414
  Keep:
415
415
 
package/README.md CHANGED
@@ -37,6 +37,15 @@ The intended production-facing proof path is now:
37
37
 
38
38
  The rest of this README explains the broader route ladder, but the public starting posture should now be understandable from that one proof-side path.
39
39
 
40
+ For explicit runtime-economics carry, the bridge now also accepts a canonical `handoff_bundle` wrapper from `xytara` so the economic consequence seam stays contract-shaped across the two repos instead of being reassembled ad hoc by callers.
41
+
42
+ That same carried bundle can now also ride inside the normal result-package handoff path:
43
+
44
+ - if `xytara` sends `handoff_bundle.economic_consequence_handoff_bundle`
45
+ - `xoonya` will validate it through the existing bounded bridge logic
46
+ - normal result-package review and run surfaces will expose compact economic-conformance review data automatically
47
+ - direct-pay or non-metered handoffs remain unaffected
48
+
40
49
  The package and service now also expose a default proof center surface so the intended proof-native path is easy to inspect directly:
41
50
 
42
51
  - canonical event bundle v1
@@ -118,6 +127,7 @@ The package quickstart demonstrates:
118
127
  - proof bundle construction
119
128
  - proof bundle verification
120
129
  - transaction proof-handoff follow-through
130
+ - proof-side bridge carry for explicit economic consequence review when runtime economics need proof-adjacent preservation
121
131
 
122
132
  ## Service Quickstart
123
133
 
@@ -155,6 +165,36 @@ Primary proof-model routes:
155
165
  - `POST /v1/proof-center/transaction-handoff/run`
156
166
  - `GET /v1/proof-center/result-package-handoff`
157
167
  - `GET /v1/proof-center/result-package-handoff/summary`
168
+ - `GET /v1/proof-center/governance`
169
+ - `GET /v1/proof-center/governance/summary`
170
+ - `GET /v1/proof-center/bridge`
171
+ - `GET /v1/proof-center/bridge/summary`
172
+ - `GET /v1/proof-center/bridge/profile-support`
173
+ - `POST /v1/proof-center/governance/interpretation-validate`
174
+ - `POST /v1/proof-center/governance/coordination`
175
+ - `POST /v1/proof-center/governance/dashboard`
176
+ - `POST /v1/proof-center/governance/operator-view`
177
+ - `POST /v1/proof-center/governance/admin-view`
178
+ - `POST /v1/proof-center/governance/dashboard-pack`
179
+ - `POST /v1/proof-center/governance/workflow-pack`
180
+ - `POST /v1/proof-center/governance/signoff-pack`
181
+ - `POST /v1/proof-center/governance/disputes/summary`
182
+ - `POST /v1/proof-center/governance/disputes/case-review`
183
+ - `POST /v1/proof-center/governance/disputes/action`
184
+ - `POST /v1/proof-center/governance/disputes/case-bundle`
185
+ - `POST /v1/proof-center/governance/disputes/resolution-pack`
186
+ - `POST /v1/proof-center/governance/console-pack`
187
+ - `POST /v1/proof-center/governance/handoff-bundle`
188
+ - `POST /v1/proof-center/governance/review-link`
189
+ - `POST /v1/proof-center/bridge/receipt-wrap`
190
+ - `POST /v1/proof-center/bridge/validator-verify`
191
+ - `POST /v1/proof-center/bridge/receipt-ledger-handoff`
192
+ - `POST /v1/proof-center/bridge/economic-handoff`
193
+ - `POST /v1/proof-center/bridge/economic-conformance-pack`
194
+ - `POST /v1/proof-center/bridge/operator-review-pack`
195
+ - `POST /v1/proof-center/bridge/compatibility-pack`
196
+ - `POST /v1/proof-center/bridge/workflow-pack`
197
+ - `POST /v1/proof-center/bridge/admin-pack`
158
198
  - `POST /v1/proof-center/result-package-handoff/review`
159
199
  - `POST /v1/proof-center/result-package-handoff/review/summary`
160
200
  - `POST /v1/proof-center/result-package-handoff/review/extension-readiness`
@@ -212,6 +252,25 @@ It now also exposes a handoff-intake summary and handoff-intake-boundary summary
212
252
  It now also exposes a handoff-intake-carry summary so the same proof-side intake surface can be reused more directly as compact consumable carry instead of only summary or boundary posture.
213
253
  It now also exposes a handoff-run summary so that same handoff contract can be read directly as the final proof-native run posture instead of only as continuity guidance.
214
254
 
255
+ The Wave B governance carry-over line adds a bounded governance center on the proof side:
256
+
257
+ - governance interpretation validation for receipt-ledger and result-package follow-through
258
+ - governance coordination emission for the next proof-side/operator handoff step
259
+ - governance dashboard, operator-view, admin-view, dashboard-pack, workflow-pack, and signoff-pack packaging
260
+ - dispute summary, case review, metadata-only dispute action, case-bundle export, and resolution-pack export
261
+ - console-pack, handoff-bundle, and explicit review-link surfaces for compact operator carry into the proof-side review/run ladder
262
+
263
+ This keeps governance review attached to the proof-side operating shape without widening `xoonya` into a runtime or economics system.
264
+
265
+ The Wave E bridge carry-over line adds a bounded bridge center on the proof side:
266
+
267
+ - receipt-wrap support for compact compatibility receipts when an outside bridge still needs that bounded surface
268
+ - validator-compatible verification and receipt inspection posture for bridge-side review
269
+ - receipt-ledger handoff packaging for compact proof-to-economics carry
270
+ - operator review packs, workflow packs, admin packs, and compatibility packs so bridge-facing support breadth is easy to inspect without changing the public proof center
271
+
272
+ This keeps the public story centered on `xoonya` while preserving the useful bridge, validator, and profile lineage as support surfaces instead of separate product identities.
273
+
215
274
  The current `1.18.0` line starts turning that adapter-consumable handoff surface into a clearer adapter-usable handoff package:
216
275
 
217
276
  - proof-side handoff-package intake summaries on top of the intake surface
@@ -7,6 +7,38 @@ This file freezes the public service contract for `xoonya`.
7
7
  Primary proof-model routes:
8
8
 
9
9
  - `GET /health`
10
+ - `GET /v1/proof-center`
11
+ - `GET /v1/proof-center/summary`
12
+ - `GET /v1/proof-center/governance`
13
+ - `GET /v1/proof-center/governance/summary`
14
+ - `GET /v1/proof-center/bridge`
15
+ - `GET /v1/proof-center/bridge/summary`
16
+ - `GET /v1/proof-center/bridge/profile-support`
17
+ - `POST /v1/proof-center/governance/interpretation-validate`
18
+ - `POST /v1/proof-center/governance/coordination`
19
+ - `POST /v1/proof-center/governance/dashboard`
20
+ - `POST /v1/proof-center/governance/operator-view`
21
+ - `POST /v1/proof-center/governance/admin-view`
22
+ - `POST /v1/proof-center/governance/dashboard-pack`
23
+ - `POST /v1/proof-center/governance/workflow-pack`
24
+ - `POST /v1/proof-center/governance/signoff-pack`
25
+ - `POST /v1/proof-center/governance/disputes/summary`
26
+ - `POST /v1/proof-center/governance/disputes/case-review`
27
+ - `POST /v1/proof-center/governance/disputes/action`
28
+ - `POST /v1/proof-center/governance/disputes/case-bundle`
29
+ - `POST /v1/proof-center/governance/disputes/resolution-pack`
30
+ - `POST /v1/proof-center/governance/console-pack`
31
+ - `POST /v1/proof-center/governance/handoff-bundle`
32
+ - `POST /v1/proof-center/governance/review-link`
33
+ - `POST /v1/proof-center/bridge/receipt-wrap`
34
+ - `POST /v1/proof-center/bridge/validator-verify`
35
+ - `POST /v1/proof-center/bridge/receipt-ledger-handoff`
36
+ - `POST /v1/proof-center/bridge/economic-handoff`
37
+ - `POST /v1/proof-center/bridge/economic-conformance-pack`
38
+ - `POST /v1/proof-center/bridge/operator-review-pack`
39
+ - `POST /v1/proof-center/bridge/compatibility-pack`
40
+ - `POST /v1/proof-center/bridge/workflow-pack`
41
+ - `POST /v1/proof-center/bridge/admin-pack`
10
42
  - `POST /v1/events/canonicalize`
11
43
  - `POST /v1/events/hash`
12
44
  - `POST /v1/receipts/emit`
@@ -51,6 +83,20 @@ The constitutional proof loop for `xoonya` is:
51
83
  4. build proof bundle
52
84
  5. verify proof bundle
53
85
 
86
+ Bridge-side economic carry should use:
87
+
88
+ 1. pass deterministic runtime economics through `POST /v1/proof-center/bridge/economic-handoff`
89
+ 2. prefer the canonical `handoff_bundle` wrapper emitted by `xytara`
90
+ 3. review the preserved usage-meter and credit-spend consequence through `POST /v1/proof-center/bridge/economic-conformance-pack`
91
+ 4. keep proof itself minimal while preserving the economic handoff as a bounded bridge/export surface
92
+
93
+ Normal result-package handoff should also accept carried economics when present:
94
+
95
+ 1. send the normal result-package `handoff_bundle`
96
+ 2. include `handoff_bundle.economic_consequence_handoff_bundle` when the transaction-side path was credit-backed and metered
97
+ 3. expect `POST /v1/proof-center/result-package-handoff/run` and review-summary surfaces to expose compact economic-conformance review data automatically
98
+ 4. omit that bundle entirely on direct-pay or non-metered paths without changing proof intake behavior
99
+
54
100
  This loop is exercised through:
55
101
 
56
102
  - package verification
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "xoonya",
3
- "version": "1.26.0",
3
+ "version": "2.0.0",
4
4
  "description": "Deterministic proof SDK for canonical events, receipts, proof bundles, and verification.",
5
5
  "main": "index.js",
6
6
  "type": "commonjs",