xytara 1.0.0

package/.env.example

@@ -0,0 +1,3 @@
+XYTARA_HOST=127.0.0.1
+XYTARA_PORT=4320
+XYTARA_BASE_URL=http://127.0.0.1:4320

package/LICENSE

@@ -0,0 +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 [yyyy] [name of copyright owner]
+
+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/README.md

@@ -0,0 +1,257 @@
+# xytara
+
+`xytara` is the machine transaction and execution layer for the final two-repo public stack.
+
+It exists to let agents, developers, and systems:
+
+- discover tasks and workflows
+- quote work before execution
+- pay through supported payment paths
+- execute tasks and workflows
+- receive deliverables
+- inspect lifecycle state
+- operate through summaries and dashboards
+- integrate third-party adapters
+- emit proof-compatible facts for `the proof repo`
+
+This repo is the hot-state commerce layer. It does not define base proof semantics. It references and emits proof-compatible facts, while `the proof repo` owns canonical proof.
+
+## Commerce Loop
+
+The public product loop is:
+
+1. discover
+2. quote
+3. pay
+4. execute
+5. deliver
+6. inspect
+7. prove
+
+The package and service surfaces both follow that model.
+
+The current built-in catalog now covers a broader first-party `1.0.0` kernel than the original narrow seed, including:
+
+- trust and receipt validation/handoff tasks
+- runtime consequence tasks
+- jobs, credits, and policy tasks
+- registry and anchoring tasks
+- discovery, admission, and settlement tasks
+- an initial built-in `mcp` adapter task
+
+The current built-in settlement posture also now reflects the canonical first-party center of gravity across:
+
+- `ethereum_evm`
+- `bsv_teranode`
+- `solana`
+- `proton_xpr`
+- `antelope_eosio`
+
+## Package Surface
+
+The SDK is broad, but it is organized into a few repeatable families rather than one-off endpoints.
+
+- Discovery and catalog:
+  Use raw getters when you need exact rows, summary getters when you want counts plus rows, and list helpers when you only need high-signal values for filtering or UI controls.
+- Schemas, templates, and validation:
+  Task and workflow schema/template/validation helpers follow the same single-item, batch, and summary pattern.
+- Planning and execution:
+  Quote, preview, execute, and wait helpers exist for single tasks, workflows, and task sets, with both raw and summary forms.
+- Records and operations:
+  Operational records support raw lists, summaries, ID lists, value lists, and aggregate summaries across quotes, transactions, receipts, payments, deliveries, disputes, refunds, and remediation tickets.
+- Operator layer:
+  `getOpenIssuesSummary(...)`, `getExecutionExceptionsSummary(...)`, `getOperationsDashboardSummary(...)`, and `getAttentionRecords(...)` provide compact operator-facing views and drill-downs.
+- Polling, inspection, and reporting:
+  Settled result inspection, linked-record retrieval, reconciliation reporting, and export-pack helpers remain part of the package surface.
+
+This keeps the SDK usable in both styles:
+
+- raw/full-payload access when callers need exact record shapes
+- compact summary/list helpers when callers want quick high-signal commerce state
+
+## Adapter Model
+
+Adapter support is now a first-class public surface.
+
+The repo includes:
+
+- manifest schema:
+  [adapter-manifest.schema.json](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/adapter-manifest.schema.json)
+- interface helper:
+  [interfaces.js](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/interfaces.js)
+- example manifest:
+  [example-execution-adapter.manifest.json](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/examples/example-execution-adapter.manifest.json)
+- example implementation:
+  [example-execution-adapter.js](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/examples/example-execution-adapter.js)
+- second adapter-class example:
+  [example-settlement-adapter.manifest.json](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/examples/example-settlement-adapter.manifest.json)
+  [example-settlement-adapter.js](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/examples/example-settlement-adapter.js)
+- authoring guide:
+  [AUTHORING_GUIDE.md](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/AUTHORING_GUIDE.md)
+- onboarding posture:
+  [ONBOARDING_POSTURE.md](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/ONBOARDING_POSTURE.md)
+
+Current adapter tooling exposes:
+
+- `ADAPTER_INTERFACE_VERSION`
+- `validateAdapterImplementation(...)`
+
+Initial certification starts with:
+
+```bash
+npm run verify:adapters
+```
+
+The current seed freezes the starter contract for:
+
+- adapter identity
+- adapter class
+- compatibility
+- health contract
+- idempotency contract
+- failure contract
+- proof contract
+
+The current onboarding path is now documented for third parties:
+
+1. choose adapter class
+2. build manifest against the schema
+3. implement the interface contract
+4. certify locally with `npm run verify:adapters`
+5. promote through explicit runtime registration
+
+## Quickstart
+
+Run:
+
+```bash
+node examples/quickstart.js
+```
+
+The quickstart exercises:
+
+- health and catalog
+- discovery summaries and filters
+- pricing, schema, and template access
+- validation
+- quote and execution flows
+- dedicated `mcp` invocation flow
+- named runtime, admission, registry, and anchoring task lanes
+- named trust and receipt-handoff lanes
+- lifecycle and operator helpers
+- service-backed client usage
+
+## Service Surface
+
+Run:
+
+```bash
+npm start
+```
+
+Then in another shell:
+
+```bash
+curl http://127.0.0.1:4320/v1/catalog/summary
+curl http://127.0.0.1:4320/v1/operations/dashboard
+curl http://127.0.0.1:4320/v1/operations/attention-records
+curl -X POST http://127.0.0.1:4320/v1/trust/handoffs/emit ^
+  -H "content-type: application/json" ^
+  -H "authorization: Bearer demo-api-key" ^
+  -d "{\"subject_id\":\"subject-1\",\"execution_ref\":\"exec-1\"}"
+curl -X POST http://127.0.0.1:4320/v1/admission/preview ^
+  -H "content-type: application/json" ^
+  -H "authorization: Bearer demo-api-key" ^
+  -d "{\"source_zone_id\":\"zone-a\",\"target_zone_id\":\"zone-b\"}"
+curl -X POST http://127.0.0.1:4320/v1/mcp/tools/invoke ^
+  -H "content-type: application/json" ^
+  -H "authorization: Bearer demo-api-key" ^
+  -d "{\"tool_name\":\"zones.lookup\",\"arguments\":{\"zone_id\":\"zone-1\"}}"
+curl -X POST http://127.0.0.1:4320/v1/payment-quotes ^
+  -H "content-type: application/json" ^
+  -d "{\"command\":\"quickstart\",\"task_ref\":\"trust.verify\",\"body\":{\"subject_id\":\"subject-1\"}}"
+```
+
+Environment example:
+
+- [`.env.example`](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/.env.example)
+
+Primary service routes:
+
+- `GET /health`
+- `GET /v1/catalog`
+- `GET /v1/catalog/summary`
+- `GET /v1/catalog/task?ref=<task_ref_or_alias>`
+- `GET /v1/catalog/workflows`
+- `GET /v1/catalog/workflow?ref=<workflow_ref_or_alias>`
+- `POST /v1/payment-quotes`
+- `POST /v1/trust/handoffs/emit`
+- `POST /v1/trust/handoffs/validate`
+- `POST /v1/execution-receipts/handoffs/emit`
+- `POST /v1/execution-receipts/handoffs/validate`
+- `POST /v1/receipt-ledger/handoffs/emit`
+- `POST /v1/receipt-ledger/handoffs/validate`
+- `POST /v1/admission/preview`
+- `POST /v1/runtime/emit`
+- `POST /v1/runtime/anchor`
+- `POST /v1/runtime/emit-anchor`
+- `POST /v1/registry/register`
+- `POST /v1/anchoring/submit`
+- `POST /v1/mcp/tools/invoke`
+- `GET /v1/payment-quotes`
+- `GET /v1/payment-quotes/:quote_id`
+- `POST /v1/commands/execute`
+- `POST /x402/commands/execute`
+- `POST /x402/mcp/tools/invoke`
+- `GET /v1/governed-transactions`
+- `GET /v1/governed-transactions/:transaction_id`
+- `GET /v1/receipts`
+- `GET /v1/receipts/:receipt_id`
+- `GET /v1/payment-ledger`
+- `GET /v1/payment-ledger/:payment_id`
+- `GET /v1/deliveries`
+- `GET /v1/deliveries/:delivery_id`
+- `GET /v1/disputes`
+- `POST /v1/disputes`
+- `GET /v1/disputes/:dispute_id`
+- `POST /v1/disputes/:dispute_id/actions`
+- `GET /v1/refunds`
+- `POST /v1/refunds`
+- `GET /v1/refunds/:refund_id`
+- `POST /v1/refunds/:refund_id/actions`
+- `POST /v1/remediation-tickets`
+- `GET /v1/remediation-tickets`
+- `GET /v1/remediation-tickets/:ticket_id`
+- `POST /v1/remediation-tickets/:ticket_id/actions`
+- `GET /v1/reconciliation-report`
+- `GET /v1/operator-export-pack`
+- `GET /v1/operations/dashboard`
+- `GET /v1/operations/attention-records`
+
+## Verification
+
+Local verification commands:
+
+- `npm run verify:package`
+- `npm run verify:adapters`
+- `npm run verify:examples`
+- `npm run verify:service`
+- `npm run verify:all`
+
+The current verification covers:
+
+- package exports and helper breadth
+- adapter manifest and implementation conformance
+- quickstart behavior
+- service-route behavior
+- preserved operator/reporting surfaces
+
+## Control Files
+
+- `FINAL_CONTRACT.md`
+- `TERMINOLOGY.md`
+- `SERVICE_CONTRACT.md`
+
+Internal program-history docs for this repo live under:
+
+- [xytara program archive](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/_program/xytara)

package/adapters/AUTHORING_GUIDE.md

@@ -0,0 +1,89 @@
+# Adapter Authoring Guide
+
+This guide describes the minimum process for a third party to build an adapter on top of `xytara`.
+
+## 1. Choose an adapter class
+
+Supported starter classes:
+
+- `execution_adapter`
+- `payment_rail_adapter`
+- `settlement_adapter`
+- `agent_protocol_adapter`
+- `identity_registry_adapter`
+
+Pick the class that matches the boundary you are integrating.
+
+## 2. Start from the manifest schema
+
+Use:
+
+- [adapter-manifest.schema.json](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/adapter-manifest.schema.json)
+
+Every adapter must publish a manifest that defines:
+
+- adapter identity
+- adapter class
+- interface version
+- compatibility
+- health contract
+- idempotency contract
+- failure contract
+- proof contract
+
+## 3. Implement the interface contract
+
+Use:
+
+- [interfaces.js](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/interfaces.js)
+
+All adapters must provide:
+
+- `manifest`
+- `getHealth()`
+- `describeCapabilities()`
+
+Execution adapters should also provide:
+
+- `preview()`
+- `execute()`
+
+Settlement adapters should also provide:
+
+- `settle()`
+- `getFinality()`
+
+## 4. Start from an example
+
+Current examples:
+
+- [example-execution-adapter.manifest.json](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/examples/example-execution-adapter.manifest.json)
+- [example-execution-adapter.js](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/examples/example-execution-adapter.js)
+- [example-settlement-adapter.manifest.json](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/examples/example-settlement-adapter.manifest.json)
+- [example-settlement-adapter.js](C:/Users/Yoga/Desktop/workspace/vscode_workspace_public/naxytra/xytara/adapters/examples/example-settlement-adapter.js)
+
+## 5. Run certification
+
+Run:
+
+```bash
+npm run verify:adapters
+```
+
+That currently validates:
+
+- manifest shape
+- interface version
+- manifest/implementation agreement
+- representative health/capability behavior
+- representative method behavior for example adapters
+
+## 6. Keep the boundary clean
+
+Adapters should integrate external systems without redefining:
+
+- proof semantics
+- quote semantics
+- core commerce lifecycle semantics
+
+They translate external systems into the stack contract. They do not replace the stack contract.

package/adapters/ONBOARDING_POSTURE.md

@@ -0,0 +1,39 @@
+# Adapter Onboarding Posture
+
+This note captures the current intended onboarding flow for third-party adapters.
+
+## Current onboarding path
+
+1. implement adapter against the public interface version
+2. publish a manifest that satisfies the schema
+3. validate implementation behavior with the adapter verifier
+4. confirm compatibility with the current commerce and proof contracts
+5. add the adapter into catalog/runtime registration only after certification passes
+
+## Current registration stance
+
+This repo does not yet provide a full public adapter registry service.
+
+The current posture is:
+
+- adapter manifests and implementations can be authored against the public contract
+- certification begins locally with `npm run verify:adapters`
+- runtime registration remains an explicit product step, not an implicit side effect of dropping files into the repo
+
+## Promotion model
+
+Recommended promotion flow:
+
+1. local development
+2. local certification
+3. staging/runtime integration
+4. production registration
+
+## Why this matters
+
+This keeps adapter support:
+
+- flexible
+- testable
+- explicit
+- less likely to drift into hidden private assumptions