npm - @dev.sail.money/sailor - Versions diffs - 0.0.2-12 → 0.0.2-15 - Mend

@dev.sail.money/sailor 0.0.2-12 → 0.0.2-15

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.

Files changed (124) hide show

package/packages/ui/dist/assets/{walletconnect-8pZBDvVI.js → walletconnect-BT9pozGB.js} RENAMED Viewed

@@ -1,4 +1,4 @@
-import{F as l}from"./core-Ckx_cyuH.js";import"./index-Q2Yai4Fe.js";import"./events-CiKP71cK.js";import"./index.es-C78cE5SI.js";import"./fallback-Ofl6uSnB.js";const o=l`<svg fill="none" viewBox="0 0 96 67">
+import{F as l}from"./core-C8jSlwHY.js";import"./index-L6zhWbjO.js";import"./events-i9ztcj9W.js";import"./index.es-BxPfiRyX.js";import"./fallback-CtKplO-p.js";const o=l`<svg fill="none" viewBox="0 0 96 67">
   <path
     fill="currentColor"
     d="M25.32 18.8a32.56 32.56 0 0 1 45.36 0l1.5 1.47c.63.62.63 1.61 0 2.22l-5.15 5.05c-.31.3-.82.3-1.14 0l-2.07-2.03a22.71 22.71 0 0 0-31.64 0l-2.22 2.18c-.31.3-.82.3-1.14 0l-5.15-5.05a1.55 1.55 0 0 1 0-2.22l1.65-1.62Zm56.02 10.44 4.59 4.5c.63.6.63 1.6 0 2.21l-20.7 20.26c-.62.61-1.63.61-2.26 0L48.28 41.83a.4.4 0 0 0-.56 0L33.03 56.21c-.63.61-1.64.61-2.27 0L10.07 35.95a1.55 1.55 0 0 1 0-2.22l4.59-4.5a1.63 1.63 0 0 1 2.27 0L31.6 43.63a.4.4 0 0 0 .57 0l14.69-14.38a1.63 1.63 0 0 1 2.26 0l14.69 14.38a.4.4 0 0 0 .57 0l14.68-14.38a1.63 1.63 0 0 1 2.27 0Z"

package/packages/ui/dist/assets/{warning-circle-ylLEE0Yp.js → warning-circle-BQ8awbZW.js} RENAMED Viewed

@@ -1,4 +1,4 @@
-import{F as r}from"./core-Ckx_cyuH.js";import"./index-Q2Yai4Fe.js";import"./events-CiKP71cK.js";import"./index.es-C78cE5SI.js";import"./fallback-Ofl6uSnB.js";const a=r`<svg fill="none" viewBox="0 0 20 20">
+import{F as r}from"./core-C8jSlwHY.js";import"./index-L6zhWbjO.js";import"./events-i9ztcj9W.js";import"./index.es-BxPfiRyX.js";import"./fallback-CtKplO-p.js";const a=r`<svg fill="none" viewBox="0 0 20 20">
   <path
     fill="currentColor"
     d="M11 6.67a1 1 0 1 0-2 0v2.66a1 1 0 0 0 2 0V6.67ZM10 14.5a1.25 1.25 0 1 0 0-2.5 1.25 1.25 0 0 0 0 2.5Z"

package/packages/ui/dist/assets/{x-C_TBsTMj.js → x-D21DQ5BR.js} RENAMED Viewed

@@ -1,4 +1,4 @@
-import{F as l}from"./core-Ckx_cyuH.js";import"./index-Q2Yai4Fe.js";import"./events-CiKP71cK.js";import"./index.es-C78cE5SI.js";import"./fallback-Ofl6uSnB.js";const a=l`<svg fill="none" viewBox="0 0 41 40">
+import{F as l}from"./core-C8jSlwHY.js";import"./index-L6zhWbjO.js";import"./events-i9ztcj9W.js";import"./index.es-BxPfiRyX.js";import"./fallback-CtKplO-p.js";const a=l`<svg fill="none" viewBox="0 0 41 40">
   <g clip-path="url(#a)">
     <path fill="#000" d="M.8 0h40v40H.8z" />
     <path

package/packages/ui/dist/index.html CHANGED Viewed

@@ -5,7 +5,7 @@
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
     <meta name="theme-color" content="#040b16" />
     <title>Sail - Unlocking Personalized Money</title>
-    <script type="module" crossorigin src="/assets/index-Q2Yai4Fe.js"></script>
+    <script type="module" crossorigin src="/assets/index-L6zhWbjO.js"></script>
     <link rel="stylesheet" crossorigin href="/assets/index-CKxgNxS9.css">
   </head>
   <body>

package/scripts/check-init.mjs CHANGED Viewed

@@ -53,9 +53,8 @@ try {
     fail(`\`sailor init ${PROJECT}\` exited non-zero.\n  ${out || err.message}`);
   }
-  // A successful fresh init prints the welcome + next steps, ending with the
-  // `Say: "start"` call-to-action. (Older builds printed "Done!".)
-  if (!/Say: "start"/.test(stdout)) {
+  // A successful fresh init prints the single-line handoff to the AI assistant.
+  if (!/say start/i.test(stdout)) {
     fail(`init did not report success.\n  stdout: ${stdout.trim()}`);
   }

package/scripts/postinstall.js CHANGED Viewed

@@ -2,24 +2,19 @@
 /**
  * Post-install script for the Sailor package.
  *
- * Runs automatically after `npm install` / `pnpm add`.  Orchestrates:
- *   1. sailor init      — scaffold the .sail/ workspace (skipped if already done)
- *   2. sailor station   — start the signing daemon in background
- *   3. sailor ui        — start the dashboard server in background
- *   4. browser launch   — open the dashboard so the user hits the onboarding flow
+ * Runs automatically after `npm install` / `pnpm add`. Does two things:
+ *   1. sailor init — scaffold the .sail/ workspace (skipped if already done)
+ *   2. Print the one-line handoff banner directing the user to their AI assistant
  *
- * Every step is logged in a structured way so an automated agent can parse the
- * output and know exactly which services are up, which failed, and where to send
- * the user next.
+ * The UI and browser launch that previously ran here have been removed.
+ * The chat (AGENTS.md) owns the welcome — the terminal just directs traffic.
  */
 "use strict";
 const fs = require("node:fs");
 const path = require("node:path");
-const http = require("node:http");
-const os = require("node:os");
-const { execFileSync, spawn } = require("node:child_process");
+const { execFileSync } = require("node:child_process");
 // Directory where the user ran `npm install` / `pnpm add`
 const initCwd = process.env.INIT_CWD || process.cwd();
@@ -40,327 +35,22 @@ if (!fs.existsSync(cliBundle)) {
   process.exit(0);
 }
-// ── Logging helpers ──────────────────────────────────────────────────────────
+// ── Step 1: scaffold — run sailor init if not already done ───────────────────
-function log(msg) { console.log(`${TAG} ${msg}`); }
-function ok(msg)  { console.log(`${TAG} ✓ ${msg}`); }
-function fail(msg){ console.error(`${TAG} ✗ ${msg}`); }
-function sep(label) {
-  console.log(`${TAG} ${"─".repeat(52)}`);
-  if (label) console.log(`${TAG}  ${label}`);
-}
-// ── Utilities ────────────────────────────────────────────────────────────────
-function readJson(file) {
-  try { return JSON.parse(fs.readFileSync(file, "utf-8")); } catch { return null; }
-}
-function isAlive(pid) {
-  try { process.kill(pid, 0); return true; } catch { return false; }
-}
-/** Repeatedly calls fn() until it returns a non-null value or the timeout expires. */
-function poll(fn, { timeout = 12_000, interval = 600 } = {}) {
-  return new Promise((resolve) => {
-    const deadline = Date.now() + timeout;
-    function attempt() {
-      Promise.resolve(fn()).then((result) => {
-        if (result != null) { resolve(result); return; }
-        if (Date.now() >= deadline) { resolve(null); return; }
-        setTimeout(attempt, interval);
-      });
-    }
-    attempt();
-  });
-}
-/** Returns true if any HTTP response arrives from url (any status = server is up). */
-function httpPing(url) {
-  return new Promise((resolve) => {
-    try {
-      const req = http.get(url, { timeout: 2500 }, (res) => {
-        res.resume();
-        resolve(true);
-      });
-      req.on("error", () => resolve(false));
-      req.on("timeout", () => { req.destroy(); resolve(false); });
-    } catch { resolve(false); }
-  });
-}
-/** Open the user's default browser (best-effort, non-fatal). */
-function openBrowser(url) {
-  try {
-    const platform = os.platform();
-    if (platform === "darwin") {
-      spawn("open", [url], { stdio: "ignore", detached: true }).unref();
-    } else if (platform === "win32") {
-      // `start ""` avoids treating the URL as a window title
-      spawn("cmd", ["/c", "start", "", url], { stdio: "ignore", detached: true }).unref();
-    } else {
-      spawn("xdg-open", [url], { stdio: "ignore", detached: true }).unref();
-    }
-  } catch { /* best-effort */ }
-}
-// ── Shared status object (machine-readable summary at the end) ───────────────
-const status = {
-  init:    { state: "skipped",     detail: "" },
-  station: { state: "not-started", detail: "" },
-  ui:      { state: "not-started", detail: "" },
-  uiUrl:   /** @type {string|null} */ (null),
-  errors:  /** @type {string[]} */ ([]),
-};
-// ── Step 1: init ─────────────────────────────────────────────────────────────
-async function step1Init() {
-  sep("Step 1 — init");
-  const configExists = fs.existsSync(path.join(initCwd, ".sail", "config.json"));
+const configExists = fs.existsSync(path.join(initCwd, ".sail", "config.json"));
-  if (configExists) {
-    ok("Project already initialized — skipping init.");
-    status.init = { state: "already-initialized", detail: path.join(initCwd, ".sail", "config.json") };
-    return true;
-  }
-  log("Running sailor init…");
+if (!configExists) {
   try {
     execFileSync(process.execPath, [cliBundle, "init"], {
       cwd: initCwd,
       stdio: "inherit",
     });
-    ok("Init complete.");
-    status.init = { state: "ok", detail: "" };
-    return true;
-  } catch (err) {
-    fail("sailor init exited with an error. Run `sailor init` manually to complete setup.");
-    const msg = err instanceof Error ? err.message : String(err);
-    status.init = { state: "error", detail: msg };
-    status.errors.push(`init: ${msg}`);
-    return false;
-  }
-}
-// ── Step 2: signing station ───────────────────────────────────────────────────
-async function step2Station() {
-  sep("Step 2 — signing station");
-  const stateFile = path.join(initCwd, ".sail", "runtime", "server.json");
-  const existing = readJson(stateFile);
-  // Already running?
-  if (existing && existing.pid && isAlive(existing.pid)) {
-    ok(`Station already running at ${existing.url}  (pid ${existing.pid})`);
-    status.station = { state: "already-running", detail: existing.url };
-    return;
-  }
-  // Remove stale state file if present
-  if (existing) {
-    try { fs.rmSync(stateFile, { force: true }); } catch { /* ignore */ }
-  }
-  log("Starting signing station in background…");
-  // station start blocks (keeps the process alive), so we must spawn it detached.
-  const child = spawn(process.execPath, [cliBundle, "station", "start"], {
-    cwd: initCwd,
-    detached: true,
-    stdio: "ignore",
-  });
-  child.unref();
-  // Poll until the state file appears and /config responds
-  const state = await poll(async () => {
-    const s = readJson(stateFile);
-    if (!s || !s.url || !s.pid) return null;
-    if (!isAlive(s.pid)) return null;
-    const up = await httpPing(`${s.url}/config`);
-    return up ? s : null;
-  }, { timeout: 15_000 });
-  if (state) {
-    ok(`Station running at ${state.url}  (pid ${state.pid})`);
-    status.station = { state: "running", detail: state.url };
-  } else {
-    fail("Station did not come up within 15 s.");
-    fail("Start it manually with: sailor station start");
-    status.station = { state: "error", detail: "timed out" };
-    status.errors.push("station: timed out waiting for /config to respond");
+  } catch {
+    // sailor init failed or was interrupted — user can run it manually
+    console.warn(`${TAG} sailor init exited with an error. Run \`sailor init\` manually to complete setup.`);
   }
 }
-// ── Step 3: dashboard UI ──────────────────────────────────────────────────────
-async function step3Ui() {
-  sep("Step 3 — dashboard UI");
-  const stateFile = path.join(initCwd, ".sail", "runtime", "ui.json");
-  const existing = readJson(stateFile);
-  // Already running?
-  if (existing && existing.pid && isAlive(existing.pid)) {
-    const url = `http://localhost:${existing.port}`;
-    ok(`UI already running at ${url}  (pid ${existing.pid})`);
-    status.ui = { state: "already-running", detail: url };
-    status.uiUrl = url;
-    return;
-  }
-  // Remove stale state file if present
-  if (existing) {
-    try { fs.rmSync(stateFile, { force: true }); } catch { /* ignore */ }
-  }
-  log("Starting Sailor UI in background…");
-  // uiCommand() spawns the server process itself and returns quickly (~300 ms).
-  try {
-    execFileSync(process.execPath, [cliBundle, "ui"], {
-      cwd: initCwd,
-      stdio: "pipe", // suppress duplicate "Sailor UI started" output; we log our own
-    });
-  } catch (err) {
-    const msg = err instanceof Error ? err.message : String(err);
-    fail(`UI start failed: ${msg}`);
-    status.ui = { state: "error", detail: msg };
-    status.errors.push(`ui: ${msg}`);
-    return;
-  }
-  // uiCommand writes the state file before returning; read it immediately.
-  const state = readJson(stateFile);
-  if (!state || !state.port) {
-    fail("UI state file missing after start. Run `sailor ui` manually.");
-    status.ui = { state: "error", detail: "state file missing" };
-    status.errors.push("ui: .sail/runtime/ui.json not written after start");
-    return;
-  }
-  const url = `http://localhost:${state.port}`;
-  // Wait until the server is actually serving (it may need a moment to bind).
-  const up = await poll(() => httpPing(url), { timeout: 10_000, interval: 500 });
-  if (up) {
-    ok(`UI running at ${url}  (pid ${state.pid})`);
-    status.ui = { state: "running", detail: url };
-    status.uiUrl = url;
-  } else {
-    fail(`UI process started (pid ${state.pid}) but not responding at ${url}.`);
-    fail("Run `sailor ui status` to check.");
-    status.ui = { state: "degraded", detail: url };
-    status.uiUrl = url; // still try to open the browser — maybe it comes up in time
-    status.errors.push(`ui: process alive but HTTP not responding at ${url}`);
-  }
-}
-// ── Step 4: open browser ──────────────────────────────────────────────────────
-async function step4Browser() {
-  if (!status.uiUrl) return;
-  sep("Step 4 — opening browser");
-  log(`Opening ${status.uiUrl} …`);
-  openBrowser(status.uiUrl);
-}
-// ── Final summary ─────────────────────────────────────────────────────────────
-function printSummary() {
-  const icon = (s) =>
-    ({ ok: "✓", "already-initialized": "✓", "already-running": "✓", running: "✓",
-       skipped: "–", error: "✗", degraded: "⚠", "not-started": "–" })[s] ?? "?";
-  sep("SAILOR SETUP — STATUS SUMMARY");
-  log(`  init:    ${icon(status.init.state)}  ${status.init.state}${status.init.detail ? "  (" + status.init.detail + ")" : ""}`);
-  log(`  station: ${icon(status.station.state)}  ${status.station.detail || status.station.state}`);
-  log(`  ui:      ${icon(status.ui.state)}  ${status.ui.detail || status.ui.state}`);
-  if (status.errors.length) {
-    log("");
-    log("  Errors encountered:");
-    status.errors.forEach((e) => log(`    • ${e}`));
-  }
-  sep();
-  if (status.uiUrl) {
-    log(`  → Onboarding: ${status.uiUrl}`);
-    log(`    Open the URL above to connect your wallet and complete setup.`);
-  } else {
-    log(`  → Run \`sailor ui\` to start the dashboard.`);
-    log(`  → Run \`sailor station start\` to start the signing daemon.`);
-    log(`  → Then open the dashboard URL to complete onboarding.`);
-  }
-  sep();
-  printAgentInstructions();
-}
-function printAgentInstructions() {
-  const uiUrl = status.uiUrl ?? "<sailor ui URL — run `sailor ui` to get it>";
-  const L = (msg = "") => console.log(`${TAG} ${msg}`);
-  L("╔══════════════════════════════════════════════════════╗");
-  L("║              IF YOU ARE AN AI AGENT                 ║");
-  L("╚══════════════════════════════════════════════════════╝");
-  L();
-  L("  Sailor has been installed and its services are running.");
-  L("  Your job now is to guide the USER through onboarding.");
-  L();
-  L("  ── Step 1: ask the user these questions ────────────────");
-  L();
-  L("  1. Which network do you want to deploy your SMA on?");
-  L("     (e.g. Base, Arbitrum One, Ethereum mainnet, …)");
-  L();
-  L("  2. Do you have an RPC URL for that network?");
-  L("     If not, suggest a free provider: Alchemy, Infura, Ankr.");
-  L("     Once they have it: write it to .sail/.env.local as RPC_URL=<url>");
-  L();
-  L("  3. Do you have a funded wallet (MetaMask or similar)?");
-  L("     They will need gas on the chosen network to deploy the SMA.");
-  L();
-  L("  ── Step 2: send the user to the browser ────────────────");
-  L();
-  L(`  Dashboard: ${uiUrl}`);
-  L();
-  L("  Tell them to open the URL and complete these 3 browser steps:");
-  L("    a. Connect their wallet");
-  L("    b. Deploy their SMA  (requires gas on the chosen network)");
-  L("    c. Create the agent wallet");
-  L();
-  L("  The signing station is running — browser requests will be");
-  L("  routed through it automatically.");
-  L();
-  L("  ── Step 3: once browser steps are done ─────────────────");
-  L();
-  L("  Ask the user to describe their strategy (what the agent");
-  L("  should do, with what limits). Then:");
-  L("    • Build the mandate contract:  sailor mandate deploy …");
-  L("    • Verify everything is healthy: sailor doctor");
-  L("    • Set up automation (local or GitHub Actions)");
-  L();
-  L("  Run `sailor capabilities` for a full list of what this");
-  L("  kernel version supports (no wallet, no gas needed).");
-  L();
-  L("══════════════════════════════════════════════════════════");
-}
-// ── Main ──────────────────────────────────────────────────────────────────────
-(async () => {
-  await step1Init();
-  // Start station and UI concurrently — they are independent of each other.
-  // Station is discovered by the UI at runtime via .sail/runtime/server.json.
-  // We attempt both even if init failed, in case the project was partially set up.
-  await Promise.all([step2Station(), step3Ui()]);
+// ── Done — direct the user to their AI assistant ─────────────────────────────
-  await step4Browser();
-  printSummary();
-})();
+console.log("\nYour Sail agent project is ready. Open your AI coding assistant in this folder and say start.");

package/templates/{dca-rebalancer → default}/.sail/config.json RENAMED Viewed

@@ -1,7 +1,7 @@
 {
   "version": 1,
-  "name": "dca-rebalancer",
-  "chainId": 8453,
+  "name": "sail-agent",
+  "chainId": null,
   "stateDir": ".sail/state",
   "contracts": {
     "kernel": "",

package/templates/default/AGENTS.md ADDED Viewed

@@ -0,0 +1,92 @@
+Sail Protocol is infrastructure for onchain Separately Managed Accounts run by AI agents. You create an SMA, keep full custody, and define exactly what your agent can do — cryptographically bound permissions you approve and can always revoke. The agent executes within those bounds on every transaction. It cannot exceed them.
+I'm Sailor, the operator that sets this up. I'll help you create your SMA, build the permissions that bound your agent, and get your strategy running.
+Here's where we're headed:
+1. Deploy your SMA and create your agent wallet
+2. Define your strategy
+3. Build, test, and sign your mandate
+4. Run your agent — locally or on a schedule
+5. Extend with notifications and a custom dashboard
+Ready? Say **start** and I'll open the setup interface in your browser.
+---
+# Instructions for the assistant
+Everything below is for you, the assistant. The user sees the welcome above; you follow the flow below.
+## Voice
+You are Sailor. Serious, precise, confident. No hype, no emojis, no exclamation marks. Explain *why*, not just *what* — the user is moving real funds. Use user-facing terms (SMA, mandate, permissions, agent wallet, owner). Assume crypto-native; teach the Sail-specific model.
+Never overstate safety: custody is protected, but a mandate is only as correct as its permission contracts.
+## Authorization rule
+During **setup**, always ask before anything that costs gas. Once the **mandate is signed and the agent is running**, the mandate is the authorization — the agent transacts autonomously. Do not ask per-dispatch.
+## First contact
+When the user says start (or any first message), present the welcome above in full — definition, stage list, handoff line — before doing anything else. Do not launch the UI yet. After the user says start a second time (or confirms they are ready), THEN run `sailor ui start`. The welcome and the UI launch are two separate beats separated by the user's go-ahead.
+Determine the user's progress by reading `.sail/` — do not ask; read it.
+If the user's first message is an npm install command, run it, then present the welcome immediately after it completes — do not wait for another message.
+## Stage 1 — Deploy your SMA and create your agent wallet
+In the browser. Run `sailor ui start`, open the printed URL, connect your owner wallet, choose your network, and deploy your SMA. Then create your agent wallet — a separate signing key I use to submit transactions on your behalf. You need gas in both: the owner wallet to deploy and sign the mandate; the agent wallet to submit transactions once the agent is running. The owner key never leaves the browser.
+## Stage 2 — Define your strategy
+Tell me what you want your agent to do. I'll ask the right questions, establish the on-chain bounds with you (tokens, amounts, slippage, venues), and set up your RPC endpoint once you've chosen your chain. Blank slate — you define the strategy.
+For a worked end-to-end example (DCA / Uniswap V3 / Base), consult `examples/dca/` — reference only; not your strategy.
+## Stage 3 — Build, test, and sign your mandate
+I'll write the permission contracts that bound your agent, prove in plain English what each one permits and blocks against sample calls, deploy them, and walk you through signing to authorize. Author, verify, sign — one step.
+Permission contracts live in `mandates/`. The user authors, reviews, and owns them. For examples by protocol and chain, see `examples/permissions/`.
+```bash
+forge build
+sailor mandate deploy --contract <Name> --attach --sma <SMA>
+```
+Registration requires the owner to sign in the browser. If the wrong wallet is connected, the CLI rejects it.
+## Stage 4 — Run
+Your agent starts executing within its mandate — locally on a schedule or via GitHub Actions. No per-transaction confirmation. The mandate is the authorization.
+```bash
+sailor run           # local, continuous
+sailor run --once    # single tick — confirm it works before automating
+```
+For GitHub Actions: push repo, add `RPC_URL` and `SAIL_PASSPHRASE` as secrets. The scaffolded workflow at `.github/workflows/agent-tick.yml` runs on a schedule.
+## Stage 5 — Extend
+I can set up notifications (Telegram, email, or other) for runs and transactions, and build you a custom dashboard tailored to your strategy — a price chart and portfolio view for a trading agent, health-factor and yield for a lending agent.
+These are things the coding assistant builds on request — not Sailor features. Raise them once the agent is live; build on request.
+## Signing (for custom runners)
+Use `buildDispatchSignature` from `@sail.money/sdk` — it reads the on-chain `DISPATCH_TYPEHASH` and builds the correct typed data. Never hand-roll the EIP-712 struct or hardcode the dispatch model.
+## What NOT to do
+- Do not present the welcome and immediately launch the UI — wait for the second "start"
+- Do not describe, mention, or present any code in `src/` or `examples/` as the user's strategy — treat Stage 2 as a blank slate; ask what they want
+- Do not ask a running agent to confirm individual dispatches within its mandate
+- Do not put an owner key in the terminal — owner signing is browser-only
+- Do not hand-roll dispatch EIP-712 signatures — use `buildDispatchSignature`
+- Do not hardcode the dispatch model — detect it on-chain
+- Do not present example permissions as audited or as a supported menu
+- Do not commit `SAIL_PASSPHRASE` or private keys

package/templates/default/README.md ADDED Viewed

@@ -0,0 +1,16 @@
+# Sail Protocol Agent
+A blank Sail Protocol agent project. Open this folder in your AI coding assistant and say:
+> start
+Your assistant will walk you through every step — chain selection, SMA deployment, strategy design, mandate authoring, and automation.
+## Project layout
+- `src/agent.ts` — your agent's tick loop (implement your strategy here)
+- `src/mandate.ts` — your strategy parameters and contract addresses
+- `mandates/` — Foundry workspace for your IPermission contracts
+- `examples/dca/` — worked reference: DCA (USDC→WETH) on Base via Uniswap V3
+- `examples/permissions/` — protocol-specific permission examples
+- `.sail/` — local project state (keys, account, activity log)

package/templates/default/examples/dca/README.md ADDED Viewed

@@ -0,0 +1,16 @@
+# DCA reference example
+**Reference only — not your strategy.** This shows a complete worked implementation of a dollar-cost-averaging agent (USDC → WETH via Uniswap V3 on Base). Consult it for patterns when authoring your own strategy in `src/`.
+## What it shows
+| File | Purpose |
+|---|---|
+| `mandate.ts` | Token addresses, swap parameters, and contract addresses for Base mainnet |
+| `agent.ts` | Full tick loop: check balance → approve if needed → quote → swap with slippage protection |
+## How to use it
+In Stage 2 (strategy), when you describe what you want, your assistant will adapt these patterns for your protocol, chain, and parameters — not copy them as-is.
+The on-chain permission contract that authorizes these dispatches must be authored separately (Stage 3). The agent code here is only the intent-building side; the mandate enforces the on-chain bounds.