@cargo-ai/cdk 0.1.1

package/templates/full/apps/dashboard/package.json

@@ -0,0 +1,15 @@
+{
+  "name": "dashboard",
+  "private": true,
+  "type": "module",
+  "scripts": {
+    "build": "vite build"
+  },
+  "dependencies": {
+    "react": "^18.3.1",
+    "react-dom": "^18.3.1"
+  },
+  "devDependencies": {
+    "vite": "^5.4.0"
+  }
+}

package/templates/full/apps/dashboard/src/main.tsx

@@ -0,0 +1,12 @@
+import { StrictMode } from "react";
+import { createRoot } from "react-dom/client";
+
+function App() {
+  return <h1>Pipeline Dashboard</h1>;
+}
+
+createRoot(document.getElementById("root")!).render(
+  <StrictMode>
+    <App />
+  </StrictMode>,
+);

package/templates/full/apps/dashboard/tsconfig.json

@@ -0,0 +1,13 @@
+{
+  "compilerOptions": {
+    "target": "ES2022",
+    "lib": ["ES2022", "DOM", "DOM.Iterable"],
+    "module": "ESNext",
+    "moduleResolution": "Bundler",
+    "jsx": "react-jsx",
+    "strict": true,
+    "skipLibCheck": true,
+    "noEmit": true
+  },
+  "include": ["src"]
+}

package/templates/full/apps/dashboard.ts

@@ -0,0 +1,9 @@
+import { defineApp } from "@cargo-ai/cdk";
+
+// A hosted Cargo app, deployed from a Vite app directory. On deploy the
+// reconciler uploads the bundle and the backend builds + promotes it. The live
+// URL is available as `dashboard.url`.
+export const dashboard = defineApp("dashboard", {
+  path: new URL("./dashboard", import.meta.url).pathname,
+  description: "Pipeline overview for the sales team.",
+});

package/templates/full/connectors/hubspot.ts

@@ -0,0 +1,12 @@
+import { defineConnector, secret } from "@cargo-ai/cdk";
+
+// A data-source connector. Creating it auto-creates a dataset, which data models
+// source from (via `dataset: hubspot`). HubSpot's config is a discriminated
+// union — a Private App access token (here) or OAuth refresh token. `secret()`
+// reads the value from the environment at deploy time and keeps it out of the
+// content hash, so rotating the token doesn't read as drift.
+
+export const hubspot = defineConnector("hubspot", {
+  integration: "hubspot",
+  config: { method: "privateApp", accessToken: secret("HUBSPOT_API_KEY") },
+});

package/templates/full/connectors/openai.ts

@@ -0,0 +1,9 @@
+import { defineConnector } from "@cargo-ai/cdk";
+
+// The LLM provider connector. OAuth/key-based connectors that can't be declared
+// in code use `adopt: true` — the reconciler links the existing authenticated
+// connector by slug instead of creating one. Agents reference it by handle: `openai`.
+export const openai = defineConnector("open_ai", {
+  integration: "openAi",
+  adopt: true,
+});

package/templates/full/context/context.ts

@@ -0,0 +1,7 @@
+import { defineContext } from "@cargo-ai/cdk";
+
+// The workspace's context repository (its GTM knowledge base) as code. `dir`
+// syncs this folder's markdown/MDX into the repo on deploy — additive, so files
+// added in the UI are left in place. Edit a doc and it re-syncs; new `.md`/`.mdx`
+// files are picked up automatically.
+export const context = defineContext({ dir: "context" });

package/templates/full/context/icp.md

@@ -0,0 +1,22 @@
+---
+title: Ideal Customer Profile
+tags: [icp, targeting]
+---
+
+# Ideal Customer Profile
+
+B2B SaaS companies, **50–500 employees**, with a dedicated revenue/GTM team.
+
+## Firmographics
+
+- Industry: SaaS, fintech, developer tools
+- Region: North America + Western Europe
+- Signals: recent funding, hiring for sales/RevOps, using a modern CRM
+
+## Qualifying questions
+
+1. Do they run outbound today?
+2. Is there an owner for GTM data quality?
+3. Are they enriching or scoring leads already?
+
+Related: [[personas/head-of-growth]]

package/templates/full/context/personas/head-of-growth.md

@@ -0,0 +1,26 @@
+---
+title: Head of Growth
+tags: [persona]
+---
+
+# Persona — Head of Growth
+
+The economic buyer for a GTM automation platform.
+
+## Goals
+
+- Predictable pipeline from outbound + inbound
+- Clean, enriched, deduplicated CRM data
+- Fast experimentation on sequences and scoring
+
+## Pains
+
+- Reps waste time on manual research and data entry
+- Lead data is stale, incomplete, or duplicated
+- No single place to encode GTM playbooks
+
+## Message
+
+"Encode your GTM motion once — enrichment, scoring, routing — and let it run."
+
+Fits: [[../icp]]

package/templates/full/files/playbook.md

@@ -0,0 +1,19 @@
+# SDR Playbook
+
+## Qualification
+
+A lead is **hot** when all of the following hold:
+
+- Work email verified
+- Company has 50+ employees
+- Title contains one of: VP, Director, Head, Chief
+
+## Routing
+
+- Hot leads → notify `#sales` in Slack within 5 minutes.
+- Warm leads → enqueue for nurture sequence.
+- Cold leads → enrich and re-score weekly.
+
+## Tone
+
+Be concise, specific, and never overpromise.

package/templates/full/files/playbook.ts

@@ -0,0 +1,8 @@
+import { defineFile } from "@cargo-ai/cdk";
+
+// A content file uploaded from a local path. The content is read + hashed at
+// define time, so editing playbook.md shows as drift on the next deploy.
+export const playbook = defineFile("playbook", {
+  path: new URL("./playbook.md", import.meta.url).pathname,
+  name: "SDR Playbook",
+});

package/templates/full/folders/crm.ts

@@ -0,0 +1,14 @@
+import { defineFolder } from "@cargo-ai/cdk";
+
+// Folders organize resources and are per-kind, so a "models" folder and an
+// "agents" folder are separate resources. Other resources reference them via
+// their `folder`.
+export const modelsFolder = defineFolder("crm-models", {
+  kind: "model",
+  name: "CRM",
+});
+
+export const agentsFolder = defineFolder("crm-agents", {
+  kind: "agent",
+  name: "CRM",
+});

package/templates/full/mcp/crm.ts

@@ -0,0 +1,15 @@
+import { defineMcpServer } from "@cargo-ai/cdk";
+
+import { sdr } from "../agents/sdr";
+import { contacts } from "../models/contacts";
+import { enrich } from "../tools/enrich";
+
+// An MCP server bundles tools, agents, and data models behind one MCP endpoint.
+// Each is referenced by handle (bare, or `{ ref, …options }` for options), so
+// the reconciler resolves each to its deployed action/resource.
+export const crmServer = defineMcpServer("crm", {
+  description: "CRM tools and data for assistants.",
+  tools: [enrich],
+  agents: [sdr],
+  models: [{ ref: contacts, readOnly: true }],
+});

package/templates/full/models/contacts.ts

@@ -0,0 +1,15 @@
+import { defineModel } from "@cargo-ai/cdk";
+
+import { hubspot } from "../connectors/hubspot";
+import { modelsFolder } from "../folders/crm";
+
+// A data model: a table sourced from a connector's dataset by an extractor.
+// `dataset` wires it to the connector (deployed first, its dataset injected);
+// `folder` places it in the CRM models folder.
+export const contacts = defineModel("contacts", {
+  dataset: hubspot,
+  extractSlug: "fetchRecords",
+  config: { objectType: "contacts", columnSelectionMode: "all" },
+  folder: modelsFolder,
+  schedule: { type: "cron", cron: "0 * * * *" }, // refresh hourly
+});

package/templates/full/package.json

@@ -0,0 +1,17 @@
+{
+  "name": "__APP_NAME__",
+  "private": true,
+  "type": "module",
+  "scripts": {
+    "types": "cargo-ai cdk types",
+    "plan": "cargo-ai cdk plan",
+    "deploy": "cargo-ai cdk deploy"
+  },
+  "dependencies": {
+    "@cargo-ai/cdk": "^0.1.0",
+    "zod": "^4.4.3"
+  },
+  "devDependencies": {
+    "typescript": "^5.3.2"
+  }
+}

package/templates/full/plays/onboarding.ts

@@ -0,0 +1,41 @@
+import { definePlay, defineWorkflow } from "@cargo-ai/cdk";
+import { z } from "zod";
+
+import { contacts } from "../models/contacts";
+import { enrich } from "../tools/enrich";
+
+// The per-row automation run for each contact the play emits — deployed as the
+// play's release. `defineWorkflow` compiles the logic; it is never executed at
+// build time.
+//
+// `uses` forward-references the `enrich` tool by handle, so the body runs it for
+// each row (`uses.enrich(...)`) and the CDK wires the deploy dependency. `ai(...)`
+// then drafts a welcome, interpolating the tool's result.
+const onboardRow = defineWorkflow(
+  "onboard-contact",
+  {
+    input: z.object({ email: z.string() }),
+    output: z.object({ welcomed: z.boolean(), message: z.string() }),
+    uses: { enrich },
+  },
+  ({ input, uses, ai }) => {
+    // `uses.enrich(...)` is typed to the tool's output, so `enriched.company`
+    // is a `Ref<string>` — member access is checked.
+    const enriched = uses.enrich({ email: input.email });
+
+    const message = ai(
+      `Draft a one-line welcome message for ${input.email} at ${enriched.company}.`,
+    );
+    return { welcomed: true, message };
+  },
+);
+
+// A play runs over a data model and emits runs as its rows change. Here it fires
+// when a contact is added or updated, running `onboardRow` for each.
+export const onboarding = definePlay("onboarding", {
+  model: contacts,
+  workflow: onboardRow,
+  changeKinds: ["added", "updated"],
+  runCreationRule: "always",
+  schedule: { type: "watch" },
+});

package/templates/full/tools/enrich.ts

@@ -0,0 +1,34 @@
+import { defineTool, defineWorkflow } from "@cargo-ai/cdk";
+import { z } from "zod";
+
+import { enricher } from "../agents/enricher";
+
+// A tool is backed by a workflow. `defineWorkflow` compiles the logic; `defineTool`
+// creates the tool + deploys that workflow as its release.
+//
+// `uses` forward-references other resources by handle — here the `enricher` agent.
+// The body calls it as `uses.enricher(...)`, and because the handle carries a
+// deferred `uuid` token, the CDK both orders the deploy (enricher first) and
+// injects the real uuid into the emitted node. The body is parsed and lowered to
+// workflow nodes — never executed at build time.
+const enrichFlow = defineWorkflow(
+  "enrich-contact",
+  {
+    input: z.object({ email: z.string() }),
+    output: z.object({ company: z.string(), enriched: z.boolean() }),
+    uses: { enricher },
+  },
+  ({ input, uses }) => {
+    const company = uses.enricher({
+      prompt: `Which company owns the email domain of ${input.email}? Reply with just the company name.`,
+    });
+    return { company, enriched: true };
+  },
+);
+
+export const enrich = defineTool("enrich", {
+  workflow: enrichFlow,
+  description: "Enrich a contact with firmographic data.",
+  emojiSlug: "mag",
+  triggers: [{ cron: "0 9 * * 1", name: "Weekly enrichment" }],
+});

package/templates/full/tsconfig.json

@@ -0,0 +1,17 @@
+{
+  "compilerOptions": {
+    "target": "ES2022",
+    "module": "ESNext",
+    "moduleResolution": "Bundler",
+    "strict": true,
+    "skipLibCheck": true,
+    "noEmit": true,
+    "types": []
+  },
+  // The resource files plus `.cargo-ai` (types generated by `cargo-ai cdk types`)
+  // — including it here is what makes defineConnector/defineModel config typed.
+  // The app/worker bundle sub-projects are self-contained (own tsconfig), so they
+  // are excluded from this project.
+  "include": ["**/*.ts", ".cargo-ai/**/*.d.ts"],
+  "exclude": ["node_modules", "apps/*/**", "workers/*/**"]
+}

package/templates/full/workers/webhook/index.js

@@ -0,0 +1,12 @@
+// A worker bundle is deployed *built*: the hosting build runs `npm ci` then
+// esbuild's this `index.js` (no TS transpile). Author in TS with
+// `createWorker` from @cargo-ai/worker-sdk if you like, but `defineWorker` must
+// point at a directory whose root has the built `index.js` plus `manifest.json`,
+// `package.json` and `package-lock.json`.
+export default {
+  fetch() {
+    return new Response(JSON.stringify({ accepted: true }), {
+      headers: { "content-type": "application/json" },
+    });
+  },
+};

package/templates/full/workers/webhook/manifest.json

@@ -0,0 +1 @@
+{ "outboundAllowlist": [] }

package/templates/full/workers/webhook/package-lock.json

@@ -0,0 +1,12 @@
+{
+  "name": "webhook",
+  "version": "1.0.0",
+  "lockfileVersion": 3,
+  "requires": true,
+  "packages": {
+    "": {
+      "name": "webhook",
+      "version": "1.0.0"
+    }
+  }
+}

package/templates/full/workers/webhook/package.json

@@ -0,0 +1,6 @@
+{
+  "name": "webhook",
+  "version": "1.0.0",
+  "private": true,
+  "type": "module"
+}

package/templates/full/workers/webhook.ts

@@ -0,0 +1,13 @@
+import { defineWorker } from "@cargo-ai/cdk";
+
+// `defineWorker` is the *resource* — the hosted worker slot. Its `path` points to
+// a *built* bundle directory: a root `index.js` (the hosting build runs `npm ci`
+// then esbuild — no TS transpile), plus `manifest.json`, `package.json` and
+// `package-lock.json`. The CDK validates those exist at define time. Author in TS
+// with `createWorker` from @cargo-ai/worker-sdk and build to `index.js`. On
+// deploy the reconciler uploads the bundle, waits for the build, and promotes it.
+// The live URL is available as `webhook.url`.
+export const webhook = defineWorker("webhook", {
+  path: new URL("./webhook", import.meta.url).pathname,
+  description: "Receives inbound lead webhooks.",
+});