xoonya 3.0.1 → 3.1.0

package/LICENSE

@@ -1,201 +1,201 @@
-Apache License
-Version 2.0, January 2004
-http://www.apache.org/licenses/
-
-TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-1. Definitions.
-
-"License" shall mean the terms and conditions for use, reproduction,
-and distribution as defined by Sections 1 through 9 of this document.
-
-"Licensor" shall mean the copyright owner or entity authorized by
-the copyright owner that is granting the License.
-
-"Legal Entity" shall mean the union of the acting entity and all
-other entities that control, are controlled by, or are under common
-control with that entity. For the purposes of this definition,
-"control" means (i) the power, direct or indirect, to cause the
-direction or management of such entity, whether by contract or
-otherwise, or (ii) ownership of fifty percent (50%) or more of the
-outstanding shares, or (iii) beneficial ownership of such entity.
-
-"You" (or "Your") shall mean an individual or Legal Entity
-exercising permissions granted by this License.
-
-"Source" form shall mean the preferred form for making modifications,
-including but not limited to software source code, documentation
-source, and configuration files.
-
-"Object" form shall mean any form resulting from mechanical
-transformation or translation of a Source form, including but
-not limited to compiled object code, generated documentation,
-and conversions to other media types.
-
-"Work" shall mean the work of authorship, whether in Source or
-Object form, made available under the License, as indicated by a
-copyright notice that is included in or attached to the work
-(an example is provided in the Appendix below).
-
-"Derivative Works" shall mean any work, whether in Source or Object
-form, that is based on (or derived from) the Work and for which the
-editorial revisions, annotations, elaborations, or other modifications
-represent, as a whole, an original work of authorship. For the purposes
-of this License, Derivative Works shall not include works that remain
-separable from, or merely link (or bind by name) to the interfaces of,
-the Work and Derivative Works thereof.
-
-"Contribution" shall mean any work of authorship, including
-the original version of the Work and any modifications or additions
-to that Work or Derivative Works thereof, that is intentionally
-submitted to Licensor for inclusion in the Work by the copyright owner
-or by an individual or Legal Entity authorized to submit on behalf of
-the copyright owner. For the purposes of this definition, "submitted"
-means any form of electronic, verbal, or written communication sent
-to the Licensor or its representatives, including but not limited to
-communication on electronic mailing lists, source code control systems,
-and issue tracking systems that are managed by, or on behalf of, the
-Licensor for the purpose of discussing and improving the Work, but
-excluding communication that is conspicuously marked or otherwise
-designated in writing by the copyright owner as "Not a Contribution."
-
-"Contributor" shall mean Licensor and any individual or Legal Entity
-on behalf of whom a Contribution has been received by Licensor and
-subsequently incorporated within the Work.
-
-2. Grant of Copyright License. Subject to the terms and conditions of
-this License, each Contributor hereby grants to You a perpetual,
-worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-copyright license to reproduce, prepare Derivative Works of,
-publicly display, publicly perform, sublicense, and distribute the
-Work and such Derivative Works in Source or Object form.
-
-3. Grant of Patent License. Subject to the terms and conditions of
-this License, each Contributor hereby grants to You a perpetual,
-worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-(except as stated in this section) patent license to make, have made,
-use, offer to sell, sell, import, and otherwise transfer the Work,
-where such license applies only to those patent claims licensable
-by such Contributor that are necessarily infringed by their
-Contribution(s) alone or by combination of their Contribution(s)
-with the Work to which such Contribution(s) was submitted. If You
-institute patent litigation against any entity (including a
-cross-claim or counterclaim in a lawsuit) alleging that the Work
-or a Contribution incorporated within the Work constitutes direct
-or contributory patent infringement, then any patent licenses
-granted to You under this License for that Work shall terminate
-as of the date such litigation is filed.
-
-4. Redistribution. You may reproduce and distribute copies of the
-Work or Derivative Works thereof in any medium, with or without
-modifications, and in Source or Object form, provided that You
-meet the following conditions:
-
-(a) You must give any other recipients of the Work or
-Derivative Works a copy of this License; and
-
-(b) You must cause any modified files to carry prominent notices
-stating that You changed the files; and
-
-(c) You must retain, in the Source form of any Derivative Works
-that You distribute, all copyright, patent, trademark, and
-attribution notices from the Source form of the Work,
-excluding those notices that do not pertain to any part of
-the Derivative Works; and
-
-(d) If the Work includes a "NOTICE" text file as part of its
-distribution, then any Derivative Works that You distribute must
-include a readable copy of the attribution notices contained
-within such NOTICE file, excluding those notices that do not
-pertain to any part of the Derivative Works, in at least one
-of the following places: within a NOTICE text file distributed
-as part of the Derivative Works; within the Source form or
-documentation, if provided along with the Derivative Works; or,
-within a display generated by the Derivative Works, if and
-wherever such third-party notices normally appear. The contents
-of the NOTICE file are for informational purposes only and
-do not modify the License. You may add Your own attribution
-notices within Derivative Works that You distribute, alongside
-or as an addendum to the NOTICE text from the Work, provided
-that such additional attribution notices cannot be construed
-as modifying the License.
-
-You may add Your own copyright statement to Your modifications and
-may provide additional or different license terms and conditions
-for use, reproduction, or distribution of Your modifications, or
-for any such Derivative Works as a whole, provided Your use,
-reproduction, and distribution of the Work otherwise complies with
-the conditions stated in this License.
-
-5. Submission of Contributions. Unless You explicitly state otherwise,
-any Contribution intentionally submitted for inclusion in the Work
-by You to the Licensor shall be under the terms and conditions of
-this License, without any additional terms or conditions.
-Notwithstanding the above, nothing herein shall supersede or modify
-the terms of any separate license agreement you may have executed
-with Licensor regarding such Contributions.
-
-6. Trademarks. This License does not grant permission to use the trade
-names, trademarks, service marks, or product names of the Licensor,
-except as required for reasonable and customary use in describing the
-origin of the Work and reproducing the content of the NOTICE file.
-
-7. Disclaimer of Warranty. Unless required by applicable law or
-agreed to in writing, Licensor provides the Work (and each
-Contributor provides its Contributions) on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-implied, including, without limitation, any warranties or conditions
-of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-PARTICULAR PURPOSE. You are solely responsible for determining the
-appropriateness of using or redistributing the Work and assume any
-risks associated with Your exercise of permissions under this License.
-
-8. Limitation of Liability. In no event and under no legal theory,
-whether in tort (including negligence), contract, or otherwise,
-unless required by applicable law (such as deliberate and grossly
-negligent acts) or agreed to in writing, shall any Contributor be
-liable to You for damages, including any direct, indirect, special,
-incidental, or consequential damages of any character arising as a
-result of this License or out of the use or inability to use the
-Work (including but not limited to damages for loss of goodwill,
-work stoppage, computer failure or malfunction, or any and all
-other commercial damages or losses), even if such Contributor
-has been advised of the possibility of such damages.
-
-9. Accepting Warranty or Additional Liability. While redistributing
-the Work or Derivative Works thereof, You may choose to offer,
-and charge a fee for, acceptance of support, warranty, indemnity,
-or other liability obligations and/or rights consistent with this
-License. However, in accepting such obligations, You may act only
-on Your own behalf and on Your sole responsibility, not on behalf
-of any other Contributor, and only if You agree to indemnify,
-defend, and hold each Contributor harmless for any liability
-incurred by, or claims asserted against, such Contributor by reason
-of your accepting any such warranty or additional liability.
-
-END OF TERMS AND CONDITIONS
-
-APPENDIX: How to apply the Apache License to your work.
-
-To apply the Apache License to your work, attach the following
-boilerplate notice, with the fields enclosed by brackets "[]"
-replaced with your own identifying information. (Don't include
-the brackets!) The text should be enclosed in the appropriate
-comment syntax for the file format. We also recommend that a
-file or class name and description of purpose be included on the
-same "printed page" as the copyright notice for easier
-identification within third-party archives.
-
-Copyright 2026 Parth Mauria Saxena
-
-Licensed under the Apache License, Version 2.0 (the "License");
-you may not use this file except in compliance with the License.
-You may obtain a copy of the License at
-
-    http://www.apache.org/licenses/LICENSE-2.0
-
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS,
-WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-See the License for the specific language governing permissions and
-limitations under the License.
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+that You distribute, all copyright, patent, trademark, and
+attribution notices from the Source form of the Work,
+excluding those notices that do not pertain to any part of
+the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must
+include a readable copy of the attribution notices contained
+within such NOTICE file, excluding those notices that do not
+pertain to any part of the Derivative Works, in at least one
+of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or,
+within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and
+do not modify the License. You may add Your own attribution
+notices within Derivative Works that You distribute, alongside
+or as an addendum to the NOTICE text from the Work, provided
+that such additional attribution notices cannot be construed
+as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following
+boilerplate notice, with the fields enclosed by brackets "[]"
+replaced with your own identifying information. (Don't include
+the brackets!) The text should be enclosed in the appropriate
+comment syntax for the file format. We also recommend that a
+file or class name and description of purpose be included on the
+same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+Copyright 2026 Parth Mauria Saxena
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/NOTICE

@@ -1,3 +1,3 @@
-Copyright 2026 Parth Mauria Saxena
-
-This product is released under the Apache License, Version 2.0.
+Copyright 2026 Parth Mauria Saxena
+
+This product is released under the Apache License, Version 2.0.

package/OPERATIONS_RUNBOOK.md

@@ -0,0 +1,50 @@
+# xoonya Operations Runbook
+
+Use this runbook for the normal post-program proof-side operating posture.
+
+## Daily checks
+
+Run:
+
+```bash
+xoonya-release --center --summary
+xoonya-release --candidate --summary
+```
+
+Inspect:
+
+- `/v1/release-center/summary`
+- `/v1/release-candidate/summary`
+- `/v1/proof-center/summary`
+
+## Proof-side confidence checks
+
+Run:
+
+```bash
+npm run verify:examples
+npm run verify:release-candidate
+```
+
+## Handoff review checks
+
+Keep these ready:
+
+- `/v1/proof-center/result-package-handoff/review/summary`
+- `CARRIED_HANDOFF_DEMO.md`
+- `PARTNER_READY_PATH.md`
+- `PUBLIC_DEMO_SCRIPT.md`
+
+## If an outside team asks “what belongs here?”
+
+Point them to:
+
+1. `START_HERE.md`
+2. `PARTNER_READY_PATH.md`
+3. `integrations/PROOF_INTEGRATION_PROCESS.md`
+
+## Boundary rule
+
+If a question depends on payment, funding, settlement, or workflow orchestration, move it back to `xytara`.
+
+If it depends on reviewable proof carry and deterministic proof emission, it can stay in `xoonya`.

package/OPERATOR_START_HERE.md

@@ -0,0 +1,67 @@
+# xoonya Operator Start Here
+
+This is the shortest path for an operator who needs to evaluate `xoonya` after the 10-phase program has already closed.
+
+## 1. Confirm Terminal Program State
+
+Run:
+
+```bash
+xoonya-release --phases --summary
+xoonya-release --phase-10 --summary
+```
+
+Or inspect:
+
+- `GET /v1/phases/summary`
+- `GET /v1/phases/phase-10/gate/summary`
+- `GET /v1/phases/phase-10/completion/summary`
+
+## 2. Confirm Release Posture
+
+Run:
+
+```bash
+xoonya-release --center --summary
+xoonya-release --candidate --summary
+```
+
+These are the fastest checks for "is the proof package live, coherent, and publish-shaped?"
+
+## 3. Exercise The Proof Path
+
+Run:
+
+```bash
+node examples/package_quickstart.js
+```
+
+For direct handoff review, also run:
+
+```bash
+xoonya-review --file ./handoff.json --summary
+```
+
+## 4. Verify Confidence
+
+Run:
+
+```bash
+npm run verify:all
+npm run verify:release-candidate
+```
+
+For the compact day-two operator path, also read:
+
+- `OPERATIONS_RUNBOOK.md`
+
+## 5. Choose The Next Workstream
+
+After the program is closed, the next useful work is one of:
+
+- productization
+- real carried-handoff integration
+- operational hardening
+- launch and release packaging
+
+If you only pick one, pick a real integration and keep the docs/productization work close behind it.

package/PARTNER_READY_PATH.md

@@ -1,67 +1,67 @@
-# xoonya Partner-Ready Path
-
-Use this path when you want to evaluate `xoonya` as an external proof-side integration surface without relying on private milestone history.
-
-## What this path is for
-
-This is the shortest partner-facing route for teams that need to:
-
-- review the proof-side boundary after runtime execution
-- understand what belongs in `xoonya` versus `xytara`
-- confirm how proof-adjacent integrations stay narrow and reviewable
-- leave with one concrete demo path, one proof contract path, and one lightweight integration path
-
-## Recommended reading order
-
-1. Read `START_HERE.md`.
-2. Read `CARRIED_HANDOFF_DEMO.md`.
-3. Read `CROSS_RUNTIME_POSTURE.md`.
-4. Read `integrations/PROOF_INTEGRATION_PROCESS.md`.
-5. Read `COMPATIBILITY_NOTE.md` if you need the narrower legacy bridge posture.
-
-## Recommended first commands
-
-Run these from a cloned `xoonya` repository:
-
-```bash
-node examples/package_quickstart.js
-npm run verify:examples
-npm run verify:release-candidate
-node scripts/registry_cli.js validate-registration --example verifier
-node scripts/registry_cli.js promotion-readiness --integration partner.verifier.lattice_notary
-```
-
-## Recommended first surfaces
-
-- `/v1/release-center/summary`
-- `/v1/proof-center/summary`
-- `/v1/proof-center/result-package-handoff/summary`
-- `/v1/integrations/summary`
-- `/v1/integrations/promotion-readiness`
-
-## First success standard
-
-First success is not "expand proof scope until it acts like the runtime."
-
-First success is:
-
-1. receive one reviewable handoff from `xytara`
-2. inspect proof-side review posture
-3. emit one proof-native completion path
-4. validate one lightweight proof-adjacent integration boundary
-5. keep commerce, pricing, workflow, and settlement semantics outside the proof kernel
-
-## Boundary rule
-
-If an integration needs pricing, funding, workflow orchestration, or settlement logic to make sense, it belongs in `xytara`.
-
-If it can remain a narrow proof helper, registry reference, or verifier-facing addition, it can belong in `xoonya`.
-
-## Hand-off rule
-
-If an outside team leaves this path with only four references, they should be these:
-
-- `START_HERE.md`
-- `CARRIED_HANDOFF_DEMO.md`
-- `CROSS_RUNTIME_POSTURE.md`
-- `integrations/PROOF_INTEGRATION_PROCESS.md`
+# xoonya Partner-Ready Path
+
+Use this path when you want to evaluate `xoonya` as an external proof-side integration surface without relying on private milestone history.
+
+## What this path is for
+
+This is the shortest partner-facing route for teams that need to:
+
+- review the proof-side boundary after runtime execution
+- understand what belongs in `xoonya` versus `xytara`
+- confirm how proof-adjacent integrations stay narrow and reviewable
+- leave with one concrete demo path, one proof contract path, and one lightweight integration path
+
+## Recommended reading order
+
+1. Read `START_HERE.md`.
+2. Read `CARRIED_HANDOFF_DEMO.md`.
+3. Read `CROSS_RUNTIME_POSTURE.md`.
+4. Read `integrations/PROOF_INTEGRATION_PROCESS.md`.
+5. Read `COMPATIBILITY_NOTE.md` if you need the narrower legacy bridge posture.
+
+## Recommended first commands
+
+Run these from a cloned `xoonya` repository:
+
+```bash
+node examples/package_quickstart.js
+npm run verify:examples
+npm run verify:release-candidate
+node scripts/registry_cli.js validate-registration --example verifier
+node scripts/registry_cli.js promotion-readiness --integration partner.verifier.lattice_notary
+```
+
+## Recommended first surfaces
+
+- `/v1/release-center/summary`
+- `/v1/proof-center/summary`
+- `/v1/proof-center/result-package-handoff/summary`
+- `/v1/integrations/summary`
+- `/v1/integrations/promotion-readiness`
+
+## First success standard
+
+First success is not "expand proof scope until it acts like the runtime."
+
+First success is:
+
+1. receive one reviewable handoff from `xytara`
+2. inspect proof-side review posture
+3. emit one proof-native completion path
+4. validate one lightweight proof-adjacent integration boundary
+5. keep commerce, pricing, workflow, and settlement semantics outside the proof kernel
+
+## Boundary rule
+
+If an integration needs pricing, funding, workflow orchestration, or settlement logic to make sense, it belongs in `xytara`.
+
+If it can remain a narrow proof helper, registry reference, or verifier-facing addition, it can belong in `xoonya`.
+
+## Hand-off rule
+
+If an outside team leaves this path with only four references, they should be these:
+
+- `START_HERE.md`
+- `CARRIED_HANDOFF_DEMO.md`
+- `CROSS_RUNTIME_POSTURE.md`
+- `integrations/PROOF_INTEGRATION_PROCESS.md`