@svsprotocol/solana 0.1.0

package/LICENSE

@@ -0,0 +1,158 @@
+Apache License
+Version 2.0, January 2004
+https://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.
+
+"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 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

package/README.md

@@ -0,0 +1,365 @@
+# @svsprotocol/solana
+
+Client SDK boundary for `SVS: Solana Verification System`.
+
+Use this package when a Solana bot or agent needs one trusted path to submit an action, prove signed bot identity, require human/operator approval, fetch production proof, and expose a verified-agent profile or badge.
+
+This package intentionally exports only bot/client/protocol-safe APIs:
+
+- `SolanaVerificationClient`
+- `createSignedBotRequest`
+- certified-submit status helpers
+- action production proof verification helpers
+- verified agent profile and badge helpers
+- deterministic verified-agent trust score helpers
+- signed proof-read verification helpers
+- webhook signature verification helpers
+- `requireVerifiedAgent` from `@svsprotocol/solana/protocol`
+- custom adapter primitives from `@svsprotocol/solana/adapter-core`
+- typed adapter discovery from `@svsprotocol/solana/adapter-catalog`
+- ElizaOS adapter helpers from `@svsprotocol/solana/elizaos`
+- GOAT adapter helpers from `@svsprotocol/solana/goat`
+- Solana Agent Kit adapter helpers from `@svsprotocol/solana/solana-agent-kit`
+- Vercel AI SDK adapter helpers from `@svsprotocol/solana/vercel-ai`
+
+Dashboard, local admin, release, registry-authority, and server internals stay in the main application package.
+
+## License and Boundary
+
+`@svsprotocol/solana` is the public client/adoption SDK and is licensed under Apache-2.0. That license applies only to this package as published. It does not grant rights to the private SVS operator dashboard, server, registry authority, release tooling, deployment evidence, signing keys, hosted registry operations, badges, domains, or trademarks.
+
+The package should remain limited to `README.md`, `LICENSE`, `package.json`, and built `dist/*.js` / `dist/*.d.ts` files. Generated evidence, dashboard files, release bundles, local credentials, wallets, keypairs, `.env`, `.devnet`, tests, and examples must stay out of the npm artifact.
+
+The package ships TypeScript declarations for the root SDK and every public adapter/protocol export. `npm run sdk:check` compiles a real TypeScript consumer against `@svsprotocol/solana` and its subpath exports, so bot teams get checked action payloads, adapter results, verified-agent profiles, registry verification results, and protocol acceptance checks without needing to inspect the dashboard internals.
+
+`npm run sdk:check` also runs the public-package hygiene gate. It uses `npm pack --dry-run` to verify that the publishable tarball only contains `README.md`, `package.json`, and `dist/*.js` / `dist/*.d.ts`; generated evidence, dashboard files, release bundles, credentials, keypairs, wallets, local env files, examples, and tests must stay out of the SDK artifact.
+
+The same hygiene gate compares every public runtime export path against the matching TypeScript declaration file, so a new SDK/helper export cannot ship without a typed public contract.
+
+TypeScript-first bot teams can start from the public typed consumer example:
+
+```sh
+npm run example:typescript:agent
+```
+
+That command compiles `examples/typescript/typed-agent-consumer/typed-agent-consumer.ts`, and the external-consumer release proof compiles the same file after installing the packed SDK into a clean temporary app.
+
+## Bot Builder Fast Path
+
+1. Install `@svsprotocol/solana`.
+2. Fill `SVS_SERVER_URL`, `SVS_BOT_ID`, `SVS_BOT_API_KEY`, `SVS_BOT_REQUEST_SIGNING_SECRET`, and `SVS_BOT_EXPECTED_INTEGRATION_CONTRACT_HASH`.
+3. Run `client.checkBotReadiness({ botId })` at startup.
+4. Submit with `client.submitCertifiedActionAndWaitForProof(...)` for the full signed request, human approval, registry proof, and proof-fetch path.
+5. Use `verifyVerifiedAgentProfile`, `verifyVerifiedAgentRegistryUrl`, or `requireVerifiedAgent` when a protocol, marketplace, or auditor needs to re-check the bot.
+
+Framework teams can use the same path through `@svsprotocol/solana/solana-agent-kit`, `@svsprotocol/solana/elizaos`, `@svsprotocol/solana/goat`, or `@svsprotocol/solana/vercel-ai`.
+
+Tools that generate bot integrations can use the typed adapter catalog instead of scraping docs:
+
+```js
+import {
+  findSvsAgentFrameworkAdapter,
+  getSvsAgentFrameworkAdapters
+} from "@svsprotocol/solana/adapter-catalog";
+
+const adapters = getSvsAgentFrameworkAdapters({ primaryOnly: true });
+for (const adapter of adapters) {
+  console.log(adapter.runtime, adapter.packageExport, adapter.demoCommand);
+}
+
+const eliza = findSvsAgentFrameworkAdapter("SVS_VERIFY_AND_SUBMIT_SOLANA_ACTION");
+console.log(eliza.packageExport); // @svsprotocol/solana/elizaos
+```
+
+SVS host-app validation also requires primary adapters to emit this catalog binding proof. That lets a protocol or bot team verify that a Solana Agent Kit tool or ElizaOS action was loaded from the public SDK adapter catalog, not from an undocumented copy of the adapter contract.
+
+## Adapter Matrix
+
+| Bot runtime | Package export | Tool/action | Demo |
+| --- | --- | --- | --- |
+| Custom agent runtime | `@svsprotocol/solana/adapter-core` | shared readiness and certified-submit primitives | TypeScript consumer example |
+| Solana Agent Kit | `@svsprotocol/solana/solana-agent-kit` | `svs_verify_and_submit_solana_action` | `npm run example:agent:solana-kit` |
+| ElizaOS | `@svsprotocol/solana/elizaos` | `SVS_VERIFY_AND_SUBMIT_SOLANA_ACTION` | `npm run example:agent:elizaos` |
+| GOAT | `@svsprotocol/solana/goat` | `svs_verify_and_submit_solana_action` | `npm run example:agent:goat` |
+| Vercel AI SDK | `@svsprotocol/solana/vercel-ai` | `svsVerifyAndSubmitSolanaAction` | `npm run example:agent:vercel-ai` |
+
+Before public release, `npm run agent:host-validate` packs this SDK, installs it into a custom adapter-core host and minimal real Solana Agent Kit, ElizaOS, GOAT SDK, and Vercel AI SDK host apps, submits through the adapter/plugin/tool, then verifies the returned action record's production proof and current SVS approval domain. That gives bot teams a host-app proof instead of only a workspace import test.
+
+Custom agent runtimes should use `@svsprotocol/solana/adapter-core` instead of importing private SDK internals. It exposes the shared readiness and certified-submit helpers used by the first-party adapters, so a new framework can get the same fail-closed production certification, human approval queueing, proof wait, and typed adapter result contract without copying adapter logic.
+
+## Real Agent Category Demos
+
+| Agent category | Purpose | Demo |
+| --- | --- | --- |
+| DeFi risk gate | Devnet Memo risk intent with protocol/notional/health-factor/LTV policy and human approval | `npm run example:agent:defi-risk` |
+| NFT mint agent | Devnet Memo mint intent with collection/metadata/quantity/fee policy and human approval | `npm run example:agent:nft-mint` |
+| Payment agent | Small devnet SOL transfer through the certified action path | `npm run example:agent:payment` |
+| Trading agent | Devnet Memo trade intent with pair/notional/slippage policy and human approval | `npm run example:agent:trading` |
+| Treasury agent | Larger devnet SOL transfer that locally proves `multisig_required` before submit | `npm run example:agent:treasury` |
+
+```js
+import { SolanaVerificationClient } from "@svsprotocol/solana";
+
+const svs = new SolanaVerificationClient({
+  baseUrl: process.env.SVS_SERVER_URL,
+  apiKey: process.env.SVS_BOT_API_KEY,
+  requestSigningSecret: process.env.SVS_BOT_REQUEST_SIGNING_SECRET
+});
+
+await svs.checkBotReadiness({ botId: process.env.SVS_BOT_ID });
+```
+
+Verified agent profile:
+
+```js
+import {
+  createVerifiedAgentBadgeSvg,
+  verifyVerifiedAgentProfile
+} from "@svsprotocol/solana";
+
+const verification = verifyVerifiedAgentProfile(profile, {
+  expectedBotId: process.env.SVS_BOT_ID,
+  staleAfterMs: 24 * 60 * 60 * 1000
+});
+
+if (!verification.ok) {
+  throw new Error("SVS verified agent profile is not current.");
+}
+
+const badgeSvg = createVerifiedAgentBadgeSvg(profile);
+```
+
+Static registry export:
+
+```sh
+npm run bot:registry -- \
+  --profile ./data/security/verified-agent-profile.json \
+  --badge ./data/security/verified-agent-badge.svg \
+  --out ./data/verified-agent-registry
+
+npm run verify:verified-agent-registry -- \
+  --file ./data/verified-agent-registry/registry.json
+```
+
+The registry directory includes `registry.json`, `trust-manifest.json`, `index.html`, and per-agent profile/badge pages. Host those files privately or publicly to give protocols, auditors, and users one inspectable trust page with the pinned registry hash, verifier commands, proof freshness, and required checks.
+The hosted/self-hosted product target is documented in `docs/hosted-registry-trust-surface.md` at the repo root, including route shape, badge states, protocol allowlists, privacy modes, caching, and production gates.
+
+Create a non-secret adoption handoff after the registry is hosted:
+
+```js
+import { createVerifiedAgentAdoptionKit } from "@svsprotocol/solana";
+
+const kit = createVerifiedAgentAdoptionKit({
+  profile,
+  registry,
+  registryUrl: process.env.SVS_VERIFIED_AGENT_REGISTRY_URL,
+  expectedRegistryHash: process.env.SVS_VERIFIED_AGENT_REGISTRY_HASH
+});
+
+console.log(kit.copy.protocolEnv);
+console.log(kit.copy.sdkSnippet);
+```
+
+The kit packages the pinned registry URL/hash, profile and badge URLs, protocol env, SDK middleware snippet, verifier commands, and checklist without bot API keys or request-signing secrets.
+
+Verify a hosted registry from a bot, protocol service, or auditor machine. This checks the remote registry hash, `trust-manifest.json`, linked profile hashes, profile freshness, verifier instructions, and secret-safety metadata:
+
+```js
+import { verifyVerifiedAgentRegistryUrl } from "@svsprotocol/solana";
+
+const result = await verifyVerifiedAgentRegistryUrl({
+  registryUrl: process.env.SVS_VERIFIED_AGENT_REGISTRY_URL,
+  expectedRegistryHash: process.env.SVS_VERIFIED_AGENT_REGISTRY_HASH
+});
+
+if (!result.ok) {
+  throw new Error("SVS verified-agent registry failed verification.");
+}
+```
+
+Create an explainable trust-score table from already-verified evidence:
+
+```js
+import {
+  VERIFIED_AGENT_TRUST_SCORE_POLICY,
+  createVerifiedAgentTrustScore
+} from "@svsprotocol/solana";
+
+const score = createVerifiedAgentTrustScore({
+  profile,
+  profileVerification,
+  registryVerification,
+  actionProductionProofEvidence,
+  actionProductionProofVerification,
+  credentialReadiness,
+  hostValidation
+});
+
+console.log(score.score, score.status, score.nextAction.message);
+console.log(VERIFIED_AGENT_TRUST_SCORE_POLICY.requiredSignalIds);
+```
+
+The score is deterministic and hashable. It helps protocols compare agents by visible evidence signals, but it does not replace the required profile, registry, production-proof, and approval-domain verifier checks. High trust requires at least `90 / 100` plus all required signals. See `docs/agent-trust-score-policy.md` for the full signal table.
+
+Protocol middleware:
+
+```js
+import { createHostedVerifiedAgentRegistryMiddleware } from "@svsprotocol/solana/protocol";
+
+const requireSvsAgent = createHostedVerifiedAgentRegistryMiddleware({
+  registryUrl: process.env.SVS_VERIFIED_AGENT_REGISTRY_URL,
+  expectedRegistryHash: process.env.SVS_VERIFIED_AGENT_REGISTRY_HASH
+});
+
+await requireSvsAgent({ botId: "devnet-treasury-agent-001" });
+```
+
+This rejects agents that are not listed in the pinned registry or whose hosted `trust-manifest.json` or linked profile fails verification.
+
+## Approval Domain Migration
+
+New production proofs should use the current SVS approval domain:
+
+```text
+svs-solana-verification-system
+```
+
+The legacy domain is still verifier-compatible so older exported receipts and audit bundles remain inspectable:
+
+```text
+solana-human-verification-system
+```
+
+Bots, protocols, and auditors should treat `humanApproval.domainStatus === "current"` as the production-ready path for new actions. Treat `legacy_compatible` as migration/audit compatibility only; it means the approval can still be verified, but the action was signed under the previous product domain.
+
+```js
+import {
+  verifyActionProductionProofEvidence
+} from "@svsprotocol/solana";
+import {
+  requireCurrentApprovalDomain
+} from "@svsprotocol/solana/protocol";
+
+const verification = verifyActionProductionProofEvidence(proofEvidence, {
+  expectedRecordId: proofEvidence.productionProof.recordId,
+  staleAfterMs: 24 * 60 * 60 * 1000
+});
+
+if (!verification.ok) {
+  throw new Error("SVS production proof failed verification.");
+}
+
+requireCurrentApprovalDomain(proofEvidence, { action: "swap" });
+```
+
+For historical audit imports, display `legacy_compatible` clearly instead of hiding it. It is useful evidence for old bundles, but new bot integrations should produce `current`.
+
+Protocol-side check:
+
+```js
+import { requireVerifiedAgent } from "@svsprotocol/solana/protocol";
+
+await requireVerifiedAgent({
+  baseUrl: process.env.SVS_SERVER_URL,
+  apiKey: process.env.SVS_PROTOCOL_API_KEY,
+  botId: "jupiter-rebalancer-001",
+  action: "swap",
+  minCertification: "production_verified"
+});
+```
+
+Copyable protocol demo. This checks production certification plus the exact action record's production proof and current SVS approval domain:
+
+```sh
+npm run example:protocol:verified-agent-gate -- \
+  --env ./examples/protocols/verified-agent-gate-demo/verified-agent-gate-demo.local.env
+```
+
+ElizaOS adapter:
+
+```js
+import { createSvsElizaOsPlugin } from "@svsprotocol/solana/elizaos";
+
+export const svsPlugin = createSvsElizaOsPlugin({
+  baseUrl: process.env.SVS_SERVER_URL,
+  apiKey: process.env.SVS_BOT_API_KEY,
+  requestSigningSecret: process.env.SVS_BOT_REQUEST_SIGNING_SECRET,
+  expectedIntegrationContractHash: process.env.SVS_BOT_EXPECTED_INTEGRATION_CONTRACT_HASH,
+  botId: process.env.SVS_BOT_ID,
+  policyId: "memo-human-approved-v1",
+  rpcUrl: process.env.SOLANA_RPC_URL
+});
+```
+
+Solana Agent Kit adapter:
+
+```js
+import { createSvsSolanaAgentKitAdapter } from "@svsprotocol/solana/solana-agent-kit";
+
+const svsTool = createSvsSolanaAgentKitAdapter({
+  baseUrl: process.env.SVS_SERVER_URL,
+  apiKey: process.env.SVS_BOT_API_KEY,
+  requestSigningSecret: process.env.SVS_BOT_REQUEST_SIGNING_SECRET,
+  expectedIntegrationContractHash: process.env.SVS_BOT_EXPECTED_INTEGRATION_CONTRACT_HASH,
+  botId: process.env.SVS_BOT_ID,
+  policyId: "memo-human-approved-v1",
+  rpcUrl: process.env.SOLANA_RPC_URL
+});
+
+await svsTool.requireSvsProductionReady();
+
+const result = await svsTool.verifyAndSubmitSolanaAction({
+  requestId,
+  intent,
+  serializedTransaction
+});
+```
+
+GOAT adapter:
+
+```js
+import { createSvsGoatPlugin } from "@svsprotocol/solana/goat";
+
+const svsGoat = createSvsGoatPlugin({
+  baseUrl: process.env.SVS_SERVER_URL,
+  apiKey: process.env.SVS_BOT_API_KEY,
+  requestSigningSecret: process.env.SVS_BOT_REQUEST_SIGNING_SECRET,
+  expectedIntegrationContractHash: process.env.SVS_BOT_EXPECTED_INTEGRATION_CONTRACT_HASH,
+  botId: process.env.SVS_BOT_ID,
+  policyId: "memo-human-approved-v1",
+  rpcUrl: process.env.SOLANA_RPC_URL
+});
+
+await svsGoat.requireSvsProductionReady();
+
+const [tool] = svsGoat.getTools();
+const result = await tool.execute({
+  requestId,
+  intent,
+  serializedTransaction
+});
+```
+
+Vercel AI SDK adapter:
+
+```js
+import { tool } from "ai";
+import { z } from "zod";
+import { createSvsVercelAiSdkTools } from "@svsprotocol/solana/vercel-ai";
+
+const svs = createSvsVercelAiSdkTools({
+  tool,
+  z,
+  baseUrl: process.env.SVS_SERVER_URL,
+  apiKey: process.env.SVS_BOT_API_KEY,
+  requestSigningSecret: process.env.SVS_BOT_REQUEST_SIGNING_SECRET,
+  expectedIntegrationContractHash: process.env.SVS_BOT_EXPECTED_INTEGRATION_CONTRACT_HASH,
+  botId: process.env.SVS_BOT_ID,
+  policyId: "memo-human-approved-v1",
+  rpcUrl: process.env.SOLANA_RPC_URL
+});
+
+await svs.requireSvsProductionReady();
+
+const tools = svs.getTools();
+```