@elevasis/ui 2.25.6 → 2.26.0

package/dist/chunk-ONFKASZI.js

@@ -0,0 +1,2004 @@
+import { SemanticIcon } from './chunk-KEFWANZY.js';
+import { Stack, Group, Title, Text, Box, Divider, useTree, Tree, UnstyledButton, TextInput } from '@mantine/core';
+import { jsx, jsxs, Fragment } from 'react/jsx-runtime';
+import { useMemo, useState, useRef, useEffect } from 'react';
+import { useClipboard } from '@mantine/hooks';
+import { IconChevronDown, IconChevronRight, IconX, IconSearch, IconCheck, IconCopy } from '@tabler/icons-react';
+
+// src/knowledge/iconTokens.ts
+var KNOWLEDGE_ICON_TOKEN_BY_KIND = {
+  playbook: "knowledge.playbook",
+  strategy: "knowledge.strategy",
+  reference: "knowledge.reference"
+};
+function getKnowledgeIconToken(node) {
+  return node.icon ?? KNOWLEDGE_ICON_TOKEN_BY_KIND[node.kind];
+}
+
+// ../core/src/knowledge/queries.ts
+function buildKnowledgeSourceIdMap(graph) {
+  const map = /* @__PURE__ */ new Map();
+  for (const node of graph.nodes) {
+    if (node.kind === "knowledge" && node.sourceId) {
+      map.set(node.id, node.sourceId);
+    }
+  }
+  return map;
+}
+function byFeature(graph, featureId, knowledgeNodes) {
+  const targetGraphNodeId = `feature:${featureId}`;
+  const governingKnowledgeNodeIds = /* @__PURE__ */ new Set();
+  for (const edge of graph.edges) {
+    if (edge.kind === "governs" && edge.targetId === targetGraphNodeId && edge.sourceId.startsWith("knowledge:")) {
+      governingKnowledgeNodeIds.add(edge.sourceId);
+    }
+  }
+  const sourceIdMap = buildKnowledgeSourceIdMap(graph);
+  const matchingOmIds = /* @__PURE__ */ new Set();
+  for (const graphNodeId of governingKnowledgeNodeIds) {
+    const omId = sourceIdMap.get(graphNodeId);
+    if (omId) matchingOmIds.add(omId);
+  }
+  return knowledgeNodes.filter((n) => matchingOmIds.has(n.id));
+}
+function byKind(_graph, kind, knowledgeNodes) {
+  return knowledgeNodes.filter((n) => n.kind === kind);
+}
+var KIND_CHIP_TONE_STYLES = {
+  subtle: {
+    backgroundColor: "var(--color-surface-hover)",
+    borderColor: "var(--color-border)",
+    color: "var(--color-text-dimmed)"
+  },
+  primary: {
+    backgroundColor: "var(--surface-primary-subtle)",
+    borderColor: "color-mix(in srgb, var(--color-primary) 28%, var(--color-border))",
+    color: "var(--color-primary)"
+  },
+  muted: {
+    backgroundColor: "var(--color-surface)",
+    borderColor: "var(--color-border)",
+    color: "var(--color-text-subtle)"
+  }
+};
+function KindChip({ kind, tone = "subtle", style, ...spanProps }) {
+  return /* @__PURE__ */ jsx(
+    "span",
+    {
+      ...spanProps,
+      "data-kind-chip": true,
+      "data-tone": tone,
+      style: {
+        display: "inline-flex",
+        alignItems: "center",
+        width: "fit-content",
+        maxWidth: "100%",
+        padding: "2px 8px",
+        border: "1px solid",
+        borderRadius: "var(--mantine-radius-sm)",
+        fontFamily: "var(--mantine-font-family)",
+        fontSize: "var(--mantine-font-size-xs)",
+        fontWeight: 600,
+        lineHeight: 1.2,
+        letterSpacing: 0,
+        whiteSpace: "nowrap",
+        transition: "background-color var(--duration-fast) var(--easing), border-color var(--duration-fast) var(--easing)",
+        ...KIND_CHIP_TONE_STYLES[tone],
+        ...style
+      },
+      children: kind
+    }
+  );
+}
+function NodeHeader({
+  title,
+  kind,
+  tone = "primary",
+  iconToken,
+  description,
+  updatedAt,
+  rightSection
+}) {
+  return /* @__PURE__ */ jsxs(Stack, { gap: "xs", children: [
+    /* @__PURE__ */ jsxs(Group, { gap: "xs", align: "flex-start", wrap: "nowrap", children: [
+      iconToken && /* @__PURE__ */ jsx(
+        SemanticIcon,
+        {
+          token: iconToken,
+          fallbackKind: "knowledge",
+          size: 22,
+          style: { color: "var(--color-primary)", marginTop: 5 }
+        }
+      ),
+      /* @__PURE__ */ jsx(Title, { order: 3, style: { flex: 1, minWidth: 0, color: "var(--color-text)" }, children: title }),
+      /* @__PURE__ */ jsx(KindChip, { kind, tone, style: { flexShrink: 0, marginTop: 4 } }),
+      rightSection
+    ] }),
+    description && /* @__PURE__ */ jsx(Text, { size: "sm", c: "dimmed", style: { lineHeight: 1.5 }, children: description }),
+    updatedAt && /* @__PURE__ */ jsxs(Text, { size: "xs", c: "dimmed", style: { opacity: 0.7 }, children: [
+      "Updated ",
+      updatedAt
+    ] })
+  ] });
+}
+function EdgeChip({ id, onClick }) {
+  return /* @__PURE__ */ jsx(
+    "div",
+    {
+      role: onClick ? "button" : void 0,
+      tabIndex: onClick ? 0 : void 0,
+      onClick,
+      onKeyDown: onClick ? (e) => (e.key === "Enter" || e.key === " ") && onClick() : void 0,
+      style: {
+        display: "inline-flex",
+        alignItems: "center",
+        padding: "2px 8px",
+        borderRadius: "var(--mantine-radius-sm)",
+        backgroundColor: "var(--color-surface)",
+        border: "1px solid var(--color-border)",
+        fontSize: "var(--mantine-font-size-xs)",
+        color: onClick ? "var(--color-primary)" : "var(--color-text-subtle)",
+        cursor: onClick ? "pointer" : "default",
+        fontFamily: "var(--mantine-font-family-monospace)",
+        width: "fit-content",
+        background: "none"
+      },
+      children: id
+    }
+  );
+}
+function EdgeGroup({ label, ids, onNavigateToNode }) {
+  return /* @__PURE__ */ jsxs(Stack, { gap: 4, children: [
+    /* @__PURE__ */ jsx(Text, { size: "xs", c: "dimmed", fw: 500, children: label }),
+    ids.map((id) => /* @__PURE__ */ jsx(EdgeChip, { id, onClick: onNavigateToNode ? () => onNavigateToNode(id) : void 0 }, id))
+  ] });
+}
+function knowledgeNodeIdFromGraphNode(graphNode, graphNodeId) {
+  if (graphNode?.sourceId) return graphNode.sourceId;
+  return graphNodeId.startsWith("knowledge:") ? graphNodeId.slice("knowledge:".length) : graphNodeId;
+}
+function RelatedKnowledgeSection({
+  nodeId,
+  graph,
+  knowledgeNodes,
+  onNavigateToNode
+}) {
+  const knowledgeById = new Map(knowledgeNodes.map((node) => [node.id, node]));
+  const cards = graph.edges.filter((edge) => edge.kind === "governs" && edge.targetId === nodeId).map((edge) => {
+    const graphNode = graph.nodes.find((node) => node.id === edge.sourceId && node.kind === "knowledge");
+    const knowledgeNode = knowledgeById.get(knowledgeNodeIdFromGraphNode(graphNode, edge.sourceId));
+    return knowledgeNode ? { graphNodeId: edge.sourceId, node: knowledgeNode } : null;
+  }).filter((card) => card !== null);
+  if (cards.length === 0) return null;
+  return /* @__PURE__ */ jsxs(Stack, { gap: "xs", "data-related-knowledge-section": true, children: [
+    /* @__PURE__ */ jsx(Text, { size: "xs", fw: 600, tt: "uppercase", c: "dimmed", style: { letterSpacing: "0.05em" }, children: "Governing Knowledge" }),
+    /* @__PURE__ */ jsx(Stack, { gap: "xs", children: cards.map(({ graphNodeId, node }) => /* @__PURE__ */ jsx(
+      Box,
+      {
+        component: onNavigateToNode ? "button" : "article",
+        type: onNavigateToNode ? "button" : void 0,
+        onClick: onNavigateToNode ? () => onNavigateToNode(graphNodeId) : void 0,
+        style: {
+          display: "block",
+          width: "100%",
+          padding: "var(--mantine-spacing-sm)",
+          border: "1px solid var(--color-border)",
+          borderRadius: "var(--mantine-radius-sm)",
+          background: "var(--color-surface)",
+          color: "var(--color-text)",
+          textAlign: "left",
+          cursor: onNavigateToNode ? "pointer" : "default",
+          font: "inherit"
+        },
+        children: /* @__PURE__ */ jsxs(Stack, { gap: 4, children: [
+          /* @__PURE__ */ jsxs(Group, { gap: "xs", align: "flex-start", wrap: "nowrap", children: [
+            /* @__PURE__ */ jsx(
+              SemanticIcon,
+              {
+                token: getKnowledgeIconToken(node),
+                fallbackKind: node.kind,
+                size: 16,
+                style: { color: "var(--color-text-subtle)", marginTop: 1 }
+              }
+            ),
+            /* @__PURE__ */ jsx(Text, { size: "sm", fw: 600, style: { flex: 1, minWidth: 0, lineHeight: 1.35 }, children: node.title }),
+            /* @__PURE__ */ jsx(KindChip, { kind: node.kind, tone: "muted", style: { flexShrink: 0 } })
+          ] }),
+          /* @__PURE__ */ jsx(Text, { size: "xs", c: "dimmed", style: { lineHeight: 1.45 }, children: node.summary })
+        ] })
+      },
+      node.id
+    )) })
+  ] });
+}
+function relatedIds(graph, nodeId, edgeKind, direction, targetKind) {
+  return graph.edges.filter(
+    (edge) => direction === "outgoing" ? edge.kind === edgeKind && edge.sourceId === nodeId : edge.kind === edgeKind && edge.targetId === nodeId
+  ).map((edge) => direction === "outgoing" ? edge.targetId : edge.sourceId).filter((id) => {
+    if (!targetKind) return true;
+    return graph.nodes.find((node) => node.id === id)?.kind === targetKind;
+  });
+}
+function EdgeRelationshipGroup({ nodeId, graph, knowledgeNodes, onNavigateToNode }) {
+  const subFeatures = relatedIds(graph, nodeId, "contains", "outgoing", "feature");
+  const resourcesUsed = relatedIds(graph, nodeId, "uses", "outgoing", "resource");
+  const entities = relatedIds(graph, nodeId, "operates-on", "outgoing", "entity");
+  const governedTargets = relatedIds(graph, nodeId, "governs", "outgoing");
+  const governingKnowledge = relatedIds(graph, nodeId, "governs", "incoming", "knowledge");
+  const hasRelationships = subFeatures.length > 0 || resourcesUsed.length > 0 || entities.length > 0 || governedTargets.length > 0 || governingKnowledge.length > 0;
+  if (!hasRelationships) return null;
+  return /* @__PURE__ */ jsxs(Stack, { gap: "xs", "data-edge-relationship-group": true, children: [
+    /* @__PURE__ */ jsx(Divider, {}),
+    /* @__PURE__ */ jsx(Text, { size: "xs", fw: 600, tt: "uppercase", c: "dimmed", style: { letterSpacing: "0.05em" }, children: "Relationships" }),
+    subFeatures.length > 0 && /* @__PURE__ */ jsx(
+      EdgeGroup,
+      {
+        label: `Sub-features (${subFeatures.length})`,
+        ids: subFeatures,
+        onNavigateToNode
+      }
+    ),
+    resourcesUsed.length > 0 && /* @__PURE__ */ jsx(
+      EdgeGroup,
+      {
+        label: `Resources used (${resourcesUsed.length})`,
+        ids: resourcesUsed,
+        onNavigateToNode
+      }
+    ),
+    entities.length > 0 && /* @__PURE__ */ jsx(EdgeGroup, { label: `Entities (${entities.length})`, ids: entities, onNavigateToNode }),
+    governedTargets.length > 0 && /* @__PURE__ */ jsx(
+      EdgeGroup,
+      {
+        label: `Governs (${governedTargets.length})`,
+        ids: governedTargets,
+        onNavigateToNode
+      }
+    ),
+    governingKnowledge.length > 0 && (knowledgeNodes ? /* @__PURE__ */ jsx(
+      RelatedKnowledgeSection,
+      {
+        nodeId,
+        graph,
+        knowledgeNodes,
+        onNavigateToNode
+      }
+    ) : /* @__PURE__ */ jsx(
+      EdgeGroup,
+      {
+        label: `Governing knowledge (${governingKnowledge.length})`,
+        ids: governingKnowledge,
+        onNavigateToNode
+      }
+    ))
+  ] });
+}
+var PRESENTATION_METADATA_KEYS = /* @__PURE__ */ new Set(["label", "description"]);
+function formatMetadataLabel(key) {
+  return key.replace(/([a-z0-9])([A-Z])/g, "$1 $2").replace(/^./, (char) => char.toUpperCase());
+}
+function NodeMetadataFooter({ node, title = "Technical metadata" }) {
+  const entries = Object.entries(node).filter(
+    ([key, value]) => !PRESENTATION_METADATA_KEYS.has(key) && value !== void 0 && value !== null && typeof value !== "object"
+  );
+  if (entries.length === 0) return null;
+  return /* @__PURE__ */ jsxs(
+    Box,
+    {
+      component: "details",
+      style: {
+        borderTop: "1px solid var(--color-border)",
+        paddingTop: "var(--mantine-spacing-sm)"
+      },
+      children: [
+        /* @__PURE__ */ jsx(
+          Box,
+          {
+            component: "summary",
+            style: {
+              cursor: "pointer",
+              color: "var(--color-text-dimmed)",
+              fontSize: "var(--mantine-font-size-xs)",
+              fontWeight: 600,
+              letterSpacing: "0.05em",
+              textTransform: "uppercase"
+            },
+            children: title
+          }
+        ),
+        /* @__PURE__ */ jsx(Stack, { gap: 4, style: { paddingTop: "var(--mantine-spacing-xs)" }, children: entries.map(([key, value]) => /* @__PURE__ */ jsx(KeyField, { label: formatMetadataLabel(key), value: String(value) }, key)) })
+      ]
+    }
+  );
+}
+function NodeDescribeShell({ header, content, relationships, footer }) {
+  return /* @__PURE__ */ jsxs(Stack, { gap: "md", style: { padding: "var(--mantine-spacing-md)", width: "100%" }, children: [
+    header,
+    content && /* @__PURE__ */ jsxs(Fragment, { children: [
+      header && /* @__PURE__ */ jsx(Divider, {}),
+      content
+    ] }),
+    relationships,
+    footer
+  ] });
+}
+function KeyField({ label, value }) {
+  return /* @__PURE__ */ jsxs(Group, { gap: "xs", align: "baseline", children: [
+    /* @__PURE__ */ jsx(Text, { size: "xs", fw: 500, c: "dimmed", style: { minWidth: 96 }, children: label }),
+    /* @__PURE__ */ jsx(Text, { size: "sm", style: { fontFamily: "var(--mantine-font-family-monospace)" }, children: value })
+  ] });
+}
+var FEATURE_PREFIX = "feat:";
+var LEAF_PREFIX = "leaf:";
+var FOLDER_PREFIX = "folder:";
+var GROUP_THRESHOLD = 8;
+var FOLDER_ORDER = [
+  "campaigns",
+  "pipeline",
+  "targeting",
+  "channels",
+  "proof",
+  "references",
+  "playbooks",
+  "strategies"
+];
+var FOLDER_LABELS = {
+  campaigns: "Campaigns",
+  pipeline: "Pipeline",
+  targeting: "Targeting and Strategy",
+  channels: "Channels",
+  proof: "Proof",
+  references: "References",
+  playbooks: "Playbooks",
+  strategies: "Strategies"
+};
+function toBareFeatureId(graphNodeId) {
+  return graphNodeId.startsWith("feature:") ? graphNodeId.slice("feature:".length) : graphNodeId;
+}
+function topLevelFeatureIds(allBareIds) {
+  return allBareIds.filter((id) => !id.includes("."));
+}
+function childFeatureIds(allBareIds, parentId) {
+  const prefix = `${parentId}.`;
+  return allBareIds.filter((id) => id.startsWith(prefix) && !id.slice(prefix.length).includes("."));
+}
+function featureHasKnowledgeDescendant(bareId, allBareIds, graph, knowledgeNodes) {
+  if (byFeature(graph, bareId, knowledgeNodes).length > 0) return true;
+  return childFeatureIds(allBareIds, bareId).some(
+    (childId) => featureHasKnowledgeDescendant(childId, allBareIds, graph, knowledgeNodes)
+  );
+}
+function buildFeatureMetaMap(graph) {
+  const map = {};
+  for (const node of graph.nodes) {
+    if (node.kind === "feature") {
+      map[toBareFeatureId(node.id)] = { label: node.label, icon: node.icon, node };
+    }
+  }
+  return map;
+}
+function getKnowledgeReadCommand(nodeId) {
+  return `/knowledge read ${nodeId}`;
+}
+function getKnowledgeReadCommands(nodeIds) {
+  return [...new Set(nodeIds)].map(getKnowledgeReadCommand).join("\n");
+}
+function getKnowledgeReadFeatureFolderCommand(bareFeatureId) {
+  return `/knowledge read-folder feature:${bareFeatureId}`;
+}
+function getKnowledgeFolderKey(node) {
+  const key = `${node.id} ${node.title}`.toLowerCase();
+  if (/\b(stage|booking|discovery|pipeline|communications?)\b/.test(key)) return "pipeline";
+  if (/\b(upwork scanning|youtube|obs|recording|reddit|social)\b/.test(key)) return "channels";
+  if (/\b(testimonials?|case stud|proof)\b/.test(key)) return "proof";
+  if (/\b(target|personalization|vertical|calibration|query|research|strategy)\b/.test(key)) return "targeting";
+  if (/\b(outreach|campaign|copy|handoff|bounce|reply|lead-gen playbook)\b/.test(key)) return "campaigns";
+  if (node.kind === "reference") return "references";
+  if (node.kind === "strategy") return "strategies";
+  return "playbooks";
+}
+function sortFolderKeys(left, right) {
+  const leftIndex = FOLDER_ORDER.indexOf(left);
+  const rightIndex = FOLDER_ORDER.indexOf(right);
+  if (leftIndex === -1 && rightIndex === -1) return left.localeCompare(right);
+  if (leftIndex === -1) return 1;
+  if (rightIndex === -1) return -1;
+  return leftIndex - rightIndex;
+}
+function createKnowledgeLeaf(bareId, node) {
+  return {
+    value: `${LEAF_PREFIX}${bareId}::${node.id}`,
+    label: node.title,
+    nodeType: "leaf",
+    knowledgeNodeId: node.id,
+    knowledgeNodeIds: [node.id]
+  };
+}
+function createKnowledgeLeaves(bareId, nodes) {
+  if (nodes.length < GROUP_THRESHOLD) {
+    return nodes.map((node) => createKnowledgeLeaf(bareId, node));
+  }
+  const grouped = /* @__PURE__ */ new Map();
+  for (const node of nodes) {
+    const folderKey = getKnowledgeFolderKey(node);
+    const folderNodes = grouped.get(folderKey) ?? [];
+    folderNodes.push(node);
+    grouped.set(folderKey, folderNodes);
+  }
+  return [...grouped.entries()].sort(([left], [right]) => sortFolderKeys(left, right)).map(([folderKey, folderNodes]) => ({
+    value: `${FOLDER_PREFIX}${bareId}::${folderKey}`,
+    label: FOLDER_LABELS[folderKey] ?? folderKey,
+    nodeType: "folder",
+    icon: "knowledge.playbook",
+    knowledgeNodeIds: folderNodes.map((node) => node.id),
+    children: folderNodes.map((node) => createKnowledgeLeaf(bareId, node))
+  }));
+}
+function collectKnowledgeNodeIds(node) {
+  if (node.knowledgeNodeIds) return node.knowledgeNodeIds;
+  return (node.children ?? []).flatMap(collectKnowledgeNodeIds);
+}
+function buildFeatureTreeNode(bareId, allBareIds, featureMetaMap, graph, knowledgeNodes) {
+  const governing = byFeature(graph, bareId, knowledgeNodes);
+  const childIds = childFeatureIds(allBareIds, bareId);
+  const childFeatureNodes = childIds.filter((childId) => featureHasKnowledgeDescendant(childId, allBareIds, graph, knowledgeNodes)).map((childId) => buildFeatureTreeNode(childId, allBareIds, featureMetaMap, graph, knowledgeNodes));
+  const knowledgeLeaves = createKnowledgeLeaves(bareId, governing);
+  const children = [...childFeatureNodes, ...knowledgeLeaves];
+  const meta = featureMetaMap[bareId];
+  return {
+    value: `${FEATURE_PREFIX}${bareId}`,
+    label: meta?.label ?? bareId,
+    nodeType: "feature",
+    icon: meta?.icon,
+    knowledgeNodeIds: children.flatMap(collectKnowledgeNodeIds),
+    children: children.length > 0 ? children : void 0
+  };
+}
+function collectExpandableValues(nodes, acc = {}) {
+  for (const node of nodes) {
+    if (typeof node.value === "string" && (node.value.startsWith(FEATURE_PREFIX) || node.value.startsWith(FOLDER_PREFIX))) {
+      acc[node.value] = true;
+    }
+    if (node.children) {
+      collectExpandableValues(node.children, acc);
+    }
+  }
+  return acc;
+}
+function KnowledgeTree({
+  graph,
+  knowledgeNodes,
+  onSelectNode,
+  onSelectGraphNode,
+  selectedNodeId
+}) {
+  const treeData = useMemo(() => {
+    const featureMetaMap = buildFeatureMetaMap(graph);
+    const allBareIds = Object.keys(featureMetaMap);
+    const topIds = topLevelFeatureIds(allBareIds);
+    return topIds.filter((bareId) => featureHasKnowledgeDescendant(bareId, allBareIds, graph, knowledgeNodes)).map((bareId) => buildFeatureTreeNode(bareId, allBareIds, featureMetaMap, graph, knowledgeNodes));
+  }, [graph, knowledgeNodes]);
+  const initialExpandedState = useMemo(() => collectExpandableValues(treeData), [treeData]);
+  const treeController = useTree({ initialExpandedState });
+  const leafNodeMap = useMemo(() => {
+    const map = /* @__PURE__ */ new Map();
+    for (const node of knowledgeNodes) {
+      for (const graphNode of graph.nodes) {
+        if (graphNode.kind === "feature") {
+          const bareId = toBareFeatureId(graphNode.id);
+          map.set(`${LEAF_PREFIX}${bareId}::${node.id}`, node);
+        }
+      }
+    }
+    return map;
+  }, [graph, knowledgeNodes]);
+  const featureKnowledgeCountMap = useMemo(() => {
+    const counts = /* @__PURE__ */ new Map();
+    for (const graphNode of graph.nodes) {
+      if (graphNode.kind === "feature") {
+        const bareId = toBareFeatureId(graphNode.id);
+        counts.set(bareId, byFeature(graph, bareId, knowledgeNodes).length);
+      }
+    }
+    return counts;
+  }, [graph, knowledgeNodes]);
+  const featureGraphNodeMap = useMemo(() => {
+    const map = /* @__PURE__ */ new Map();
+    for (const graphNode of graph.nodes) {
+      if (graphNode.kind === "feature") {
+        map.set(toBareFeatureId(graphNode.id), graphNode);
+      }
+    }
+    return map;
+  }, [graph]);
+  if (treeData.length === 0) {
+    return /* @__PURE__ */ jsx(Text, { size: "sm", c: "dimmed", style: { padding: "var(--mantine-spacing-md)" }, children: "No features in graph." });
+  }
+  return /* @__PURE__ */ jsx(
+    Tree,
+    {
+      data: treeData,
+      tree: treeController,
+      style: { padding: "var(--mantine-spacing-xs)" },
+      renderNode: ({ node, expanded, hasChildren, elementProps }) => {
+        const value = node.value;
+        const typedNode = node;
+        if (typeof value === "string" && value.startsWith(LEAF_PREFIX)) {
+          const knowledgeNode = leafNodeMap.get(value);
+          if (!knowledgeNode) return null;
+          return /* @__PURE__ */ jsx(
+            KnowledgeLeafRow,
+            {
+              elementProps,
+              knowledgeNode,
+              isActive: knowledgeNode.id === selectedNodeId,
+              onSelectNode
+            }
+          );
+        }
+        if (typeof value === "string" && value.startsWith(FOLDER_PREFIX)) {
+          return /* @__PURE__ */ jsx(
+            DirectoryRow,
+            {
+              elementProps,
+              expanded,
+              hasChildren,
+              label: String(node.label),
+              iconToken: typedNode.icon,
+              count: typedNode.knowledgeNodeIds?.length ?? 0,
+              command: getKnowledgeReadCommands(typedNode.knowledgeNodeIds ?? []),
+              isActive: false
+            }
+          );
+        }
+        const bareId = typeof value === "string" && value.startsWith(FEATURE_PREFIX) ? value.slice(FEATURE_PREFIX.length) : String(value);
+        const count = featureKnowledgeCountMap.get(bareId) ?? 0;
+        const graphNode = featureGraphNodeMap.get(bareId);
+        const isActive = graphNode !== void 0 && (selectedNodeId === graphNode.id || selectedNodeId === graphNode.sourceId || selectedNodeId === bareId);
+        return /* @__PURE__ */ jsx(
+          DirectoryRow,
+          {
+            elementProps,
+            expanded,
+            hasChildren,
+            label: String(node.label),
+            iconToken: typedNode.icon,
+            count,
+            command: getKnowledgeReadFeatureFolderCommand(bareId),
+            isActive,
+            uppercase: true,
+            onSelectGraphNode: graphNode ? () => onSelectGraphNode?.(graphNode) : void 0
+          }
+        );
+      }
+    }
+  );
+}
+function CopyCommandControl({ command, label, visible }) {
+  const clipboard = useClipboard({ timeout: 1500 });
+  if (!command) return null;
+  return /* @__PURE__ */ jsx(
+    "span",
+    {
+      role: "button",
+      tabIndex: 0,
+      "aria-label": label,
+      onClick: (event) => {
+        event.preventDefault();
+        event.stopPropagation();
+        clipboard.copy(command);
+      },
+      onKeyDown: (event) => {
+        if (event.key !== "Enter" && event.key !== " ") return;
+        event.preventDefault();
+        event.stopPropagation();
+        clipboard.copy(command);
+      },
+      style: {
+        display: "inline-flex",
+        alignItems: "center",
+        justifyContent: "center",
+        width: 22,
+        height: 22,
+        flexShrink: 0,
+        opacity: visible ? 1 : 0,
+        pointerEvents: visible ? "auto" : "none",
+        color: clipboard.copied ? "var(--color-primary)" : "var(--color-text-subtle)",
+        transition: "opacity 120ms ease, color 120ms ease"
+      },
+      children: clipboard.copied ? /* @__PURE__ */ jsx(IconCheck, { size: 14 }) : /* @__PURE__ */ jsx(IconCopy, { size: 14 })
+    }
+  );
+}
+function KnowledgeLeafRow({ elementProps, knowledgeNode, isActive, onSelectNode }) {
+  const [hovered, setHovered] = useState(false);
+  return /* @__PURE__ */ jsx(
+    UnstyledButton,
+    {
+      ...elementProps,
+      onMouseEnter: (event) => {
+        elementProps.onMouseEnter?.(event);
+        setHovered(true);
+      },
+      onMouseLeave: (event) => {
+        elementProps.onMouseLeave?.(event);
+        setHovered(false);
+      },
+      onClick: () => onSelectNode(knowledgeNode),
+      style: {
+        ...elementProps.style ?? {},
+        padding: "5px 8px 5px 24px",
+        borderRadius: "var(--mantine-radius-sm)",
+        backgroundColor: isActive ? "color-mix(in srgb, var(--color-primary) 10%, transparent)" : hovered ? "var(--color-surface-hover)" : "transparent",
+        width: "100%",
+        textAlign: "left",
+        display: "block"
+      },
+      children: /* @__PURE__ */ jsxs(Group, { gap: "xs", wrap: "nowrap", children: [
+        /* @__PURE__ */ jsx(
+          SemanticIcon,
+          {
+            token: getKnowledgeIconToken(knowledgeNode),
+            fallbackKind: knowledgeNode.kind,
+            size: 15,
+            style: {
+              color: isActive ? "var(--color-primary)" : hovered ? "var(--color-text)" : "var(--color-text-subtle)"
+            }
+          }
+        ),
+        /* @__PURE__ */ jsx(
+          Text,
+          {
+            size: "sm",
+            c: isActive ? "var(--color-primary)" : hovered ? "var(--color-text)" : void 0,
+            fw: isActive ? 600 : 400,
+            style: { flex: 1, minWidth: 0, overflow: "hidden", textOverflow: "ellipsis", whiteSpace: "nowrap" },
+            children: knowledgeNode.title
+          }
+        ),
+        /* @__PURE__ */ jsx(
+          CopyCommandControl,
+          {
+            command: getKnowledgeReadCommand(knowledgeNode.id),
+            label: "Copy knowledge command",
+            visible: hovered
+          }
+        )
+      ] })
+    }
+  );
+}
+function DirectoryRow({
+  elementProps,
+  expanded,
+  hasChildren,
+  label,
+  iconToken,
+  count,
+  command,
+  isActive,
+  uppercase = false,
+  onSelectGraphNode
+}) {
+  const [hovered, setHovered] = useState(false);
+  return /* @__PURE__ */ jsxs(
+    Group,
+    {
+      ...elementProps,
+      gap: "xs",
+      onMouseEnter: (event) => {
+        elementProps.onMouseEnter?.(event);
+        setHovered(true);
+      },
+      onMouseLeave: (event) => {
+        elementProps.onMouseLeave?.(event);
+        setHovered(false);
+      },
+      onClick: (event) => {
+        elementProps.onClick?.(event);
+        onSelectGraphNode?.();
+      },
+      style: {
+        ...elementProps.style ?? {},
+        padding: "4px 8px",
+        borderRadius: "var(--mantine-radius-sm)",
+        backgroundColor: isActive ? "color-mix(in srgb, var(--color-primary) 10%, transparent)" : hovered ? "var(--color-surface-hover)" : "transparent",
+        cursor: onSelectGraphNode || hasChildren ? "pointer" : "default",
+        userSelect: "none"
+      },
+      children: [
+        hasChildren ? /* @__PURE__ */ jsx(
+          "span",
+          {
+            "aria-hidden": "true",
+            style: {
+              display: "inline-flex",
+              alignItems: "center",
+              justifyContent: "center",
+              width: 12,
+              height: 12,
+              color: "var(--color-text-subtle)",
+              flexShrink: 0
+            },
+            children: expanded ? /* @__PURE__ */ jsx(IconChevronDown, { size: 12, stroke: 2 }) : /* @__PURE__ */ jsx(IconChevronRight, { size: 12, stroke: 2 })
+          }
+        ) : /* @__PURE__ */ jsx(Text, { size: "xs", style: { width: 12, flexShrink: 0 } }),
+        /* @__PURE__ */ jsx(
+          SemanticIcon,
+          {
+            token: iconToken,
+            fallbackKind: "feature",
+            size: 14,
+            style: {
+              color: isActive ? "var(--color-primary)" : hovered ? "var(--color-text)" : "var(--color-text-subtle)"
+            }
+          }
+        ),
+        /* @__PURE__ */ jsx(
+          Text,
+          {
+            size: "xs",
+            fw: isActive ? 700 : 600,
+            tt: uppercase ? "uppercase" : void 0,
+            c: isActive ? "var(--color-primary)" : hovered ? "var(--color-text)" : void 0,
+            style: {
+              letterSpacing: uppercase ? "0.05em" : 0,
+              flex: 1,
+              minWidth: 0,
+              overflow: "hidden",
+              textOverflow: "ellipsis",
+              whiteSpace: "nowrap"
+            },
+            children: label
+          }
+        ),
+        /* @__PURE__ */ jsx(TrailingCopySlot, { count, command, label: "Copy folder knowledge commands", showCopy: hovered })
+      ]
+    }
+  );
+}
+function TrailingCopySlot({ count, command, label, showCopy }) {
+  return /* @__PURE__ */ jsx(
+    "span",
+    {
+      style: {
+        display: "inline-flex",
+        alignItems: "center",
+        justifyContent: "center",
+        width: 32,
+        height: 22,
+        flexShrink: 0
+      },
+      children: showCopy && command ? /* @__PURE__ */ jsx(CopyCommandControl, { command, label, visible: true }) : count > 0 ? /* @__PURE__ */ jsx(KindChip, { kind: String(count), tone: "muted" }) : null
+    }
+  );
+}
+
+// src/knowledge/_generated/knowledge-search-index.json
+var knowledge_search_index_default = [
+  {
+    id: "knowledge.outreach-playbook",
+    title: "Outreach Sequence Playbook",
+    summary: "Step-by-step runbook for launching a cold outreach campaign: prospect sourcing, copy review, sending schedule, and reply handling.",
+    bodyText: "Overview\n\nThis playbook covers the end-to-end process for launching a cold outreach campaign using the Elevasis lead-gen pipeline.\n\nSteps\n\n1. Source prospects via the Lead Gen feature.\n2. Review and approve copy in the CRM campaign editor.\n3. Schedule sends using the Task Scheduler.\n4. Monitor replies in the CRM inbox and route to the appropriate deal stage."
+  },
+  {
+    id: "knowledge.lead-gen-strategy",
+    title: "Lead Gen Targeting Strategy",
+    summary: "Defines ICP signal prioritization, firmographic filters, and scoring thresholds used by the lead-gen pipeline.",
+    bodyText: "Strategy\n\nThe lead-gen pipeline targets SMBs with 10-200 employees in recession-resistant verticals (manufacturing, logistics, professional services). Firmographic filters: revenue \\>$1M, HQ in US/CA/AU, tech stack includes at least one SaaS CRM.\n\nScoring Thresholds\n\n- High priority: ICP score \\>= 80\n- Medium priority: ICP score 60-79\n- Low priority: \\< 60 (excluded from active outreach)"
+  },
+  {
+    id: "knowledge.org-model-reference",
+    title: "Organization Model Schema Reference",
+    summary: "Technical reference for the OrganizationModel Zod schema: all domains, field contracts, and versioning rules.",
+    bodyText: "Schema\n\nThe OrganizationModel schema is defined in packages/core/src/organization-model/schema.ts. It is versioned at version: 1 and composed from domain sub-schemas.\n\nDomains\n\n- features \u2014 flat array of FeatureSchema nodes (nav tree)\n- knowledge \u2014 flat array of KnowledgeNodeSchema nodes\n- sales, prospecting, projects \u2014 sales and GTM domains\n- operations, statuses \u2014 runtime entity domains\n- customers, offerings, roles, goals \u2014 business context domains"
+  },
+  {
+    id: "knowledge.seo-lead-gen-playbook",
+    title: "SEO-to-Lead-Gen Handoff Playbook",
+    summary: "Runbook for promoting SEO-qualified prospects into the active lead-gen pipeline: signal capture, scoring override, and campaign assignment.",
+    bodyText: "Overview\n\nThis playbook governs the handoff from SEO-sourced traffic to the lead-gen pipeline.\n\nSteps\n\n1. SEO feature captures visitor signal (form fill or intent data).\n2. Score the lead using the standard ICP scoring thresholds.\n3. If score \\>= 60, inject into the lead-gen prospect list.\n4. Assign to the appropriate outreach campaign in the CRM."
+  },
+  {
+    id: "knowledge.outreach-campaign-playbook",
+    title: "Campaign Playbook",
+    summary: "Codified rules, benchmarks, and standard operating procedures for Instantly cold email campaigns -- testing methodology, personalization tiers, sequence structure, optimization loop, and batch readiness queries.",
+    bodyText: 'Benchmarks\n\nB2B cold email benchmarks (2025-2026). Use these as evaluation thresholds when running ist-analytics-workflow.\n\n| Metric | Bad | Needs Work | Good | Excellent |\n| --- | --- | --- | --- | --- |\n| Open Rate | \\<20% | 20-30% | 30-45% | 45%+ |\n| Reply Rate | \\<1% | 1-3% | 3-8% | 8%+ |\n| Positive Reply Rate | \\<0.5% | 0.5-1% | 1-3% | 3%+ |\n| Bounce Rate | \\>5% | 2-5% | 1-2% | \\<1% |\n\nCampaign Sizing Rules\n\n- 100-200 contacts per campaign segment -- small enough for meaningful personalization, large enough for statistical learning\n- 1-2 contacts per company -- reply rates drop from 8% to 4% when blasting 10+ people at the same company\n- 30-50 emails/day max per sending account\n- 50-100 emails/day total during testing (weeks 1-4), scaling to 500+/day once a winning formula is found\n\nTesting Priority\n\n1. Subject lines -- highest leverage, easiest to isolate\n2. Opening line / hook -- determines if they keep reading\n3. CTA type -- meeting request vs. soft question vs. value offer\n4. Body copy angle -- pain-point framing vs. benefit lead vs. social proof\n5. Send timing -- Tuesday-Thursday outperform Monday/Friday for B2B\n\nSequence Structure\n\n3 emails total (1 opener + 2 follow-ups). 87-95% of replies come within the first 3 emails.\n\n| Step | Timing | Strategy |\n| --- | --- | --- |\n| Email 1 | Day 0 | Cold read opener + EMRG social proof + interest-based CTA |\n| Email 2 | Day 3 | Short bump in same thread |\n| Email 3 | Day 5 | Breakup email. Soft close, loss aversion |\n\nAgent Optimization Loop\n\nPhase 1 (Launch): Verify batch readiness \u2192 Personalize \u2192 Create campaign \u2192 Create tracking list \u2192 Upload \u2192 Activate\n\nPhase 2 (Analyze Day 7-14): Run ist-campaign-review-workflow \u2192 Run ist-analytics-workflow \u2192 Interpret results\n\nPhase 3 (Optimize): Fix based on Phase 2 analysis (subject lines, personalization, bounce cleanup)\n\nPhase 4 (Scale): Document winning combination \u2192 Replicate to new segments \u2192 Maintain hygiene\n\nOffer Framing\n\n"We find one bottleneck, build an AI solution to fix it, and you only pay if it actually saves you time or makes you money."\n\n- Never use "free" in subject lines -- triggers spam filters\n- Frame as conditional, not charitable\n- Low-commitment CTAs get 2x more replies than direct meeting requests'
+  },
+  {
+    id: "knowledge.outreach-copy-strategy",
+    title: "Copy Strategy",
+    summary: "Reusable email copy framework, tone rules, personalization input guidance, subject line patterns, and offer framing for cold outreach campaigns.",
+    bodyText: `Base reference for writing and evaluating campaign copy. Batch-specific email text lives in each batch tracker's Campaign Strategy section.
+
+Offer
+
+Core message: "We find one bottleneck in your business, build an AI solution to fix it, and you only pay if it actually saves you time or makes you money."
+
+- Never use "free" in subject lines or body copy
+- Frame as conditional, not charitable
+- Don't mention pricing in outreach
+
+Tone
+
+- Voice: First person singular ("I" not "we")
+- Register: Conversational, direct, no jargon
+- Formatting: Plain text only. No bold, no links in body, no HTML
+
+3-Email Sequence Framework
+
+Email 1 \u2014 Hook + Offer (Day 0, 80 words)
+
+Hi {{firstName | there}},
+
+{{openingline}}
+
+{{categorypain}}
+
+I built 4 automations for a company that worked with Google and Sony Music. The first one alone saved them over $1,500 a month. I do the same thing for businesses like yours \u2014 you only pay if it actually works.
+
+Worth a quick look?
+
+{{sendingAccountFirstName}}
+
+Email 2 \u2014 Bump (Day 3, 40 words)
+
+Hi {{firstName | there}},
+
+Wanted to circle back on this \u2014 I've been helping a few companies like {{companyName}} free up their team by automating the repetitive stuff that eats up the day.
+
+Happy to take a 10-minute look \u2014 no pitch, just observations.
+
+{{sendingAccountFirstName}}
+
+Email 3 \u2014 Breakup (Day 5, 25 words)
+
+Totally understand if this isn't the right time. If you ever want a second pair of eyes on what could be automated at {{companyName}}, the offer stands.
+
+{{sendingAccountFirstName}}
+
+Subject Lines
+
+| Variant | Subject | Pattern |
+| --- | --- | --- |
+| A | quick thought | Colleague-camo |
+| B | about {{companyName}} | Observation-trigger |
+
+- Target 21-40 characters
+- Personalized subjects: 46% open rate vs 35% without
+- No "free," "guaranteed," "urgent," "risk-free"`
+  },
+  {
+    id: "knowledge.personalization-strategy",
+    title: "Personalization Strategy",
+    summary: "4-tier personalization waterfall, workflow inputs, quality rules, diagnostic process, and vertical adaptation for cold outreach opening line generation.",
+    bodyText: `How we generate personalized opening lines for Email 1. The ist-personalization-workflow produces ONLY the opening line.
+
+4-Tier Waterfall
+
+| Tier | Name | Trigger | Expected Reply Rate |
+| --- | --- | --- | --- |
+| 1 | Individual Signal | contact.enrichmentData.linkedin.summary exists | 10-15% |
+| 2 | Company Signal | Company has businessDescription OR services[] | 5-10% |
+| 3 | Basic Context | Company has categoryName OR category | 3-5% |
+| 4 | Minimal | Only company name and/or contact title | 1-3% |
+
+Workflow Inputs
+
+| Input | Purpose |
+| --- | --- |
+| batchId | Which contacts to personalize |
+| emailBody | Rest of Email 1 after {openingline} |
+| industryContext | Audience framing for LLM |
+| creativeDirection | Override default creative guidance |
+| performanceContext | Feedback from campaign results |
+| overwrite | Re-personalize existing opening lines |
+
+Quality Rules
+
+Core principle: Wrong personalization is worse than none. Accuracy > depth.
+
+Opening Line Style: Cold Read
+
+The opening line must earn attention through recognition, not create tension through a pitch setup. Take one real fact from enrichment data and make an observation that shows you actually looked at their business.
+
+Good examples:
+- "4,400 reviews since 2018 \u2014 that kind of growth in Orange County is honestly wild."
+- "60 years family-owned with a proprietary Clean Green method \u2014 that's rare in pest control."
+
+Anti-patterns:
+- "You do termite inspections \u2014 how many follow-up calls get missed?" (Implication \u2014 signals selling)
+- "Great company you've built!" (Generic flattery)`
+  },
+  {
+    id: "knowledge.vertical-messaging-playbook",
+    title: "Vertical Messaging Playbook",
+    summary: "Research-backed messaging strategy per vertical \u2014 verified claims, owner voice, language guides, pain point framing, and copy guidelines for outreach messaging.",
+    bodyText: `Purpose
+
+Reference doc for writing and evaluating vertical-specific outreach copy. Captures verified research, owner voice and language, and per-vertical messaging strategy.
+
+Grounded Relatability Strategy
+
+Layer 1: Claim Verification
+Web-research every statistical claim. Grade each as Tier 1 (Verified), Tier 2 (Plausible), or Tier 3 (Unverified). Drop or soften anything Tier 3.
+
+Layer 2: Voice-of-Customer Research
+Search Reddit, trade forums, and industry communities for how owners actually talk about their frustrations.
+
+Layer 3: Scenario-First Copy
+Combine verified claims with owner language to write copy that sounds like a peer, not a vendor:
+1. Lead with the scenario
+2. Use their vocabulary
+3. Reinforce with stats only if they pass the "would I trust this from a stranger?" test
+4. Name concrete capabilities
+
+Universal Owner Patterns
+
+- The Identity Gap: They started the business to do the craft. Acknowledging this resonates deeply.
+- Phone = Business: The owner's phone IS the business.
+- Software Cynicism: Every vertical has been sold to aggressively by SaaS vendors.
+
+Words That Work Everywhere: "Stop losing...", "Without lifting a finger", "Less software, not more"
+
+Words That Fail Everywhere: "AI-powered", "Scale your business", "Digital transformation"
+
+Copy Principles
+
+Lead with Scenarios, Not Statistics
+
+| Weak (stat-first) | Strong (scenario-first) |
+| --- | --- |
+| "78% of homeowners hire the first contractor who responds." | "When you're on a job, you can't answer the phone \u2014 but the homeowner already called two other plumbers." |
+
+Claim Strength Tiers:
+- Tier 1 (Verified): Named source, specific methodology. Use confidently.
+- Tier 2 (Plausible): Widely cited, directionally correct. Use the insight, soften the specific number.
+- Tier 3 (Unverified): No credible source found. Do not use specific numbers.`
+  },
+  {
+    id: "knowledge.cold-email-research-2026",
+    title: "Copy Research (March 2026)",
+    summary: "Cold email research findings from 2025-2026 benchmark reports, A/B test data, and industry studies \u2014 reply rates, subject lines, CTAs, sequence structure, social proof, and vertical-specific angles.",
+    bodyText: `Research findings that inform our copy strategy and campaign decisions. Sourced from Instantly's 2026 Benchmark Report (3M+ emails), industry studies, and platform data.
+
+Last researched: 2026-03-18
+
+Reply Rate Benchmarks (2026)
+
+| Tier | Reply Rate | What It Takes |
+| --- | --- | --- |
+| Average B2B | 3.4% | Basic targeting, template emails |
+| Top quartile | 5.5% | Segmentation + follow-ups |
+| Top performers | 10%+ | Signal-based personalization + tight ICP |
+| Best-in-class | 15-25% | Hyper-personalization + intent signals |
+
+Advanced personalization doubles reply rates: 18% vs 9% for generic.
+
+Email Length
+
+- Under 80 words = 2.4x higher reply rate than emails over 200 words
+- Sweet spot: 50-125 words
+
+Subject Lines
+
+21-40 characters = 49.1% open rate -- long enough to communicate value, short enough for mobile.
+
+- Personalized subject lines: 46% open rate vs 35% without
+- Numbers in subject lines: 113% improvement in open rates
+- Questions in subject lines: 21% increase in open rates
+- Lowercase always -- title case reads as marketing email
+
+CTA Research
+
+- Interest-based CTAs: 30% success rate -- 2x any other type
+- Timeline-based CTAs ("Worth 15 minutes this week?"): 3.4x meeting rate vs problem-based
+- Keep Email 1 CTA short -- one sentence max
+
+Sequence Length
+
+87-95% of replies come within the first 3 emails. Additional emails triple spam complaints without meaningful reply lift (Belkins, 16.5M emails).`
+  },
+  {
+    id: "knowledge.bounce-recovery-protocol",
+    title: "Bounce Recovery Protocol",
+    summary: `Step-by-step protocol for handling campaigns that enter Instantly's "Bounces" status, including cleanup mechanics, root cause investigation, and decision framework for continuing vs. restarting.`,
+    bodyText: `When to Use
+
+A campaign enters Instantly's "Bounces" status (typically \\>5% bounce rate).
+
+Key Mechanics
+
+Bounce Rate Is Historical: Instantly's bounce rate = bounced / sent. Removing bounced leads does not retroactively reduce the rate.
+
+What ist-cleanup-workflow does:
+- Stop sequence: marks lead as "not interested" in Instantly
+- Mark invalid in Lead DB: excludes from all future uploads
+- Delete from Instantly (only with removeFromInstantly: true)
+
+Protocol
+
+Step 1: Pause the Campaign
+bash
+pnpm exec elevasis --prod exec Elevasis/ist-campaign-pause-workflow --input '{"campaignId":"<campaign-id>"}'
+
+Step 2: Dry-Run Cleanup
+bash
+pnpm exec elevasis --prod exec Elevasis/ist-cleanup-workflow --input '{"campaignIds":["<campaign-id>"],"dryRun":true}' --async
+
+Step 3: Run Cleanup
+bash
+pnpm exec elevasis --prod exec Elevasis/ist-cleanup-workflow --input '{"campaignIds":["<id>"],"removeFromInstantly":true}' --async
+
+Step 4: Decide -- Continue or Restart
+
+| Scenario | Action |
+| --- | --- |
+| Most leads unsent (campaign was early) | Continue -- reactivate |
+| Most leads already received emails | Let it finish |
+| Bounce rate \\>10% or account health degraded | Restart -- fresh campaign |
+
+Step 5: Investigate Root Cause
+
+Common root causes: catch-all domains, stale data, verification false positives, generic/role addresses (info@, service@).
+
+Step 6: Update Batch Tracker
+
+Log bounce count, leads cleaned, root cause, and resolution in the batch tracker doc.`
+  },
+  {
+    id: "knowledge.lead-gen-pipeline-playbook",
+    title: "Lead-Gen Playbook",
+    summary: "Empirical benchmarks, threshold guidance, provider economics, and codified learnings from 3 completed batches of the lead-gen pipeline.",
+    bodyText: "Performance Benchmarks\n\nPer-stage success rates across the 3 completed Orange County batches (vet-1, auto-1, home-1).\n\nStage 1: Scrape (Raw to Filtered)\n\n| Metric | vet-1 | auto-1 | home-1 | Benchmark |\n| --- | --- | --- | --- | --- |\n| Raw results | 480 | 800 | 1000 | -- |\n| Companies created | 393 | 566 | 701 | -- |\n| Active in DB | 322 | 428 | 640 | -- |\n\nStage 3: Company Qualification Rate\n\n| Metric | vet-1 | auto-1 | home-1 | Benchmark |\n| --- | --- | --- | --- | --- |\n| Qualified | 213 (76%) | 284 (79%) | 326 (60%) | 60-80% |\n| Disqualified | 66 (24%) | 74 (21%) | 222 (40%) | 20-40% |\n\nStage 5: Email Verification\n\nVALID rate: 33-41% of discovered emails across batches. Target bounce rate \\<2%.\n\nModel Selection\n\nUse Gemini Flash models for high-volume qualification steps (cost/quality balance). Use GPT for personalization where quality matters most.\n\nProvider Economics\n\nTomba domain search provides the best cost-per-verified-contact for local SMBs. Dual-verify (Tomba + Mails.so) catches most false positives.\n\nPipeline Stages\n\n1. Scrape (Google Maps via Apify)\n2. LLM Extract (website crawl \u2192 structured data)\n3. Company Qualification (LLM ICP scoring)\n4. Email Discovery (Tomba domain search)\n5. Email Verification (Mails.so)\n6. Opening Line Generation (ist-personalization-workflow)\n7. Campaign Upload (ist-upload-workflow)"
+  },
+  {
+    id: "knowledge.upwork-proposal-playbook",
+    title: "Proposal Playbook",
+    summary: "Data-backed strategies for writing winning Upwork proposals \u2014 structure, pricing, timing, client qualification, and benchmarks.",
+    bodyText: `The Numbers That Matter
+
+| Metric | Benchmark |
+| --- | --- |
+| Personalized proposals | 30% higher reply rate vs generic |
+| Proposals within first 2 hours | 3x response rate vs 24h+ |
+| First-hour proposals | 3-5x interview rate boost |
+
+Proposal Structure
+
+Keep proposals 150-200 words, mobile-scannable.
+
+The Five-Part Formula
+
+1. Hook (1-2 sentences) \u2014 Lead with what you do and why it's relevant. Never use "caught my attention" \u2014 overused clich\xE9.
+2. Proof (1-2 sentences) \u2014 One concrete metric from past work.
+3. Plan (2-3 lines) \u2014 Maximum 3 steps.
+4. Discovery Questions (exactly 2) \u2014 Smart, role-specific questions. End with a binary CTA.
+5. Sample (optional) \u2014 Loom video (2-3 min).
+
+Opening Lines
+
+The first line decides 80% of reply outcomes. Always use the client's name or company name.
+
+Good openers: "Hi \u2014 I build {whattheyneed} for a living and run my own business on them daily."
+
+Never open with: "The part that caught my attention..." / "What stood out..."
+
+Elevasis-Specific Positioning
+
+Dogfooding (Strongest Differentiator): We run our own 7-stage client acquisition pipeline on the platform: Scrape \u2192 Extract \u2192 Qualify \u2192 Email Discovery \u2192 Verify \u2192 Personalize \u2192 Outreach.
+
+The 4 Principles (Use in Discovery Questions):
+1. Integrated \u2014 Works with existing tools
+2. Improving \u2014 Learns from every human decision
+3. Observable \u2014 Real-time visibility
+4. Governed \u2014 Humans approve what matters`
+  },
+  {
+    id: "knowledge.upwork-response-templates",
+    title: "Response Templates",
+    summary: "Templates and guidelines for responding to Upwork messages, offers, and client communications.",
+    bodyText: `Offer Acceptance Response
+
+When a client sends an offer and invites a call:
+1. Thank them for the offer (brief, no flattery)
+2. Confirm the call with a specific day/time and timezone
+3. Ask 2-3 qualifying questions to show engagement
+4. Sign off with first name (Alex, not Alexander)
+
+Template
+
+Hi {name},
+
+Thanks for the offer and for reaching out, I'll book a time for {day} {time} ({timezone}). I look forward to learning more about your setup!
+
+Just a few questions:
+1. {qualifying question about current tools/stack}
+2. {qualifying question about current process/pain}
+3. {qualifying question about scope/direction}
+
+Thanks!
+Alex
+
+Qualifying Question Bank
+
+- Current stack: "What do you currently use for workflows / automation?"
+- Pain points: "What's the most time-consuming repetitive task right now?"
+- Approval flow: "What do you currently use for approval control?"
+- Consolidation: "Are you using multiple tools or interested in custom software?"
+- Team size: "How many people will be using these workflows?"
+- Priority: "What's the first workflow you'd want built?"
+
+Style Rules
+
+- Tone: Warm but concise. No filler, no over-enthusiasm.
+- Length: 3-6 sentences max.
+- Timezone: Always specify timezone when confirming times (PDT/PST).
+- No selling: The call is for learning, not pitching.`
+  },
+  {
+    id: "knowledge.seo-playbook",
+    title: "SEO Playbook",
+    summary: "Operational playbook for the SEO/AEO system \u2014 vertical launch workflow, content quality gates, AEO formatting rules, stale content management, metrics interpretation, and rollout phases.",
+    bodyText: "Vertical Launch Workflow\n\nEnd-to-end process for launching a new vertical (e.g., hvac-contractors):\n\nStep 1: Research vertical data\n\nFind real, citable industry statistics: pain points, automation ROI, market context. Sources: trade associations, industry surveys, government data (BLS, Census).\n\nStep 2: Generate pages\n\nbash\nPillar page\npnpm tsx scripts/seo/generate-pages.ts --vertical hvac-contractors --type pillar --dry-run\npnpm tsx scripts/seo/generate-pages.ts --vertical hvac-contractors --type pillar\n\nCluster pages\npnpm tsx scripts/seo/generate-pages.ts --vertical hvac-contractors --type cluster\n\nStep 3: Backfill chart data\n\nCharts require post-generation patching. Write chart patch files using Step 1 research, then apply via content.ts patch.\n\nStep 4: AEO optimization\n\nEvery section must be self-contained. AI engines extract individual passages, not full pages.\n- Lead with a 30-50 word standalone answer in the first sentence of each section\n- 78% of AI Overview answers use list format\n- Frame headings as questions when possible\n\nStep 5: Post-publish distribution\n\nUpdate llms.txt, ping IndexNow, submit sitemap segments to Search Console.\n\nData Sourcing Rules\n\n- Tier 1 (Verified): Named source, specific methodology. Use confidently.\n- Tier 2 (Plausible): Widely cited, directionally correct. Soften the specific number.\n- Tier 3 (Unverified): No credible source. Do not use specific numbers."
+  },
+  {
+    id: "knowledge.seo-content-guide",
+    title: "SEO Content Writing Guide",
+    summary: "Tactical guide for writing SEO and AEO-optimized content \u2014 page structure, keyword strategy, AI engine citation optimization, E-E-A-T signals, and CTA patterns.",
+    bodyText: 'Overview\n\nThis guide covers how to write SEO content that ranks in traditional search AND gets cited by AI answer engines \u2014 ChatGPT, Perplexity, Google AI Overviews, and Gemini.\n\nThe distribution channel is split: 69% of Google searches result in zero clicks, while AI platforms generated 1.13 billion referral visits in June 2025 alone.\n\nPage Structure\n\nSection Architecture\n\nEvery section must be self-contained. AI engines extract individual passages, not full pages.\n\n- Lead with a 30-50 word standalone answer in the first sentence of each section\n- Paragraphs: 2-4 sentences max\n- 78% of AI Overview answers use list format -- use bullets and numbered lists extensively\n- Heading hierarchy: one H1 (page title), H2 for major sections, H3 for subsections\n- Frame headings as questions when possible\n\nSection Length\n\n- Pillar pages: 2,000-3,000 words total\n- Cluster pages: 1,000-2,000 words total\n- Each major section: 150-300 words\n\nConciseness Rules\n\n1. Two-paragraph intro max\n2. No stat duplication between intro and problem section\n3. Section character budget: Intro 450-600 chars, Problem 250-400 chars, Solution 300-550 chars\n\nE-E-A-T Signals\n\n- Brand name "Elevasis" must appear explicitly minimum 3x per page\n- Vertical names used as proper noun concepts\n- Organization + Service + SoftwareApplication schema markup reinforces entity recognition'
+  },
+  {
+    id: "knowledge.seo-distribution-playbook",
+    title: "Distribution & Citation Building",
+    summary: "Post-publish distribution playbook \u2014 AI crawler discovery, directory citations, Google Business Profile, community seeding, monitoring cadence, and AEO optimization tactics.",
+    bodyText: 'Overview\n\nEverything that happens after pages are published and sitemap/IndexNow pings are sent. Evergreen reference for maximizing visibility across traditional search, AI answer engines, and buyer-intent directories.\n\nAI Crawler Discovery\n\nllms.txt\n\nA plain-text Markdown file at the domain root that gives LLMs a structured map of key content. Location: apps/website/public/llms.txt.\n\nUpdate whenever pillar or cluster pages are published.\n\nSitemap Segmentation\n\n| Segment ID | Contents | Priority |\n| --- | --- | --- |\n| 0 | Static pages | Default |\n| 1 | Pillar pages (9) | 0.9 |\n| 2 | Cluster pages (52) | 0.8 |\n\nEntity Density Rules\n\nPages with 15+ recognized entities show 4.8x higher selection probability for AI citations.\n- Brand name "Elevasis" must appear explicitly (minimum 3x per page)\n- Stat density target: one statistic every 150-200 words\n\nDirectory Citations\n\nTier 1 (Buyer Intent): G2, Capterra, Product Hunt, AppSumo (direct buyer intent, high domain authority)\n\nTier 2 (Authority): Crunchbase, AngelList, LinkedIn company page, industry association directories\n\nGoogle Business Profile\n\nClaim and verify GBP listing. Category: "Software Company". Keep NAP (Name, Address, Phone) consistent across all citations.'
+  },
+  {
+    id: "knowledge.content-playbook",
+    title: "Content Playbook",
+    summary: "Content creation guide \u2014 pillars, platform rules, format specs, repurposing chain, and metrics benchmarks for multi-platform distribution",
+    bodyText: 'Content Pillars\n\nEvery content piece maps to one of five pillars.\n\n| Pillar | What It Is | Target Frequency |\n| --- | --- | --- |\n| dogfooding | How we run Elevasis using our own platform | 1-2x/week |\n| education | 4 Pattern Framework and AI orchestration concepts | 1x/week |\n| demo | "Watch AI Work" \u2014 showing the platform in action | 1x/2 weeks |\n| pain-point | SMB pain points backed by data | 1x/week |\n| founder-journey | Solo founder building with AI | 1x/week |\n\nThe 90-10 Rule\n\n90% educational value, 10% promotional. Keeping promotional content to \\<15% ensures your audience stays receptive when you do make an offer.\n\nContent Creation Workflow\n\n1. Capture the Idea \u2014 Insert into acqcontent with status: idea\n2. Draft the Source Content \u2014 Write core idea in acqcontent.body. LinkedIn first.\n3. Adapt for Platforms \u2014 Repurpose from LinkedIn to YouTube, Instagram, X\n4. Schedule and Publish \u2014 Use platform-native scheduling\n5. Track Performance \u2014 Monitor in acqcontent via Command Center\n\nPlatform Priority\n\n1. LinkedIn \u2014 #1 priority, 3x/week\n2. YouTube \u2014 #2 priority, 1x/week + Shorts\n3. Instagram \u2014 #3 priority, 2-3x/week, repurpose from LinkedIn/YouTube\n4. X \u2014 #4 priority, 2-3x/week, threads from LinkedIn'
+  },
+  {
+    id: "knowledge.inbound-reply-handling-playbook",
+    title: "Stage 01: Reply Handling",
+    summary: "Classify email replies, create CRM contact, and send booking link to interested leads",
+    bodyText: `Overview
+
+Classify incoming email replies, create CRM contact for interested leads, and send booking link. Uses value-first approach: offer a free one-time AI service instead of passive content.
+
+Classification
+
+Four-way classification with confidence-based HITL routing. Auto-replies detected deterministically before any LLM call.
+
+| Category | Examples | Action |
+| --- | --- | --- |
+| Interested | "Yes I'm interested", "Tell me more" | CRM \u2192 HITL task with LLM-drafted follow-up |
+| Not Interested | "Unsubscribe", "Not interested" | Stop outreach sequence |
+| Bounced | mailer-daemon@, "Undeliverable" | Stop outreach \u2192 Mark Lead DB INVALID \u2192 Skip CRM |
+| Auto-Reply | Out-of-office, ticketing acknowledgments | No action \u2014 campaign continues |
+
+Auto-Reply Detection (Pre-LLM)
+
+Caught deterministically via regex:
+- Sender address prefix: noreply, no-reply, donotreply, auto, mailer
+- Subject patterns: "auto-reply", "out of office", "OOO"
+- Body patterns: "this is an automated message", vacation auto-responders
+
+Routing Notes
+
+- NOTINTERESTED and BOUNCED: sequence stopped via Instantly update-interest-status
+- INTERESTED: does NOT stop sequence \u2014 proceeds to CRM creation and HITL queue
+- AUTO-REPLY: no CRM, no sequence stop, no reply
+
+HITL Strategy
+
+For INTERESTED replies, an LLM drafts a follow-up response. Admin reviews and approves via Command Queue before anything sends.`
+  },
+  {
+    id: "knowledge.inbound-booking-playbook",
+    title: "Stage 02: Booking",
+    summary: "Cal.com booking handling -- create, reschedule, and cancel discovery call bookings",
+    bodyText: 'Overview\n\nWhen a prospect books a discovery call via Cal.com, the booking handler manages CRM updates, notifications, and reminder scheduling across all booking lifecycle events.\n\nBooking Handler Workflow\n\nTriggers: Cal.com webhooks (BOOKINGCREATED, BOOKINGRESCHEDULED, BOOKINGCANCELLED)\n\nEvent Flows\n\nBOOKINGCREATED:\n1. create-contact \u2014 Create or update Attio Person record, resolve Deal via metadata or email, update Deal stage to booked, create Discovery Call Prep note, cancel brochure follow-ups\n2. notify-created \u2014 Send platform notification to admin\n3. schedule-reminders \u2014 Create absolute schedule with pre-computed -24h and -1h reminder times\n\nBOOKINGRESCHEDULED:\n1. update-schedule \u2014 Cancel existing reminders, schedule new ones at updated times\n2. finish-reschedule \u2014 Update Deal stage, notify admin\n\nBOOKINGCANCELLED:\n1. cancel-schedule \u2014 Cancel all scheduled reminders\n2. finish-cancel \u2014 Update Deal stage to cancelled, notify admin\n\nReminder Schedule\n\nTwo automated reminders per booking:\n- -24h reminder: "Looking forward to our call tomorrow"\n- -1h reminder: "See you in 1 hour" with discovery form link\n\nReminders are scheduled as absolute times (not relative), so rescheduling correctly cancels and re-schedules them.'
+  },
+  {
+    id: "knowledge.discovery-call-playbook",
+    title: "Stage 03: Discovery",
+    summary: "Discovery form submission, qualification routing, and data storage -- the pipeline endpoint",
+    bodyText: "Overview\n\nThe discovery form is filled during the call by the salesperson. On submission, the workflow stores structured data, updates the CRM, and routes based on qualification.\n\nThis is the current pipeline endpoint \u2014 qualified leads receive a HITL task for manual follow-up; no automated stages exist beyond this point.\n\nWorkflow Steps\n\n1. route-by-action \u2014 Route to submission or no-show flow\n2. compute-cost \u2014 Calculate totalAnnualCost from bottlenecks\n3. store-discovery \u2014 Save discoverydata JSONB to acqdeals\n4. find-deal \u2014 Find Attio Deal (acqdeals \u2192 URL context \u2192 Attio API)\n5. update-attio-stage \u2014 Update Deal.stage based on qualification\n6. create-summary-note \u2014 Add markdown Note to Deal\n7. create-hitl-task \u2014 Create HITL approval item for qualified leads\n\nQualification Routing\n\n- Qualified: Deal moves to qualified stage; HITL task created for admin follow-up\n- Not Qualified: Deal moves to closedlost stage; no further automation\n- No-Show: Deal moves to noshow stage; timeout checker handles re-engagement\n\nDiscovery Form Structure\n\nThe form captures: company size, current tools, 3 biggest bottlenecks, estimated time wasted per week, budget comfort range, urgency, decision-making authority."
+  },
+  {
+    id: "knowledge.pipeline-management-playbook",
+    title: "Pipeline Management",
+    summary: "Automated pipeline maintenance workflows for the inbound pipeline, covering timeout monitoring, stale deal handling, unsubscribe cleanup, and full contact reset.",
+    bodyText: "Overview\n\nPipeline management keeps the inbound pipeline clean without manual intervention.\n\n- Timeout monitoring \u2014 Detecting deals that have gone stale in a stage\n- Unsubscribe cleanup \u2014 Closing deals and cancelling automation when a contact opts out\n- Full cleanup \u2014 Complete removal of all pipeline data for a contact\n\nNo timeout action transitions a deal automatically. All stage changes from the timeout system require admin approval via a HITL Command Queue item.\n\nTimeout System\n\nTimeout Checker (inb-pipeline-timeout-checker-workflow)\n\nScans all active pipeline stages. For each stale deal, creates a HITL approval item in the Command Queue. Never modifies deal records directly.\n\nTimeout rules by stage:\n\n| Stage | Condition | Timeout |\n| --- | --- | --- |\n| interested | No activity | 30 days |\n| booked | Meeting time has passed | 3 hours after meeting |\n| discovery | No form submission | 24 hours after call |\n\nAction Workflows\n\n4 action workflows triggered by admin approval:\n- Nurture: Move to nurture sequence\n- Close-Lost: Mark deal closed, stop all automation\n- No-Show: Re-send booking link with personal note\n- Follow-Up: Send soft re-engagement email\n\nUnsubscribe Cleanup\n\nWhen a contact opts out:\n1. Find all active automation for the contact\n2. Cancel scheduled reminders\n3. Update Deal stage to unsubscribed\n4. Mark contact as unsubscribed in Attio"
+  },
+  {
+    id: "knowledge.communications-map",
+    title: "Communications Map",
+    summary: "All lead-facing messages across the active client acquisition pipeline (stages 01-03). Stages 04-08 communications are archived.",
+    bodyText: 'Overview\n\nEvery message sent to a lead across the active acquisition pipeline \u2014 outreach, follow-ups, reminders, and event-triggered emails. 10 total active messages (3 outreach + 1 reply + 2 subsequent reply + 2 discovery reminders + 1 timeout follow-up + 1 timeout re-engagement).\n\nStages 04-08 communications (proposal follow-ups, payment reminders, nurture sequences) are archived.\n\nActive Pipeline Phases\n\n1. Outreach (Instantly)  2. Reply Handling     3. Discovery Reminders\n 3 emails                 1 email + 2 HITL      2 reminders\n Day 0/3/7                On reply              -24h/-1h\n\nPhase 1: Outreach (Instantly)\n\n| # | Day | Subject | Angle | Purpose |\n| --- | --- | --- | --- | --- |\n| 1 | 0 | idea for {{companyName}} | Earn attention | Personal, specific |\n| 2 | 3 | where do business hours actually go? | New angle | Peer-level, intriguing |\n| 3 | 7 | the offer (whenever useful) | Permission to close | Warm, zero pressure |\n\nPhase 2: Reply Handling (Resend)\n\nSent only to INTERESTED replies. LLM drafts; admin approves via HITL before sending.\n\nPhase 3: Discovery Reminders (Resend)\n\nTwo automated reminders per booking:\n- -24h: "Looking forward to our call tomorrow"\n- -1h: "See you in 1 hour" with discovery form link\n\nAll scheduled/event emails signed "Alex". Plain text.'
+  },
+  {
+    id: "knowledge.reddit-monitoring-playbook",
+    title: "Social Monitoring",
+    summary: "Automated Reddit monitoring pipeline \u2014 4-step workflow (search, LLM score, LLM draft, store) with tiered subreddit scraping via Apify, Gemini-powered scoring and response drafting, and lead-gen optimized responses via the AlexElevasis account.",
+    bodyText: "Overview\n\nSocial monitoring surfaces Reddit posts where business owners discuss operational challenges, manual processes, and automation needs.\n\nCron Trigger (3x/day: 16:00, 22:00, 04:00 UTC)\n    \u2192 mnt-reddit-monitor-workflow (4-step pipeline)\n        \u2192 Step 1: Search \u2014 4 sequential Apify actors (one per tier)\n        \u2192 Step 2: Score \u2014 Gemini Flash Lite (concurrency 5)\n        \u2192 Step 3: Draft \u2014 Gemini Flash (high-score only)\n        \u2192 Step 4: Report \u2014 Store to acqsocialposts, log breakdown\n    \u2192 Command Center: /acquisition/monitoring\n\nStatus: Paused until further notice (2026-03-31). Pipeline technically validated but ROI is low without deep vertical expertise.\n\nVelocity Batches\n\nSubreddits grouped by posting velocity, each with its own maxPostsPerSource.\n\n| Batch | Subs | Posts/Source | Example Subreddits |\n| --- | --- | --- | --- |\n| Medium Velocity | 2 | 5 | Accounting, Plumbing |\n| Buyer Low-Volume | 10 | 3 | CRM, EntrepreneurRideAlong, sweatystartup |\n| Trade Niche | 10 | 2 | electricians, Dentists, InsuranceAgent |\n| Decision Niche | 3 | 2 | logistics, FreightBrokers, healthIT |\n\nScoring\n\nPosts scored 0-100 by Gemini Flash Lite for business automation opportunity relevance. Posts scoring \\>= 60 get response drafts via Gemini Flash.\n\nAlexElevasis Account\n\nAll responses posted via the AlexElevasis Reddit account. See Reddit Account strategy doc for warmup playbook and karma thresholds."
+  },
+  {
+    id: "knowledge.reddit-account-strategy",
+    title: "Reddit Account",
+    summary: "AlexElevasis Reddit account strategy \u2014 warm-up playbook, karma thresholds, posting rules, and lead generation approach for the social monitoring pipeline.",
+    bodyText: 'Account Details\n\n| Field | Value |\n| --- | --- |\n| Username | AlexElevasis |\n| Created | 2026-03-26 |\n| Purpose | Lead generation via Reddit monitoring pipeline |\n| Persona | Alexander, founder of an AI automation company |\n\nThe username serves double duty: every helpful comment puts "Elevasis" in front of the reader.\n\nWarm-Up Playbook\n\nDays 1-3 \u2014 Cold Start:\n- Browse, upvote, follow target subs\n- 1 comment per day max\n- No links, no self-promotion, no CTAs\n\nDays 4-14 \u2014 Gradual Ramp:\n- Increase to 2-3 comments/day\n- Genuine, helpful answers \u2014 no copy-paste across threads\n- Still no links or CTAs\n\nAfter 30 Days + 100 Karma \u2014 Activation:\n- Most automod filters cleared\n- Start using monitoring pipeline drafts\n- 300+ karma unlocks more restrictive subs (r/Entrepreneur, r/startups)\n\nKarma Thresholds\n\n| Karma | Access Level |\n| --- | --- |\n| 100 | Bypasses most automod filters |\n| 300+ | Access to restrictive subs |\n| 1,000+ | Considered established community member |\n\nPosting Rules\n\n- Genuine value first \u2014 no pitching without established reputation\n- 30-day account age required before using pipeline drafts\n- Open questions in responses (not CTAs) per pipeline draft conventions'
+  },
+  {
+    id: "knowledge.linkedin-strategy",
+    title: "LinkedIn Strategy",
+    summary: "LinkedIn posting strategy \u2014 algorithm deep dive, format rankings, hook techniques, carousel optimization, newsletter strategy, engagement tactics, profile optimization, and growth playbook for B2B SaaS (2025-2026)",
+    bodyText: 'Overview\n\nLinkedIn is the #1 priority platform. The algorithm heavily favors personal profiles over company pages. In 2025-2026, LinkedIn shifted from viral reach to depth and authority \u2014 topical consistency is now the single biggest strategic lever.\n\nCadence: 3-5x/week (Wed/Thu/Fri strongest, Monday weakest)\n\nAlgorithm Deep Dive\n\nRanking Signals (by weight)\n\n| Signal | Weight | Notes |\n| --- | --- | --- |\n| Comments | Highest | 15x more valuable than likes |\n| Saves and sends | Very high | Added to analytics in late 2025 |\n| Dwell time | High | 15+ seconds = meaningful |\n| "See more" clicks | High | Whether people expand the full post |\n| Reactions/likes | Lowest | Significantly de-emphasized |\n\nTopical Authority\n\nThe algorithm rewards consistent publishing within a defined area of expertise. Pick a lane (AI automation) and stay in it.\n\nPost Formats\n\n1. Carousels \u2014 Highest avg engagement; 10-slide with text + data\n2. Text posts \u2014 Quick takes, contrarian observations, founder stories\n3. Documents/PDFs \u2014 In-depth guides, playbooks, frameworks\n4. Videos \u2014 Native upload outperforms external links by 5x\n\nHook Techniques\n\n- Lead with the most surprising/counterintuitive insight\n- Use "I" not "we" \u2014 personal profile posts outperform company pages\n- 3 lines max before "...see more" break\n- Questions outperform statements for comments engagement'
+  },
+  {
+    id: "knowledge.instagram-strategy",
+    title: "Instagram Strategy",
+    summary: "Comprehensive Instagram posting strategy for B2B SaaS founder content \u2014 algorithm deep dive, Reels, carousels, Stories, SEO, hashtags, captions, profile optimization, growth tactics, and analytics benchmarks (2025-2026)",
+    bodyText: 'Overview\n\nInstagram is the #3 priority platform. Carousels repurpose easily from LinkedIn, and Reels come directly from YouTube Shorts.\n\nCadence: 3-5x/week feed posts + daily Stories\n\nB2B Reality Check: Instagram is a complementary channel for B2B SaaS, not a primary lead gen tool. Decision-makers are on Instagram (76% of B2B companies use it), but they are in consumer mode.\n\nAlgorithm Deep Dive (2025-2026)\n\nReels Algorithm (Most Important for Reach)\n\nReels are designed for discovery: 55% of Reels views come from non-followers.\n\nThree priority signals:\n| Signal | Weight | How to Optimize |\n| --- | --- | --- |\n| Watch time | #1 | Hook in first 1.7s; optimize for completion |\n| Sends per reach | Highest for new audiences | "Send this to someone" content |\n| Likes per reach | Highest for followers | Valuable content followers engage with |\n\nContent Strategy\n\n- Repurpose from LinkedIn: Carousel slides \u2192 Instagram carousel\n- Repurpose from YouTube: Long-form \u2192 Reels (cut 30-60s clips)\n- Stories: Daily touchpoints, polls, Q&A, behind-the-scenes\n\nCarousel Optimization\n\n- Slide 1: Hook (bold claim or question)\n- Slides 2-9: Value delivery (one point per slide)\n- Slide 10: CTA (follow, DM, link in bio)'
+  },
+  {
+    id: "knowledge.x-strategy",
+    title: "X (Twitter) Strategy",
+    summary: "X/Twitter posting strategy \u2014 algorithm signals, thread tactics, engagement weights, Premium ROI, video specs, growth playbook, and B2B SaaS niche tactics",
+    bodyText: "Overview\n\nX is the #4 priority platform. Most content is repurposed from LinkedIn text posts as threads.\n\nCadence: 3-5 posts/day (mix of original posts + replies + quote tweets), 2-3 threads/week\n\nPrerequisite: Get X Premium ($8/mo) \u2014 verified accounts get 10x more impressions. Non-Premium accounts posting links receive near-zero engagement as of 2026.\n\nAlgorithm Deep Dive\n\nEngagement Weight Scoring\n\n| Signal | Weight | vs. Like |\n| --- | --- | --- |\n| Reply engaged by author | +75 | 150x |\n| Reply | +13.5 | 27x |\n| Profile click + engagement | +12.0 | 24x |\n| Bookmark | +10.0 | 20x |\n| Retweet | +1.0 | 2x |\n| Like | +0.5 | 1x |\n\nCritical takeaway: Replying to your own replies is worth 150x a like.\n\nPenalties\n\n- External links: 30-50% reach reduction\n- Multiple hashtags: 40% penalty\n\nThread Strategy\n\n- First tweet = hook (bold claim or surprising stat)\n- 5-10 tweets per thread\n- Last tweet = CTA (follow for more, link to extended content)\n- Reply to your own threads within the first hour to boost algorithmic velocity"
+  },
+  {
+    id: "knowledge.youtube-channel-strategy",
+    title: "Channel Strategy",
+    summary: 'Unified YouTube channel strategy \u2014 channel setup, content pipeline, differentiation positioning, launch queue, and production workflow for "Alexander Le | Elevasis" channel',
+    bodyText: `Objective
+
+Build the "Alexander Le | Elevasis" YouTube channel as an evergreen discovery engine for Elevasis. YouTube is the #1 content priority \u2014 evergreen discovery, SEO compounding, and 53% of B2B buyers watch video before requesting demos.
+
+Channel Identity
+
+- Name: "Alexander Le | Elevasis" \u2014 personal-brand hybrid with clear business association
+- Handle: @AlexanderElevasis
+- Why personal-brand hybrid: People subscribe to people. Algorithm favors creator-branded channels over faceless brands.
+
+Content Format: Face Bubble Intro \u2192 Screen Recording
+
+Primary format: Quick face-cam intro (circle overlay, 15-30s) to build trust, then full-screen recording.
+
+Why this works:
+- 40%+ of YouTube's top 1,000 channels never show a presenter \u2014 faceless works
+- Screen recording tutorials rank extremely well on YouTube + Google
+- Face in thumbnails gets 921K more views on average
+
+Differentiation
+
+Compete on substance, not production quality:
+- Real execution data, real costs, real results (not simulations)
+- "Document the build" format: record while building, editing, deploying
+- Show Command Center in action \u2014 no equivalent content exists
+
+Launch Queue
+
+3 priority video types for channel launch:
+1. Platform demo walkthroughs (Command Center, workflow execution)
+2. Founder journey episodes (building in public)
+3. Educational explainers (AI orchestration concepts)`
+  },
+  {
+    id: "knowledge.youtube-tactics",
+    title: "YouTube Strategy",
+    summary: "YouTube posting strategy \u2014 upload optimization, Shorts tactics, algorithm signals, SEO, first-48-hour playbook, faceless content tips, and small channel growth for B2B SaaS",
+    bodyText: `Overview
+
+YouTube is the #2 priority platform and the only one with true evergreen discovery. Videos keep gaining views months/years after posting.
+
+Cadence: 1 long-form/week + 3-5 Shorts/week
+
+Upload Checklist
+
+Title
+- Keep meaningful part in first 60 chars (mobile truncation)
+- Front-load primary keyword: "AI Automation for Veterinary Clinics (Full Walkthrough)"
+- Long-tail titles outperform generic for small channels
+
+Thumbnail
+- 1280x720px, 16:9, max 2MB
+- 4 words max of bold, high-contrast text
+- Use YouTube's Test & Compare \u2014 upload 3 thumbnails, YouTube A/B tests and reports CTR
+
+Description
+- First 125 chars = what shows in search results
+- Add timestamps/chapters \u2014 improve retention + create extra search ranking hooks
+
+Shorts Strategy
+
+- Cut 30-60s clips from long-form: best moments, surprising reveals, "before/after"
+- Repurpose from YouTube to Instagram Reels and TikTok
+- Hook in first 1-2 seconds: start with the payoff, not the setup
+
+First-48-Hour Playbook
+
+1. Publish during peak hours (12pm-3pm ET Tuesday-Thursday)
+2. Post about the video on LinkedIn immediately after upload
+3. Reply to every comment within the first 24 hours
+4. Share in relevant communities (not spam \u2014 genuine value)`
+  },
+  {
+    id: "knowledge.youtube-growth-playbook",
+    title: "YouTube Growth Playbook",
+    summary: "Practical YouTube optimization guide for Elevasis screen-recorded demos, founder-led walkthroughs, Shorts, SEO, and launch review loops",
+    bodyText: 'Overview\n\nThis playbook maps YouTube growth tactics to the current Elevasis content format: screen recordings, Command Center walkthroughs, founder commentary, proof assets, and short clips cut from real demos.\n\nThe goal is to make real AI orchestration visible enough that buyers and technical peers understand what Elevasis does.\n\nCore Format\n\n| Format | Use For | Notes |\n| --- | --- | --- |\n| Face intro \u2192 screen recording | Flagship demos, founder-led walkthroughs | 15-30 second intro, then full-screen product work |\n| Screen recording only | Tutorials, Shorts source material | Fastest to produce |\n| Data walkthrough | Campaign metrics, cost tracking, workflow results | Use only real data |\n| Concept explainer | AI agents, orchestration, human oversight | Keep tied to concrete business workflows |\n\nCTR Optimization\n\nThumbnails should show the result or system, not abstract concepts:\n1. Command Center, workflow graph, campaign analytics, or visible output\n2. Optional face overlay when it improves trust\n3. Three to five words of context. High contrast, readable at mobile size.\n\nTitle rules:\n- Front-load the topic\n- Use real numbers only when current and verifiable\n- Prefer "Watch", "Real", "Live", "Actual", "Walkthrough" over hype language\n- Make the title and thumbnail say different things\n\nRetention\n\nOpen with the payoff:\n1. Show the final dashboard, result, or workflow output\n2. Explain what the viewer is about to see\n3. Switch into the walkthrough quickly\n\nFirst-24-Hour Workflow\n\nAlgorithm watches first 30-60 minutes closely. A video getting 10 replies in 15 minutes dramatically outperforms one getting 10 replies over 24 hours.'
+  },
+  {
+    id: "knowledge.youtube-mental-prep",
+    title: "Mental Preparation \u2014 Creator Anxiety Playbook",
+    summary: "Research-backed strategies for overcoming publishing anxiety, the spotlight effect, graduated exposure, and building comfort on camera \u2014 practical guide for a technical founder starting YouTube",
+    bodyText: `Why This Exists
+
+Recording yourself and putting your ideas out publicly is genuinely uncomfortable. This doc captures the research and practical strategies so you can reference them when the anxiety spikes \u2014 not as motivation, but as evidence that the discomfort is normal, finite, and navigable.
+
+The Core Insight
+
+Readiness is a product of exposure, not a prerequisite for it. You don't stop feeling afraid and then start. You start, and the fear gradually recedes.
+
+What You're Actually Afraid Of
+
+The Spotlight Effect (Gilovich et al., 2000)
+
+People overestimate how much others notice and judge them by roughly 2x. Early videos get almost zero views \u2014 you're practicing in an empty room.
+
+The Five Common Fears (in order of prevalence)
+
+1. Judgment from people you know \u2014 not strangers. The #1 blocker.
+2. Perfectionism as procrastination \u2014 "I'll start when I have better equipment." This is avoidance.
+3. Impostor syndrome \u2014 "Who am I to teach this?"
+4. Permanence anxiety \u2014 "This will be on the internet forever"
+5. Voice/face aversion \u2014 Most people dislike their recorded voice (bone conduction gap)
+
+The Real Fear: Cringe
+
+People tolerate a video that flops quietly. What they can't tolerate is creating something they later find embarrassing.
+
+Graduated Exposure Protocol
+
+1. Screen recording only (no face, no voice) \u2014 2 videos
+2. Screen recording + voiceover (no face) \u2014 5 videos
+3. Face bubble intro (15-30s) + screen recording \u2014 ongoing
+
+Each stage desensitizes one fear at a time. Never skip ahead. The goal is consistency, not perfection.`
+  },
+  {
+    id: "knowledge.new-vertical-launch-playbook",
+    title: "New Vertical Launch Playbook",
+    summary: "Zero-to-first-campaign workflow for launching a new acquisition vertical: batch definition, tracker setup, lead generation stages, campaign launch, and monitoring.",
+    bodyText: `Overview
+
+Use this playbook when launching a new acquisition vertical from zero to first campaign. A vertical launch turns an audience hypothesis such as independent dental practices, auto repair shops, or bookkeeping firms into a tracked lead generation batch, qualified contacts, a draft Instantly campaign, and an active monitoring loop.
+
+The workflow has five phases:
+
+1. Define the batch and qualification rules.
+2. Create the batch tracker.
+3. Run the lead generation pipeline.
+4. Launch the outreach campaign.
+5. Monitor replies and campaign quality.
+
+Define the Batch
+
+Choose a batch ID using the acquisition naming convention: {vertical}-{number}, for example dental-1, auto-1, or home-1.
+
+Record the batch configuration in the tracker before running pipeline stages. At minimum, capture:
+
+- Target description, such as "independent dental practices in Orange County, California".
+- Search queries for the initial source pull.
+- Region: county, state, country, or other geography accepted by the scraper workflow.
+- Minimum review count and minimum rating, when Google Maps quality thresholds matter.
+- Custom disqualification rules, such as excluding chains, franchises, pediatric-only practices, or irrelevant subcategories.
+- Website crawl keywords, such as about, team, staff, contact, services, or vertical-specific service pages.
+
+Use packages/elevasis-operations/src/sales/prospecting/constants.ts as the batch registry. Current launch work should keep the tracker as the human-readable source and pass qualification criteria through the workflow input, list qualification metadata, or the registered batch config for the stage being run.
+
+Create the Batch Tracker
+
+Create a tracker from the acquisition batch template:
+
+text
+apps/docs/content/docs/operations/client-acquisition/outreach/batches/template.mdx
+
+Place the new tracker in the pending batch directory:
+
+text
+apps/docs/content/docs/operations/client-acquisition/outreach/batches/pending/{batch-id}.mdx
+
+Fill in the frontmatter with status: in-progress, then complete the batch configuration table before running pipeline work. The tracker should make it possible to reconstruct the vertical, region, search inputs, disqualification rules, and campaign state without reading execution logs.
+
+Run Lead Generation
+
+Run the lead generation stages with the platform CLI from the monorepo root so .env.development and .env.production resolve correctly.
+
+Stage 01: Google Maps Scrape
+
+Use the Google Maps scrape workflow to acquire initial companies:
+
+bash
+pnpm exec elevasis exec Elevasis/lgn-01a-google-maps-scrape-workflow --input '{"searchQueries":["dentist","dental clinic"],"county":"Orange County","state":"California"}' --async
+
+After the execution starts, record the execution ID and source counts in the batch tracker.
+
+Local Website Crawl
+
+Run the local website crawler against the batch:
+
+bash
+pnpm -C scripts/web-scraper run crawl -- {batch-id}
+
+The crawl should capture relevant sub-pages for LLM extraction. If vertical-specific keywords are not available in the active code path, use the default crawl coverage and note any manual crawl gaps in the tracker before extraction.
+
+Stage 02: Website Extract
+
+Extract structured company profile data from crawl output:
+
+bash
+pnpm exec elevasis exec Elevasis/lgn-02-website-extract-workflow --input '{"batchId":"{batch-id}"}' --async
+
+Stage 03: Company Qualification
+
+Qualify companies using the target description, review thresholds, rating thresholds, and custom rules captured in the tracker. If the workflow does not resolve criteria automatically for the batch, pass the criteria explicitly in the input or attach them through the list qualification surface before running the stage.
+
+bash
+pnpm exec elevasis exec Elevasis/lgn-03-company-qualification-workflow --input '{"batchId":"{batch-id}","criteria":{"targetDescription":"Independent dental practices in Orange County, California","minimumReviewCount":5,"minimumRating":3,"customRules":"Disqualify franchises and chains. Disqualify orthodontics-only and pediatric-only practices."}}' --async
+
+For list-oriented runs, use listId instead of batchId; list configuration takes priority over the batch registry unless an explicit criteria override is provided.
+
+Stage 04: Email Discovery
+
+Discover contacts for qualified companies:
+
+bash
+pnpm exec elevasis exec Elevasis/lgn-04-email-discovery-workflow --input '{"batchId":"{batch-id}"}' --async
+
+Stage 05: Email Verification
+
+Verify discovered emails before campaign upload:
+
+bash
+pnpm exec elevasis exec Elevasis/lgn-05-email-verification-workflow --input '{"batchId":"{batch-id}"}' --async
+
+When verification completes, update the tracker with company counts, contact counts, usable email counts, and set the batch status to ready if campaign launch prerequisites are satisfied.
+
+Launch the Campaign
+
+Use the acquisition outreach workflow to move a ready batch into Instantly:
+
+1. Check account inventory with ist-account-inventory-workflow.
+2. Personalize contacts with ist-personalization-workflow.
+3. Create a draft campaign with ist-campaign-create-workflow and activate: false.
+4. Create the tracking list with ist-campaign-list-workflow.
+5. Upload contacts with ist-upload-workflow, dry run first and then real.
+6. Activate with ist-campaign-activate-workflow.
+7. Update the tracker to status: active and fill in campaign metadata.
+
+Keep the first campaign small enough to evaluate copy and deliverability. Prefer 100-200 contacts per segment, 1-2 contacts per company, and conservative sending volume until benchmarks are visible.
+
+Monitor and Optimize
+
+After launch, monitor both campaign metrics and inbound replies:
+
+- Use /acquisition --outreach for campaign review and analytics.
+- Use /acquisition --inbound status for reply handling and active deal state.
+- Watch open rate, reply rate, positive reply rate, and bounce rate.
+- Pause or repair the campaign if bounce rate rises above the accepted threshold.
+- Rework subject lines, personalization, or offer framing when reply rate is below target.
+
+Every optimization pass should write back to the tracker: what changed, why it changed, and what result would justify scaling the vertical.
+
+Launch Checklist
+
+- Batch ID selected with {vertical}-{number} naming.
+- Batch tracker created from the template.
+- Target description, geography, search queries, thresholds, and custom rules recorded.
+- Stage 01 scrape execution complete.
+- Website crawl complete or crawl gaps documented.
+- Stage 02 extraction complete.
+- Stage 03 qualification complete with explicit criteria source.
+- Stage 04 email discovery complete.
+- Stage 05 email verification complete.
+- Tracker status set to ready.
+- Draft Instantly campaign created.
+- Tracking list created and contacts uploaded.
+- Campaign activated.
+- Tracker status set to active with campaign metadata.`
+  },
+  {
+    id: "knowledge.upwork-calibration-strategy",
+    title: "Upwork Calibration Strategy",
+    summary: "Deep calibration process for Upwork queries, including scan parameters, scoring, duplicate handling, output format, verdict criteria, and current calibration results.",
+    bodyText: "Overview\n\nUse this playbook when running a deep calibration scan for one or more Upwork queries. Calibration is separate from daily scanning: it evaluates query quality, competition, uniqueness, and noise patterns so the active saved-query set stays healthy.\n\nUse calibration when:\n\n- Testing a new query candidate before adding it to active scans.\n- Re-evaluating an active query whose health score has declined.\n- Running periodic re-calibration of the full active query set. Quarterly is the default cadence.\n\nUse knowledge.upwork-query-strategy for the active query table and knowledge.upwork-scanning-playbook for the daily scan workflow.\n\nScan Parameters\n\n| Parameter | Value | Rationale |\n| --------- | ----- | --------- |\n| Max posts | 20 per query | Enough for confidence without turning calibration into an archive. |\n| Max age | 2 weeks | Captures 2 full hiring cycles; older posts are stale. |\n| Filters | U.S. only, Most Recent | Matches the standard scan surface while preserving full competition visibility. |\n| Proposal filter | None | Calibration needs to see competition levels, not hide them. |\n| Extraction | Search page script | Capture title, snippet, budget, proposals, and client info without click-in enrichment. |\n\nCalibration Process\n\n1. Check the Upwork query registry for the exact candidate query and close variants.\n2. Re-test a dropped query only if the search terms or market conditions have changed.\n3. Navigate to https://www.upwork.com/nx/search/jobs/.\n4. Enter the query and apply U.S. only plus Most Recent sort.\n5. Run the search-card extraction script from the operations docs.\n6. If more than 20 results are visible, analyze only the first 20.\n7. If fewer than 20 results are visible, analyze all visible posts.\n8. Record the exact result count shown by Upwork in the search header.\n9. Score each extracted post with the calibration relevance rubric.\n10. For each post scoring 50+, check whether it appears in other query calibration docs.\n11. Write the per-query calibration doc and update the summary results.\n\nRelevance Rubric\n\nFor each extracted post, assign a relevance score from 0 to 100. The core question is whether the client needs a system, workflow, integration, automation, or operational build that Elevasis can deliver.\n\n| Score Range | Tier | Meaning |\n| ----------- | ---- | ------- |\n| 75-100 | Strong fit | Clear build intent, named platforms or tools, business context, and specific deliverable. |\n| 50-74 | Possible fit | Some build signals, but scope or domain is ambiguous. |\n| 25-49 | Weak fit | Marginally related and mostly noise. |\n| 0-24 | Irrelevant | Hiring posts, marketing or design work, personal projects, manual work, or VA work. |\n\nAuto-score disqualifiers in the 0-10 range even if they contain automation language:\n\n- Hiring for a role.\n- Marketing, design, or funnel work.\n- Manual or VA tasks.\n- Personal, non-business projects.\n\nDuplicate Handling\n\nFor each post scoring 50+, check whether the same job appeared in another query's calibration output. Mark it with DUPE: Q{N} when found.\n\nTrack total relevance and unique relevance separately. A query with 60% relevance but 0% unique relevance is usually not worth keeping because it adds scan time without adding opportunity coverage.\n\nOutput Format\n\nPer-query calibration docs use this naming pattern:\n\ntext\nq{NN}-{slug}.mdx\ncandidate-{slug}.mdx\nsummary.mdx\n\nUse active-query filenames such as q15-system-nouns.mdx and candidate filenames such as candidate-pipedrive.mdx.\n\nEach per-query doc should include:\n\n- Frontmatter with title, exact query, scan date, total Upwork result count, analyzed post count, relevant count, and verdict.\n- A ## Posts section with post-level scoring.\n- A ## Summary section with relevance rate, high-relevance count, perfect fits, low-competition gems, unique posts, noise patterns, why the query works or fails, and final verdict.\n\nKeep irrelevant posts short. Relevant posts should include budget, proposals, posted age, client signal, description snippet, relevance rationale, and uniqueness or duplicate marker.\n\nVerdict Criteria\n\n| Verdict | Criteria |\n| ------- | -------- |\n| KEEP (strong) | More than 40% relevance, more than 20% unique relevance, more than 2 low-competition gems, and fresh posts within 1 week. |\n| KEEP (borderline) | 25-40% relevance, or low unique relevance but useful low-competition gems. Trial for 3 scans. |\n| MONITOR | Relevant posts exist but are flooded with 20-50 proposals. Cherry-pick only; do not treat as a core saved search. |\n| DROP | Less than 20% relevance, 0 low-competition gems, dead volume under 5 results, or all stale posts older than 2 weeks. |\n\nQuick vs Deep Calibration\n\n| Aspect | Quick Screening | Deep Calibration |\n| ------ | --------------- | ---------------- |\n| Purpose | Fast keep/drop triage for new candidates. | Full analysis for active-query management. |\n| Posts | All visible, no hard max. | Max 20, max 2 weeks old. |\n| Scoring | Inline summary table. | Per-post entries with rationale. |\n| Output | Task notes or conversation. | Dedicated calibration MDX document. |\n| Duplicate check | Informal overlap note. | Formal cross-reference with post numbers. |\n| Use case | Bulk screening 5+ candidates. | Promotion, quarterly review, or declined health score. |\n\nCurrent Calibration Results\n\nLast full calibration: 2026-03-29.\n\nDeep scan results exist as original scan session notes. Formal per-query calibration files have not yet been written.\n\n| Current Q# | Query | Total | Rel | Unique Rel | Calibration Status |\n| ---------- | ----- | ----- | --- | ---------- | ------------------ |\n| Q1 | System nouns | 47 | 60% | 30% | Not yet written: q15-system-nouns.mdx. |\n| Q2 | GHL | 111 | 50% | 45% | Not yet written: q16-ghl.mdx. |\n| Q3 | AR/AP/Collections | 66 | 40% | 30% | Not yet written: q01-ar-ap-collections.mdx. |\n| Q4 | Inventory | 69 | 40% | 35% | Not yet written: q06-inventory.mdx. |\n| Q5 | Invoice/billing | 67 | 55% | 30% | Not yet written: q04-invoice-billing.mdx. |\n| Q6 | CRM | 370 | 40% | 20% | Not yet written: q08-crm.mdx. |\n| Q7 | API integration | 298 | 40% | 15% | Not yet written: q14-api-integrate.mdx. |\n| Q8 | Pipedrive | 10 | 40% | 30% | Quick scan only; no deep calibration file yet. |\n\nThe current query numbers match knowledge.upwork-query-strategy. The older calibration filenames reflect original 16-query scan numbering.\n\nNoise Patterns\n\nCommon noise patterns across calibrated queries:\n\n- Hiring posts: the top noise source across all queries, especially CRM and API searches.\n- Marketing and funnel work: especially common in GHL-adjacent searches.\n- Bookkeeper and accountant roles: common in AR/AP and invoice searches.\n- BI and analytics specialist work: common in invoice/billing and API searches.\n- High competition: broad CRM and API queries often attract 20-50+ proposals.\n\nCross-Query Overlap\n\nThe highest-overlap pairs from calibration:\n\n- Q3 AR/AP and Q5 Invoice/billing overlap heavily on financial automation posts.\n- Q6 CRM and Q7 API catch many of each other's broad integration posts.\n- Q1 System nouns produces the most unique gems and remains the strongest standalone query."
+  },
+  {
+    id: "knowledge.upwork-query-strategy",
+    title: "Upwork Query Strategy",
+    summary: "Active saved-query set, tiering, calibration outcomes, query-design principles, and failure modes for the Upwork acquisition channel.",
+    bodyText: 'Overview\n\nUse this reference to choose which Upwork saved searches to scan, understand why each query is active, and avoid repeating failed discovery work. The active query set targets niche operations and business-process automation jobs rather than broad "AI automation" searches, which are usually saturated.\n\nUse knowledge.upwork-scanning-playbook for the scan workflow and knowledge.upwork-calibration-strategy for deep query calibration.\n\nActive Saved Queries\n\nThe active saved-query set has 14 queries as of 2026-03-31. Q1-Q7 were kept after the full calibration scan of the original 16 queries. Q8 Pipedrive was added after SaaS platform calibration. Q9-Q14 are formerly monitor-tier queries moved into active scanning with stricter freshness and competition discipline.\n\n| Tier | #  | Query | Relevance | Unique Rel | Rationale |\n| ---- | -- | ----- | --------- | ---------- | --------- |\n| T1 | 1 | ("booking system" OR "intake form" OR "scheduling system" OR "ticketing system" OR "tracking system" OR "reservation system" OR "billing system" OR "payment system") AND (build OR automate OR custom) | 60% | 30% | Best query. SMB owners describe systems they need built. Lowest competition and highest ROI per connect. |\n| T1 | 2 | ("GoHighLevel" OR "GHL") AND (build OR setup OR integration OR workflow OR automate) | 50% | 45% | GHL niche with high unique relevance. "Funnel" was removed because it pulled marketing noise; "automate" replaced it. |\n| T2 | 3 | ("accounts receivable" OR "accounts payable" OR "collections") AND automate | 40% | 30% | "Automate" catches real builds and maps to the Xero testimonial. Some overlap with Q1 and Q7. |\n| T2 | 4 | "inventory" AND ("automation" OR "integration" OR "sync") | 40% | 35% | Inventory system builds are unique to this query. Low cross-query overlap. |\n| T3 | 5 | ("invoice" OR "billing") AND ("automate" OR "integration") | 55% | 30% | Finds healthcare EDI, Stripe Connect, and Power Automate AP work. Heavy Q3 overlap. |\n| T3 | 6 | "CRM" AND ("integration" OR "automate" OR "migrate") | 40% | 20% | Finds Twenty CRM, HubSpot Service Hub, and Zoho automation. Noisy and high-volume. |\n| T3 | 7 | "integrate" AND "API" AND (build OR develop OR custom) | 40% | 15% | Finds strong integration work such as Authorize.Net webhooks and Email-to-ERP pipelines. Competition is often high. |\n| T3 | 8 | "Pipedrive" AND (build OR setup OR integration OR workflow OR automate) | 40% | 30% | CRM setup and automation builds. Only platform query besides GHL to pass calibration. Trial query; evaluate after 3 scans. |\n| T4 | 9 | ("Zapier" OR "Make.com" OR "n8n") AND (automate OR build OR workflow) | Very high | -- | High relevance but competition risk. Apply only to posts with fewer than 10 proposals. |\n| T4 | 10 | "SaaS" AND ("MVP" OR "prototype") AND (build OR develop) | High | -- | Bimodal competition: some low-proposal gems, some flooded posts. Skip flooded posts. |\n| T4 | 11 | "Google Sheets" AND (automate OR app OR dashboard OR replace) | 40% | -- | Fresh and even competition spread. Good posts get flooded quickly, so prioritize speed. |\n| T4 | 12 | "chatbot" AND (build OR custom OR develop) | 25% | -- | Low relevance baseline. Pulls AI engineering hiring and chat UI work, but occasional SMB gems exist. |\n| T4 | 13 | ("voice agent" OR "AI receptionist") AND (build OR develop OR custom) | High | -- | Very low volume, often 1-2 results. High quality when fresh posts appear. |\n| T4 | 14 | "sales funnel" AND (automate OR build OR system OR custom) | 40% | -- | Fresh GHL integrations and CRM builds mixed with affiliate-funnel noise. Filter hard. |\n\nAll active queries use the Upwork proposal-count filters "Less than 5" and "5 to 10". Tier 1 queries are the primary scan focus. Tier 2 queries are solid contributors. Tier 3 queries are borderline and should be dropped if health scores decline across 3 or more scans. Tier 4 queries have higher competition risk and should only be applied to fresh, low-proposal posts.\n\nQuery Design Principles\n\nStrong Upwork queries describe the system the buyer needs, not the freelancer category they think they are hiring.\n\nUse:\n\n- Specific operational system nouns such as booking system, intake form, scheduling system, ticketing system, tracking system, reservation system, billing system, and payment system.\n- Action verbs such as build, automate, custom, develop, setup, integration, and workflow.\n- Platform-specific searches when system-build intent overlaps with implementation work, such as GoHighLevel, Pipedrive, CRM, API integration, and inventory sync.\n- The Q1 pattern: specific system noun plus action verb. This catches clients describing the thing they need built.\n- The proposal-count filter from 0-10 proposals. Competition control is non-negotiable.\n\nAvoid:\n\n- Vertical keywords such as clinic, contractor, salon, or real estate. On Upwork these usually pull marketing or hiring posts for that industry, not system buyers from that industry.\n- Pain-signal phrases such as "hours per week", "manual", "repetitive", or "bottleneck". On Upwork these usually mean the client is hiring humans to perform the work.\n- Migration terms such as migrate, replace, or switch unless tied to a concrete platform or system. Generic migration queries pull website and email platform changes.\n- Broad tool or category nouns such as portal, dashboard, tool, or custom without a specific system type.\n- Solution-first keywords such as AI automation, AI agent, and workflow automation. They attract the saturated AI freelancer crowd.\n- Revenue-proximity service terms such as cold email, outbound, nurture, appointment setting, and qualify leads. These are proposal-positioning angles, not good Upwork query filters.\n- Professional-service terms such as contract review, due diligence, or reputation management. They pull human professionals rather than system builds.\n\nQuery Evolution\n\nDiscovery is complete for the current strategy: 127 queries were tested across 18 rounds and calibrated to 14 active queries. The current ROI lever is execution quality: faster scans, stronger proposal targeting, and query-health monitoring.\n\nQ1 has 8 proven system nouns:\n\n- Booking system.\n- Intake form.\n- Scheduling system.\n- Ticketing system.\n- Tracking system.\n- Reservation system.\n- Billing system.\n- Payment system.\n\nTwenty-three other system nouns were tested and failed. Before testing any new query, check the Upwork query registry in the operations docs for prior verdicts and failure modes.\n\nKnown Limitations\n\n- The "U.S. only" checkbox does not persist with saved searches. It is a session-only filter and must be manually checked each time a saved search loads.\n- Upwork search is not strict phrase matching. A quoted phrase such as "client portal" can still match posts containing the words separately.\n- Relevance percentages are from the expanded 2026-03-29 evaluation: 147 jobs across 15 queries plus 32-query discovery analysis. Re-evaluate monthly as job mix shifts.\n\nLive Reference Docs\n\nPreserve these operations docs because they remain live working references rather than migrated Knowledge Map content:\n\n- apps/docs/content/docs/operations/client-acquisition/upwork/query-registry.mdx tracks all 127 tested queries, verdicts, and failure modes.\n- apps/docs/content/docs/operations/client-acquisition/upwork/scripts.mdx stores runnable browser extraction scripts and current Upwork DOM notes.'
+  },
+  {
+    id: "knowledge.upwork-scanning-playbook",
+    title: "Upwork Scanning Playbook",
+    summary: "Stable scanning, scoring, freshness, and query-health workflow for the Upwork acquisition channel.",
+    bodyText: 'Overview\n\nUse this playbook to run the Upwork acquisition scanning loop. The goal is to find fresh, low-competition jobs where Elevasis can deliver a real business system, score them consistently, and turn the best opportunities into proposals through the Upwork proposal playbook.\n\nThe scanning loop has six phases:\n\n1. Confirm browser and login readiness.\n2. Run saved search queries with the right filters.\n3. Extract fresh job cards.\n4. Deduplicate, score, and enrich strong candidates.\n5. Write the scan output.\n6. Review query health before the next scan.\n\nProposal copy and response handling are intentionally separate. Use knowledge.upwork-proposal-playbook for proposal strategy and knowledge.upwork-response-templates for client replies.\n\nPreconditions\n\nBefore scanning, verify the browser automation surface is available and Upwork is logged in.\n\n- Chrome tooling must be available through the active browser automation tools.\n- The Upwork search page must load at https://www.upwork.com/nx/search/jobs/.\n- The page must show the job search interface, not a login prompt.\n- If login is required, stop and log in manually before scanning again.\n\nDo not try to work around a missing browser session by inventing scan results. The scan depends on live Upwork search pages, current saved-search filters, and the visible result cards.\n\nScan Surface\n\nRun scans from the Upwork search page:\n\ntext\nhttps://www.upwork.com/nx/search/jobs/\n\nEach saved query is run individually. Apply the filters every time, because Upwork search state is session-dependent and not always persisted across queries.\n\n| Filter    | Value       | Reason                                                                 |\n| --------- | ----------- | ---------------------------------------------------------------------- |\n| U.S. only | Checked     | Higher-quality clients, stronger timezone fit, more verified payments. |\n| Sort by   | Most Recent | Freshness is the strongest conversion lever.                           |\n| Proposals | \\<5, 5-10 | Low competition is required before spending connects.                  |\n\nUse saved queries as the primary scan source. The strategy targets operational system-build terms, not generic "AI automation" searches that attract high competition.\n\nFreshness Rule\n\nOnly collect posts from the last 12 hours. Results should be sorted by Most Recent, so stop extracting for a query once the visible posts are older than 12 hours. Do not do catch-up windows.\n\nFreshness priority:\n\n| Post age   | Action                                                           |\n| ---------- | ---------------------------------------------------------------- |\n| 0-1 hour   | Highest priority. Client is most likely active and shortlisting. |\n| 1-12 hours | Valid scan window. Still worth scoring if competition is low.    |\n| 12+ hours  | Skip. The client has usually already formed the shortlist.       |\n\nRecord the scan timestamp as lastscanned in the daily scan doc frontmatter. This timestamp helps avoid reprocessing posts from prior scans, but the hard 12-hour cap still applies.\n\nRun Each Query\n\nFor each active saved query:\n\n1. Clear the search box.\n2. Enter the query string and submit.\n3. Apply U.S. only, Most Recent, and proposal-count filters.\n4. Wait for results to render.\n5. Extract visible job cards from the search page.\n6. Stop once a post exceeds the freshness cutoff.\n7. Tag each job with the source query.\n\nThe first page of most-recent, low-proposal results is the high-value slice. Do not paginate unless a specific investigation requires it.\n\nWhile scanning the API integration query, flag custom dashboard opportunities where a custom build is likely better than Power BI, Looker, Tableau, or a spreadsheet. Strong signs include 3+ data sources, live dashboard requirements, AI-generated summaries, anomaly detection, or workflow triggers.\n\nExtract Job Card Data\n\nThe search-card extraction should capture the fields needed for initial triage:\n\n- Title.\n- Upwork job URL path.\n- Posted age.\n- Proposal count.\n- Budget or hourly range.\n- Payment verification.\n- Client rating.\n- Total client spend.\n- Description snippet.\n- Source query.\n\nDeduplicate by Upwork job URL path after all queries finish. If a job appears under multiple queries, keep one row and note the overlap.\n\nScore and Enrich\n\nScoring has two stages.\n\nStage 1: Relevance\n\nScore relevance from 0 to 100 by asking whether the client needs a system, workflow, integration, automation, or operational build that Elevasis can deliver.\n\n| Range  | Label        | Criteria                                                                  |\n| ------ | ------------ | ------------------------------------------------------------------------- |\n| 75-100 | Strong fit   | Clear build intent, specific business workflow, named tools or outputs.   |\n| 50-74  | Possible fit | Some build signals, but scope or buyer intent is ambiguous.               |\n| 25-49  | Weak fit     | Marginally related, mostly noise, low business-system signal.             |\n| 0-24   | Irrelevant   | Hiring, marketing, design, manual VA work, personal projects, or errands. |\n\nDisqualify posts that are clearly hiring a role, outsourcing manual work, asking for generic marketing/design help, or describing a personal/non-business project.\n\nStage 2: Application Priority\n\nApply tactical modifiers after relevance scoring. The final score determines whether to draft a proposal.\n\n| Signal         | Positive indicators                                  | Negative indicators                         |\n| -------------- | ---------------------------------------------------- | ------------------------------------------- |\n| Freshness      | \\<1h or same-session post.                         | 8-12h old, or outside the scan window.      |\n| Competition    | \\<5 proposals, or 5-10 with strong fit.            | 10+ proposals, especially 20+.              |\n| Client quality | Payment verified, spend history, good rating, hires. | Unverified, no history, 0% hire rate.       |\n| Budget         | Fixed \\>$5K or hourly \\>$75/hr.                  | Fixed \\<$1K or hourly \\<$40/hr.         |\n| Fit            | Workflow, integration, dashboard, CRM, operations.   | Copywriting, funnels, ads, hiring, support. |\n\nOnly enrich posts with a strong enough relevance score to matter, usually 65+. For those posts, open the job detail view and capture:\n\n- Hire rate.\n- Jobs posted.\n- Member since.\n- Company size.\n- Last viewed by client.\n- Interviewing count.\n\nUse this data to avoid over-ranking stale or low-quality clients that have a good-sounding job description but weak application ROI.\n\nWrite the Scan Output\n\nWrite scan docs under:\n\ntext\napps/docs/content/docs/operations/client-acquisition/upwork/scans/{YYYY-MM-DD}.mdx\n\nIf a scan doc already exists for the day, append the new scan as a later section instead of creating a second daily file.\n\nEach scan output should include:\n\n- Date and timestamp.\n- Freshness cutoff.\n- Queries scanned.\n- Total posts collected.\n- Deduplicated count.\n- Top opportunities only.\n- Comparison table.\n- Query health table.\n- Draft proposals section, when proposals are generated.\n\nKeep scan docs as decision tools, not archives. Include the top 10 ranked opportunities rather than every collected post.\n\nQuery Health\n\nAfter scoring, compute a query-health score so weak searches can be removed over time.\n\n| Metric          | Measurement                                                       | Weight |\n| --------------- | ----------------------------------------------------------------- | ------ |\n| Fresh posts     | Count within cutoff, normalized against 5 posts.                  | 25%    |\n| Low competition | Percent with fewer than 10 proposals.                             | 25%    |\n| Relevance       | Percent actionable after deduplication and disqualification.      | 30%    |\n| Client quality  | Percent with verified payment and useful spend or rating signals. | 20%    |\n\nQueries that score 0 across 3+ consecutive scans are drop candidates. Compare the latest query-health table with the previous scan before changing the active query set.\n\nActive Query Principles\n\nStrong Upwork queries describe the system the buyer needs, not the freelancer category they think they are hiring.\n\nUse:\n\n- Specific operational system nouns such as booking system, intake form, scheduling system, ticketing system, tracking system, reservation system, billing system, and payment system.\n- Action verbs such as build, automate, custom, develop, setup, integration, and workflow.\n- Platform-specific searches where system-build intent overlaps with implementation work, such as GoHighLevel, Pipedrive, CRM, API integration, or inventory sync.\n\nAvoid:\n\n- Broad solution-first terms such as AI automation, AI agent, workflow automation, portal, dashboard, tool, or custom without a specific system noun.\n- Vertical keywords such as clinic, contractor, salon, or real estate unless paired with concrete system intent.\n- Pain-signal phrases that usually mean the client is hiring a human to perform manual work.\n- Revenue-proximity service terms such as cold email, appointment setting, outbound specialist, or funnel work.\n\nBefore testing a new query, read knowledge.upwork-query-strategy and check the Upwork query registry in the operations docs so old failure modes are not repeated. Use knowledge.upwork-calibration-strategy when promoting, dropping, or re-evaluating saved searches.\n\nProposal Handoff\n\nAfter the scan, draft proposals only for opportunities that remain strong after relevance, tactical modifiers, and client-quality checks.\n\nFor proposal drafting:\n\n1. Load knowledge.upwork-proposal-playbook.\n2. Read the top opportunities from the latest scan doc.\n3. Select the right proposal template by scope, budget, and relevance.\n4. Tailor the opening, proof point, plan, and two discovery questions.\n5. Append draft proposals to the scan doc under ## Draft Proposals.\n\nUse knowledge.upwork-response-templates after a client replies or sends an offer.\n\nScan Checklist\n\n- Browser tooling available.\n- Upwork logged in.\n- Search page loaded.\n- U.S. only filter applied.\n- Sort set to Most Recent.\n- Proposal-count filters applied.\n- All active saved queries scanned.\n- Posts older than 12 hours skipped.\n- Jobs deduplicated by URL path.\n- Relevance scores assigned.\n- Strong candidates enriched from detail view.\n- Final scores sorted descending.\n- Daily scan doc created or appended.\n- Query health table written.\n- Top proposal candidates handed to knowledge.upwork-proposal-playbook.'
+  },
+  {
+    id: "knowledge.youtube-obs-recording-setup",
+    title: "YouTube OBS Recording Setup",
+    summary: "Canonical OBS Studio recording setup for Elevasis YouTube production, covering 1080p60 screen capture, safe recording format, NVENC quality settings, audio routing, face-camera scenes, and pre-recording checks.",
+    bodyText: `Overview
+
+Use this setup for Elevasis YouTube recordings that combine a short face-camera intro with Command Center or workflow screen capture. The target output is a clean 1080p60 source file that YouTube can re-encode without avoidable motion, audio, or color artifacts.
+
+Baseline configuration:
+
+text
+Video:   1920x1080, 60fps, NV12, Rec. 709 Partial
+Encode:  NVENC H.264, CQP 18, P5 preset, High profile
+Format:  MKV with automatic remux to MP4
+Audio:   48 kHz stereo, 320 kbps AAC, mixed plus mic-only tracks
+Camera:  Insta360 Link 2C at 1080p60 with circle mask
+Scenes:  Face + Screen on F5, Screen Only on F6
+
+Prefer 1080p60 over 4K30 for screen recordings. Smooth cursor motion, scrolling, typing, and app transitions matter more than pixel density, and most viewers watch at 1080p or below. 4K30 produces larger files, slower editing, and visibly choppier screen motion.
+
+Recording Output
+
+Record to MKV, not MP4. MKV writes continuously, so a crash usually leaves the file usable. MP4 writes its index at the end, so a crash can corrupt the recording.
+
+Enable automatic remux:
+
+text
+Settings > Advanced > Recording > Automatically remux to mp4
+
+After each recording, upload the remuxed MP4 and keep the MKV as the backup.
+
+Use the advanced recording output mode:
+
+text
+Settings > Output > Output Mode: Advanced
+Recording Tab:
+  Type:                  Standard
+  Recording Format:      mkv
+  Encoder:               NVIDIA NVENC H.264
+  Rate Control:          CQP
+  CQ Level:              18
+  Keyframe Interval:     2
+  Preset:                P5 (Slow)
+  Profile:               high
+  Look-ahead:            checked
+  Psycho Visual Tuning:  checked
+  Max B-frames:          2
+
+CQP 18 is the stable quality target for screen content. It is visually lossless for this use case and gives YouTube a high-quality source before its VP9 or AV1 re-encode.
+
+Fallback encoders:
+
+- AMD GPU: use AMD HW H.264 (AMF) with equivalent CQP settings.
+- No dedicated GPU: use x264, CRF 18, CPU preset slow, or medium if the CPU struggles.
+
+Set audio bitrates:
+
+text
+Output > Advanced > Audio:
+  Track 1: 320 kbps
+  Track 2: 320 kbps
+
+Video Settings
+
+Use a 1080p canvas and output:
+
+text
+Settings > Video:
+  Base (Canvas) Resolution:    1920x1080
+  Output (Scaled) Resolution:  1920x1080
+  Downscale Filter:            Lanczos (36 samples)
+  Common FPS Values:           60
+
+Use Rec. 709 limited-range color:
+
+text
+Settings > Advanced:
+  Color Format: NV12
+  Color Space:  709
+  Color Range:  Partial
+
+YouTube expects Rec. 709 limited range. Full range can produce washed-out or overly contrasty results after processing.
+
+For a 3440x1440 ultrawide monitor, crop the display capture to the center 16:9 region before it is downscaled:
+
+1. Add Display Capture for the primary monitor.
+2. Right-click the source and open Transform > Edit Transform.
+3. Set Crop Left to 440 and Crop Right to 440.
+4. Right-click the source again and select Transform > Fit to Screen.
+
+This crops the capture to the center 2560x1440 region. Keep recorded windows inside that center area. A Windows 11 FancyZones center 16:9 zone is useful for keeping Command Center, browser, and terminal windows inside the captured area.
+
+Use Window Capture only when the recording is limited to one browser window. Display Capture is better for tutorials that switch windows, show the taskbar, or tile terminal and browser views.
+
+Audio Settings
+
+Global audio settings:
+
+text
+Settings > Audio:
+  Sample Rate:           48 kHz
+  Channels:              Stereo
+  Desktop Audio:         Default
+  Mic/Auxiliary Audio:   Focusrite USB Audio (Scarlett 2i2)
+
+Set the Focusrite input in Windows before recording:
+
+1. Open Windows Sound Settings.
+2. Select the Focusrite USB Audio input.
+3. Set format to 48000 Hz, 24-bit.
+
+Physical Focusrite setup:
+
+- Turn 48V phantom power on for the Lewitt LCT 240 PRO condenser.
+- Start input gain at 12 o'clock and adjust so peaks land around -12 dB.
+- Keep Direct Monitor off to avoid double-monitoring.
+
+Apply OBS mic filters to the Mic/Aux source in this exact order:
+
+| Order | Filter            | Settings                                                                 |
+| ----- | ----------------- | ------------------------------------------------------------------------ |
+| 1     | Noise Suppression | RNNoise                                                                  |
+| 2     | Noise Gate        | Close -40 dB, Open -35 dB, Attack 10 ms, Hold 200 ms, Release 100 ms     |
+| 3     | Compressor        | Ratio 3:1, Threshold -18 dB, Attack 6 ms, Release 60 ms, Output Gain 6 dB |
+| 4     | Limiter           | Threshold -3 dB, Release 60 ms                                           |
+
+This order removes steady noise first, gates silence-period noise second, evens speech dynamics third, and catches peaks last. Do not add a Gain filter unless the signal is still too quiet after setting the Scarlett gain.
+
+Multi-Track Audio
+
+Record mixed audio and isolated mic audio:
+
+text
+Settings > Output > Advanced > Recording Tab:
+  Audio Track: check 1 and 2
+
+Route tracks in Audio Mixer > Advanced Audio Properties:
+
+| Source        | Track 1 | Track 2 |
+| ------------- | ------- | ------- |
+| Desktop Audio | checked | empty   |
+| Mic/Aux       | checked | checked |
+
+Track 1 is YouTube-ready mixed audio. Track 2 is mic-only audio for cleanup or editing.
+
+Scene Setup
+
+Create two scenes.
+
+Face + Screen
+
+Use this scene for the intro and occasional commentary call-ins.
+
+Sources from bottom to top:
+
+1. Display Capture named Screen.
+2. Video Capture Device named Facecam.
+3. Optional image source for a circle border or glow.
+
+Display Capture settings:
+
+text
+Source:          Display Capture
+Display:         Primary monitor
+Capture Method:  Windows 10 (1903 and later)
+Capture Cursor:  checked
+
+Apply the ultrawide crop to this source when recording from the 3440x1440 monitor.
+
+Facecam settings:
+
+text
+Device:        Insta360 Link 2C
+Resolution:    1920x1080
+FPS:           60
+Video Format:  MJPEG or default
+
+Create a 512x512 PNG with a white circle on a black background and store it permanently, for example:
+
+text
+E:\\OBS\\circle-mask.png
+
+Apply it to the Facecam source:
+
+text
+Filters > Image Mask/Blend:
+  Type: Alpha Mask (Colour Channel)
+  Path: E:\\OBS\\circle-mask.png
+
+Resize the facecam source to roughly 300-400 px diameter and place it in a lower corner.
+
+Screen Only
+
+Use this scene for the main tutorial content.
+
+Add the existing Screen source from the Face + Screen scene. Do not duplicate the display capture source.
+
+Hotkeys:
+
+text
+Settings > Hotkeys:
+  Switch to Scene "Face + Screen": F5
+  Switch to Scene "Screen Only":   F6
+  Start Recording:                 Ctrl+F9
+  Stop Recording:                  Ctrl+F10
+
+Avoid hotkeys that collide with the app being recorded. If using F5 inside a browser-heavy recording, choose a different key because F5 refreshes the page.
+
+Recording flow:
+
+1. Start on Face + Screen.
+2. Press Ctrl+F9.
+3. Record a 15-30 second face-camera intro.
+4. Press F6 for Screen Only.
+5. Record the screen walkthrough.
+6. Optionally press F5 to bring face-camera back for commentary.
+7. Press Ctrl+F10 to stop.
+
+For a fade, set Scene Transitions to Fade with a 300 ms duration.
+
+Windows 11 Checks
+
+Before a recording session:
+
+- Disable Xbox Game Bar.
+- Leave GPU scheduling enabled.
+- Run OBS as Administrator if frame drops or black-screen capture occur.
+- Set OBS process priority to Above Normal if the recording drops frames.
+- Use the High Performance power plan during recording.
+
+Upload Quality
+
+YouTube re-encodes every upload. The goal is to provide clean source material.
+
+- Do not upload at YouTube's minimum recommended bitrate.
+- Do not run the recording through HandBrake or another extra encode just to save space.
+- Upload the OBS-remuxed MP4 directly unless the video was edited.
+- If editing in DaVinci Resolve or Premiere, render H.264 at 50 Mbps CBR for 1080p60 or use the YouTube preset.
+
+The OBS output should match YouTube's expected upload shape: MP4 container, H.264 video, AAC-LC audio, 48 kHz stereo, Rec. 709 limited range.
+
+Pre-Recording Checklist
+
+- Scarlett 2i2 phantom power is on and voice peaks around -12 dB.
+- Correct OBS scene is selected, usually Face + Screen.
+- Insta360 Link Controller has AI tracking and HDR enabled when needed.
+- Door is closed, fan or AC is off, and the room is controlled.
+- OBS mic meter peaks in green or yellow, never red.
+- A 10-second test recording has been played back for audio, video quality, and facecam position.
+- The 12-minute warm-up from knowledge.youtube-mental-prep is complete when recording on camera.`
+  },
+  {
+    id: "knowledge.finance-operations-playbook",
+    title: "Finance Operations Playbook",
+    summary: "Operating playbook for Elevasis finance: Xero as the system of record, Stripe payment collection and payout reconciliation, invoicing and AR cadence, tax estimates, deductions, 1099s, and annual filing prep.",
+    bodyText: "Overview\n\nElevasis finance operations run through Xero, with Stripe handling payment collection. Xero is the single source of truth for financial records: business checking bank feeds, Stripe payouts, contractor payments, expenses, invoices, receivables, and year-end exports.\n\nThe finance loop has three connected parts:\n\n1. Invoicing captures client revenue through monthly retainers and Stripe Checkout.\n2. Accounting records and reconciles bank transactions, Stripe payouts, contractor payments, and operating expenses.\n3. Taxes use accurate Xero records for quarterly estimates, deductions, 1099s, and annual filing.\n\nAccounting and Reconciliation\n\nReconcile bank transactions in Xero weekly. Match each bank feed entry to its real-world source before month end.\n\n- Stripe payouts should match against Stripe bank feed activity.\n- Contractor payments should match checking account transfers.\n- Software subscriptions such as Railway, Vercel, Supabase, WorkOS, and OpenAI should be categorized as operating expenses.\n- Unmatched or ambiguous transactions should be flagged for manual review before monthly close.\n\nMaintain the core chart of accounts around revenue, cost of sales, operating expenses, and owner draws. Revenue includes client retainers and one-time project fees. Cost of sales covers contractor labor directly tied to client work. Operating expenses cover SaaS tools, hosting, banking fees, and professional services. Owner draws track business distributions.\n\nConfigure Xero with the connected business checking account, the default tax rate for the business jurisdiction, and the correct financial year end in organization settings.\n\nInvoicing and Accounts Receivable\n\nClient billing runs on a monthly retainer model. Create invoices in Xero at the start of each billing period, send them by Xero email or Stripe Checkout link, record payment after Stripe confirms checkout completion, and reconcile the Stripe payout in Xero.\n\nUse Xero repeating invoices for monthly retainers:\n\n- Frequency: monthly.\n- Start date: billing cycle start date.\n- Approval: automatic approval where the billing terms are stable.\n\nConfigure invoice reminders around the due date: a courtesy reminder 3 days before due date, an overdue notice 1 day after due date, and an escalation notice 7 days after due date.\n\nFor invoices more than 14 days overdue, contact the client directly through the active communication channel, pause active work pending payment confirmation, and resolve the balance before the next billing cycle.\n\nTaxes\n\nTax work depends on accurate Xero records throughout the year. As a pass-through entity, Elevasis business income flows to the owner personal return, so quarterly estimates reduce underpayment risk and year-end exports should be clean enough for a CPA or tax preparer.\n\nQuarterly estimated payment targets:\n\n- Q1: April 15.\n- Q2: June 15.\n- Q3: September 15.\n- Q4: January 15 of the following year.\n\nEstimate payments as roughly 25-30% of net profit for the quarter and pay via IRS Direct Pay or EFTPS.\n\nTrack deductible expenses in Xero during the year: SaaS subscriptions, contractor payments, home office expenses where applicable, professional development, courses, and business banking fees. Keep digital receipts organized by year in the business records folder.\n\nIssue 1099-NEC forms to US-based contractors paid more than $600 in a calendar year. Collect a W-9 before first payment, track annual contractor totals in Xero, file 1099-NEC forms by January 31 of the following year, and file the 1096 summary with the IRS when required.\n\nAt year end, export the Xero profit and loss statement and balance sheet. Provide them to the CPA or tax preparer with issued 1099s, bank statements for the business year, mileage logs if applicable, and home office documentation if applicable."
+  },
+  {
+    id: "knowledge.platform-command-view",
+    title: "Platform Command View",
+    summary: "Reference for Command View, the read-only graph surface for organization automation resources, relationships, manifest validation, graph modes, filters, and troubleshooting.",
+    bodyText: "Overview\n\nCommand View visualizes an organization's automation landscape: agents, workflows, triggers, integrations, external resources, and human checkpoints, plus the relationships between them.\n\nIt answers operational questions such as:\n\n- What does this agent talk to?\n- If a provider goes down, what breaks?\n- What is connected to the CRM?\n- Which resources are hidden, diagnostic-only, or currently relevant to this trace?\n\nAccess Command View through the Knowledge area at /knowledge/command-view.\n\nHow Command View Works\n\nCommand View is a visualization layer over the organization deployment manifest.\n\ntypescript\nconst yourOrgRegistry: DeploymentSpec = {\n  agents: [],\n  workflows: [],\n  triggers: [],\n  integrations: [],\n  humanCheckpoints: [],\n  relationships: {},\n  externalResources: []\n}\n\nArchitecture:\n\n1. Manifest declares resources and relationships.\n2. SDK deploy and API registration validate declared references.\n3. Pre-serialization computes graph data once.\n4. Frontend visualizes cached graph data.\n\nCommand View does not create routing. It displays declarations and runtime topology data.\n\nNode Types\n\n| Type | Purpose | Badge info |\n| --- | --- | --- |\n| Triggers | Entry points such as webhook, schedule, manual, or event triggers | Trigger type |\n| Agents | Autonomous AI resources | Tool count, Knowledge Map, memory |\n| Workflows | Multi-step orchestrations | Step count |\n| Integrations | External service connections | Connection status |\n| External resources | Third-party platforms such as n8n, Make, or Zapier | Platform name |\n| Human checkpoints | Human decision points | Approval required |\n\nNode badges:\n\n- Agents show tool count, Knowledge Map, and memory.\n- Workflows show step count.\n- Integrations show connection status.\n- Triggers show webhook, schedule, manual, or event type.\n- External resources show platform.\n\nEdge Types\n\n| Type | Meaning |\n| --- | --- |\n| Triggers | A trigger initiates a resource |\n| Invokes | A resource calls another resource |\n| Uses | A resource uses an integration |\n| Approval | A resource requests human approval |\n\nDeclaring Relationships\n\nInternal Resources\n\nUse relationships to declare what agents and workflows invoke or use.\n\ntypescript\nconst relationships: ResourceRelationships = {\n  'executive-agent': {\n    triggers: {\n      workflows: ['report-workflow'],\n      agents: ['research-agent']\n    },\n    uses: {\n      integrations: ['integration-gmail', 'integration-attio']\n    }\n  }\n}\n\nTriggers\n\nTriggers declare their own metadata, while routing is declared through relationships.\n\ntypescript\nconst triggers: TriggerDefinition[] = [\n  {\n    resourceId: 'webhook-customer-created',\n    type: 'trigger',\n    triggerType: 'webhook',\n    name: 'Customer Created Webhook',\n    description: 'Triggers when a customer is created in Shopify',\n    status: 'prod',\n    webhookPath: '/webhooks/customer-created'\n  }\n]\n\nTrigger routing is not configured on the trigger object itself.\n\nExternal Resources\n\nExternal resources can declare what they trigger and which integrations they use.\n\ntypescript\nconst externalResources: ExternalResourceDefinition[] = [\n  {\n    resourceId: 'external-n8n-sync',\n    type: 'external',\n    platform: 'n8n',\n    name: 'N8N Product Sync',\n    description: 'Syncs product data from Shopify to internal database',\n    status: 'prod',\n    triggers: { workflows: ['internal-sync-workflow'] },\n    uses: { integrations: ['integration-shopify'] }\n  }\n]\n\nThese declarations document the relationship. They do not programmatically connect the external platform.\n\nHuman Checkpoints\n\nHuman checkpoints declare which resources request approval and where approval can route.\n\ntypescript\nconst humanCheckpoints: HumanCheckpointDefinition[] = [\n  {\n    resourceId: 'approval-sales',\n    name: 'Sales Approval Queue',\n    description: 'Human approval for sales proposals',\n    status: 'prod',\n    requestedBy: { agents: ['sales-agent'] },\n    routesTo: { workflows: ['send-proposal-workflow'] }\n  }\n]\n\nActual human approval decisions are runtime choices, not automatic routing from the declaration alone.\n\nValidation\n\nCommand View shows relationships validated during deploy and API registration.\n\nValidation checks:\n\n- Referenced resource IDs exist.\n- Agent and workflow IDs are unique.\n- External resource references are valid.\n- Human checkpoint routes exist.\n- Model configs have valid providers, models, and API key references.\n\nThese checks cover declared relationships and registry consistency. They do not infer every runtime execution.trigger(...) target, especially when the target is computed dynamically.\n\nWhen validation errors occur, API startup fails with a descriptive error such as:\n\ntext\nRegistryValidationError: [YourOrg] Resource 'my-agent' uses non-existent integration: integration-attio\n\nFix validation errors by updating the manifest to reference the correct IDs or by adding the missing resource definition.\n\nUsing Command View\n\nVisualization Features\n\nCommand View uses Cytoscape graph modes:\n\n- Map: keeps organization structure visible and honors hidden-resource visibility.\n- Trace: resolves directed paths and reveals resources for the active trace.\n- Impact: pivots around the selected node and reveals related resources for impact review.\n\nFilter panel capabilities:\n\n- Search across nodes, relationships, and IDs.\n- Filter by node kind, resource type, environment, topology presence, integrations, and resource facets.\n- Toggle resource visibility and diagnostic/testing resource visibility.\n- Show visible and hidden resource counts in the same control surface.\n\nHidden resource behavior:\n\n- Resource nodes are hidden by default so the organization structure remains readable.\n- Structural nodes remain visible as the navigation skeleton.\n- Selecting a visible node can reveal directly connected hidden resources.\n- Diagnostic and testing resources are hidden by default and can be revealed from the filter panel.\n\nExpand Around behavior:\n\n- Select a node, open Details, and use Expand Around to preview nearby graph context before revealing it.\n- Semantic presets cover coverage, operational dependencies, organization context, and impact paths.\n- Feature, surface, entity, and capability nodes default to Coverage.\n- Resource nodes default to Operational Dependencies.\n- Preview counts show hidden resources before Apply reveals the graph patch.\n\nRead-only constraints:\n\n- No drag and drop.\n- No connection editing.\n- No graph mutation from the visualization layer.\n\nManifest Debugging\n\nUse Command View to verify:\n\n1. Resources appear as nodes.\n2. Relationships show as edges.\n3. Integration connections exist.\n4. Trigger invocations are declared correctly.\n5. Orphaned resources are intentional.\n\nCommon issues:\n\n- Typo in a resource ID reference.\n- Missing relationship declaration.\n- Incorrect integration credential name.\n- External resource missing a bidirectional declaration.\n\nSystem Understanding\n\nUseful exploration questions:\n\n- What triggers this workflow?\n- What integrations does this agent use?\n- What happens after this approval?\n- If this integration fails, what breaks?\n\nVisual patterns:\n\n- Hub nodes with many connections indicate critical resources.\n- Linear chains show sequential workflows.\n- Branching shows conditional logic.\n- Isolated nodes may indicate unused resources.\n\nTroubleshooting\n\nEmpty Graph\n\nLikely causes:\n\n- Organization has no resources defined.\n- Search, environment, node kind, topology, or resource facet filters hide all graph elements.\n- Command View resources are hidden and no structural nodes match current filters.\n- Validation errors prevented serialization.\n\nCheck:\n\n1. API logs for validation errors.\n2. Network tab for the /api/command-view response.\n3. Manifest resources arrays.\n4. Filter panel visibility and filter state.\n\nFix:\n\n- Add resources to the manifest.\n- Fix validation errors.\n- Reveal resources or reset graph filters.\n\nMissing Edges\n\nLikely causes:\n\n- Relationship is not declared in the manifest.\n- Resource ID reference has a typo.\n- Validation passed but the relationship declaration is incomplete.\n\nCheck:\n\n1. Manifest relationships field.\n2. Resource ID spelling and case.\n3. API response includes both nodes.\n\nFix the relationship declaration in the manifest.\n\nNode Not Appearing\n\nLikely causes:\n\n- Resource is not in the correct manifest array.\n- Resource is hidden by visibility controls.\n- Status, resource type, topology, or facet filters exclude the node.\n- Duplicate ID caused validation failure.\n\nCheck:\n\n1. Manifest includes the resource in the correct array.\n2. Filter panel visibility and filter state.\n3. Resource status field.\n4. API logs for duplicate ID errors.\n\nFix by adding the resource, revealing resources, or resetting filters.\n\nValidation Errors on Startup\n\nCommon error shape:\n\ntext\nRegistryValidationError: [OrgName] Resource 'resource-id' uses non-existent integration: integration-name\n\nCommon causes:\n\n- Typo in integration credential name.\n- Resource referenced before definition.\n- Missing import.\n\nFix:\n\n- Verify credential names match integration definitions.\n- Ensure all resources exist in manifest arrays.\n- Check module dependency statements in the manifest module.\n\nBest Practices\n\nKeep relationships current when resources change:\n\n1. Add new tools, then update uses.integrations.\n2. Add workflow invocation, then update triggers.workflows.\n3. Add agent delegation, then update triggers.agents.\n4. Add approval gate, then update the human checkpoint requestedBy.\n\nUse descriptive IDs:\n\n- integration-shopify-store-alpha instead of integration-1.\n- trigger-customer-created-webhook instead of trigger-webhook.\n- approval-sales-proposals instead of approval-1.\n\nValidate early and often:\n\nbash\npnpm dev:api\n\nAPI startup runs registry validation. Fix validation errors immediately because they prevent graph visualization.\n\nReview Command View regularly to onboard team members, plan new features, trace execution paths, and audit integration dependencies.\n\nRelationship Enforcement\n\nRelationships are declarations, not routing.\n\n| Layer | What it does | Enforcement |\n| --- | --- | --- |\n| DeploymentSpec.relationships | Declares relationships such as workflow A triggers workflow B | Validated at startup so IDs must exist |\n| buildEdges() in serialization.ts | Serializes declarations into CommandViewEdge[] | Pure transformation, no runtime check |\n| Runtime workflow and agent code | Calls resources through execution.trigger(...) or equivalent wiring | Independent of declarations |\n\nThe Resource Registry validates that declared targets reference real resource IDs during deploy and registration. However, there is no guarantee that declared graph relationships match runtime reality. Code can call a resource that is not declared in relationships, and that runtime call will not fail solely because the declaration is missing.\n\nEnforcement status:\n\n| Category | Validated at startup | Matches runtime | Status |\n| --- | --- | --- | --- |\n| Resource IDs unique | Yes | Yes, because lookup works | Enforced |\n| Input schema matches execution interface | Yes | Yes, because validation uses it | Enforced |\n| Relationship targets exist | Yes | No, invocations can be dynamic strings | Partially enforced |\n| Trigger routing | No | No, webhook handlers can hardcode routes | Decorative |\n| Tool availability per agent | No | No, tools are built dynamically by factories | Decorative |\n| Model config | Yes | No, runtime selects from environment variables | Decorative |\n| Integration usage | Partially, IDs checked | No, credentials resolve at runtime | Decorative |\n\nNon-Executable Node Types\n\nTriggers, integrations, external resources, and human checkpoints are non-executable node types. They exist for Command View.\n\n- TriggerDefinition does not set up actual routing. Webhook routing is independent.\n- IntegrationDefinition is a credentials reference with provider and credentialName; it does not connect to a provider by itself.\n- ExternalResourceDefinition documents a third-party automation but has no programmatic link to that platform.\n- HumanCheckpointDefinition documents approval queues and routes. Actual routing is determined by human choice and workflow code.\n\nRuntime Relationship Guard\n\nThere is no general runtime guard that discovers every nested execution target at call time. Deployed SDK workers can invoke nested resources through execution.trigger(...) and the API dispatcher, so dynamic targets can drift from DeploymentSpec.relationships even when deploy-time validation passes.\n\nDeploy-Time Validation\n\nResources are deployed through elevasis-sdk deploy. The SDK includes relationships in DeployMetadata, validates the resulting DeploymentSpec locally, and the API validates the merged deployment before registerOrganization().\n\nKey files:\n\n- packages/sdk/src/cli/commands/deploy.ts\n- apps/api/src/deployments/service.ts\n- packages/core/src/platform/registry/validation.ts\n\nAccepted Decorative Gaps\n\nThese gaps are inherent to the architecture and cannot be fully validated at deploy time:\n\n- Runtime invocation drift, especially with computed target IDs.\n- Tool declarations, because agents build tools dynamically by factory.\n- Model config, because runtime LLM calls use environment variables.\n- External resource triggers, because routing lives in external platforms.\n\nRelated References\n\n- /knowledge read knowledge.platform-composition-patterns\n- /knowledge read knowledge.platform-integration-patterns\n- /knowledge read knowledge.platform-capabilities"
+  },
+  {
+    id: "knowledge.platform-composition-patterns",
+    title: "Platform Composition Patterns",
+    summary: "Reference for composing agents, workflows, integrations, tools, observability, scaling, error handling, and security into complete Elevasis automation systems.",
+    bodyText: "Overview\n\nUse this reference to choose how Elevasis resources compose into complete systems. The core decision is whether reasoning, deterministic orchestration, or a hybrid of both should own the business flow.\n\nThree primary patterns exist:\n\n- Agent-centric: an agent is the primary orchestrator, and workflows or integrations are tools.\n- Workflow-centric: a workflow is the deterministic pipeline, and agents appear only as processing steps.\n- Hybrid: agents decide what should happen, and workflows execute reliable sequences.\n\nSystem Architecture Patterns\n\nAgent-Centric Systems\n\nPattern: Agent is the primary orchestrator; workflows and integrations are tools.\n\ntext\nTrigger to Agent\n           |- Tool: Integration A\n           |- Tool: Integration B\n           |- Tool: Workflow 1 via resource invocation\n           - Tool: Workflow 2 via resource invocation\n\nUse this pattern for ambiguous goals, dynamic decision-making, multi-turn conversations, and business logic that requires judgment.\n\nStrengths:\n\n- Flexible and adaptive.\n- Handles ambiguity well.\n- Can delegate to specialist resources.\n- Supports natural language interaction.\n\nWeaknesses:\n\n- Token cost per execution.\n- Non-deterministic LLM variance.\n- Requires strong observability for debugging.\n- Usually slower than deterministic workflows.\n\nWorkflow-Centric Systems\n\nPattern: Workflow is the pipeline; agents are processing steps.\n\ntext\nTrigger to Workflow\n           |- Step 1: Integration A reads data\n           |- Step 2: Agent processes or reasons\n           |- Step 3: Integration B writes result\n           - Step 4: Conditional routing\n\nUse this pattern for predictable sequences, data transformation pipelines, integration orchestration, and fixed business logic.\n\nStrengths:\n\n- Deterministic and reliable.\n- Fast execution.\n- Easy to debug step-by-step.\n- No token cost unless an agent step is included.\n\nWeaknesses:\n\n- Rigid, because steps are predefined.\n- Does not handle ambiguity well.\n- Requires code changes for logic updates.\n\nHybrid Systems\n\nPattern: Agents decide, workflows execute. This is the recommended default for complex automation.\n\ntext\nTrigger to Agent decides what to do\n           |- Invokes: Workflow A\n           |- Invokes: Workflow B\n           - Uses: Integration C directly\n\nWorkflow A:\n  |- Integration D reads\n  |- Agent processes a specific subtask\n  - Integration E writes\n\nUse this pattern when the system needs variable paths, reasoning, reliability, and a mix of predictable and unpredictable steps.\n\nStrengths:\n\n- Flexible where needed and reliable where possible.\n- Cost-efficient because workflows do not use tokens by default.\n- Good observability across agent reasoning and workflow steps.\n\nResource Composition Patterns\n\nAgent + Tools\n\nUse direct integration access for simple or frequent operations.\n\nTool categories:\n\n- Base tools: always available, high-frequency operations such as read queries or cached data access. Example: attiogetrecord.\n- Knowledge Map tools: lazy-loaded, low-frequency operations such as write operations or domain-specific capabilities. Examples: attiocreatecontact, dropboxuploadfile.\n- Resource invocation tools: delegate to workflows for deterministic sequences or call specialist agents.\n\nTool creation example:\n\ntypescript\nconst tool = createAttioCreateRecordTool('elevasis-attio')\n\nCredential names resolve to organization-scoped storage. RLS policies enforce organization isolation, credentials are encrypted at rest, and OAuth tokens can refresh automatically.\n\nAgent + Workflow\n\nUse an agent for reasoning and a workflow for deterministic execution.\n\ntext\nTrigger to Agent reasoning\n          |- Direct tool: read integration\n          |- Invoke tool: Workflow A\n          - Invoke tool: Workflow B\n\nExecution flow:\n\n1. Agent analyzes the request.\n2. Agent invokes a workflow through a tool call.\n3. Workflow executes deterministic steps without token cost.\n4. Agent explains the result to the user.\n\nUse this pattern when the system needs both reasoning and reliability, has multiple execution paths, or should minimize token use by moving predictable work into workflows.\n\nWorkflow + Integration\n\nUse a workflow to orchestrate deterministic integration sequences.\n\ntext\nTrigger to Workflow\n          |- Step 1: Integration A reads\n          |- Step 2: Transform pure function\n          |- Step 3: Integration B writes\n          - Step 4: Notify\n\nUse this pattern for predictable step sequences, data transformation pipelines, integration orchestration, and cost-sensitive work that does not need LLM reasoning.\n\nPattern Selection Guide\n\n| Requirement | Pattern | Example |\n| --- | --- | --- |\n| Ambiguous goals | Agent-centric | Business orchestration with variable outcomes |\n| Predictable sequence | Workflow-centric | Shopify to CRM sync |\n| Hybrid needs | Agent + workflow | Support router where agent decides and workflow executes |\n| \\>10 tools | Knowledge Map | Agent with many domain capabilities |\n| High-frequency reads | Base tools | Attio read operations |\n| Low-frequency writes | Lazy-loaded tools | CRM updates or page creation |\n| External services | Integration tools | Attio, Gmail, Google Sheets |\n| Deterministic pipelines | Workflow + integration | Data transformation |\n\nComplexity guidelines:\n\n- Simple, 1-2 resources: agent with base tools, or workflow with 1-2 integrations.\n- Medium, 3-5 resources: agent plus Knowledge Map with 2-3 nodes, or workflow plus an agent step.\n- Complex, 6+ resources: agent plus Knowledge Map plus memory preload, or multi-integration workflows.\n\nCross-Cutting Concerns\n\nObservability\n\nTrack these surfaces:\n\n- Agent iterations, including reasoning and actions.\n- Workflow steps, including inputs and outputs.\n- Tool calls, including integration requests and responses.\n- Errors and retries.\n- Token usage and cost.\n\nPrimary tools:\n\n- Execution Logs for SSE-based debugging.\n- Activity Log for the real-time stream.\n- Execution Health for cost tracking and ROI review.\n- Command View for system architecture and dependency review.\n\nCost Tracking\n\nAgent cost comes from per-iteration token usage, model pricing, and tool execution cost. Workflow cost is usually zero token cost plus any external integration API fees.\n\nOptimization rules:\n\n- Use workflows for predictable tasks.\n- Lazy-load tools for 80-95% token savings.\n- Cache frequently accessed stable data.\n- Choose the appropriate model per task.\n\nScaling Strategies\n\nHorizontal scaling:\n\n- Keep agent execution stateless.\n- Store sessions in the database.\n- Let a load balancer distribute requests.\n\nVertical optimization:\n\n- Preload memory to reduce iteration count.\n- Lazy-load tools to reduce token usage.\n- Batch tool operations where possible.\n- Use parallel integration calls when the steps are independent.\n\nError Handling\n\nAgent error handling:\n\n- Tool errors are returned to the agent so it can reason about recovery.\n- Iteration limits prevent infinite loops.\n- Timeout protection constrains long-running tools and executions.\n- Graceful degradation explains what failed.\n\nWorkflow error handling:\n\n- Step retry logic uses exponential backoff, commonly 1, 4, and 9 minutes.\n- Conditional routing can send failures to an alternative step.\n- Manual intervention can route work to a human checkpoint.\n- Idempotent steps should be safe to retry.\n\nExample:\n\ntypescript\n{\n  id: 'sync-to-crm',\n  handler: async ({ input, context }) => {\n    try {\n      return await crmClient.createContact(input)\n    } catch (error) {\n      if (error.code === 'DUPLICATE') {\n        return crmClient.updateContact(input)\n      }\n\n      throw error\n    }\n  },\n  next: { type: 'linear', target: 'send-notification' }\n}\n\nSecurity\n\nCredential management:\n\n- Store credentials in the credentials table.\n- Encrypt values at rest.\n- Scope records by organization with RLS policies.\n- Refresh OAuth tokens automatically where supported.\n- Never store API keys in code.\n\nMulti-tenancy isolation layers:\n\n1. Database RLS on tenant-scoped tables.\n2. API middleware that requires organization context.\n3. Resource registry lookups scoped to the organization.\n4. Command View filtered by organization.\n\nBest Practices\n\n1. Start with a single agent or workflow, then add complexity only when needed.\n2. Build the working version before optimizing for caching or lazy loading.\n3. Put domain logic in agents and execution flow in workflows.\n4. Lazy-load large or low-frequency tool groups.\n5. Cache stable data, not fast-changing operational state.\n\nCommon mistakes:\n\n- Creating a Knowledge Map for fewer than five tools.\n- Using a workflow for one integration call when an agent tool would be simpler.\n- Loading more than ten tools as base tools.\n- Putting domain logic into workflows where it becomes hard to test and adapt.\n- Mixing unrelated concerns in one knowledge node.\n\nRelated References\n\n- /knowledge read knowledge.platform-integration-patterns\n- /knowledge read knowledge.platform-command-view"
+  },
+  {
+    id: "knowledge.platform-integration-patterns",
+    title: "Platform Integration Patterns",
+    summary: "Reference for connecting Elevasis agents and workflows to external services through adapters, OAuth, API keys, tenant-isolated credentials, retries, and tests.",
+    bodyText: "Overview\n\nIntegration patterns define how Elevasis agents and workflows connect to external services such as Gmail, Attio, Google Sheets, and custom APIs. The platform uses a standardized adapter pattern with OAuth 2.0 and API key authentication backed by tenant-isolated credentials.\n\nCore patterns:\n\n- Direct integration, where a resource uses integration tools directly.\n- Integration workflow, where a workflow coordinates multiple integrations.\n- Shared integration, where multiple resources use the same credential set.\n- Multi-account integration, where the same provider has separate credentials for different contexts.\n\nDirect Integration Pattern\n\nPattern: Resource uses an integration tool.\n\nUse direct integration tools when an agent or workflow performs frequent operations against a provider.\n\nCharacteristics:\n\n- Tools are always available to the resource.\n- There is no additional navigation overhead.\n- The pattern is optimized for frequent read-heavy operations.\n\nTool factory location:\n\ntext\npackages/core/src/execution/engine/tools/integration/server/adapters/{provider}/{provider}-tools.ts\n\nTool factories use createIntegrationTool() with a credentialName parameter. Example: createAttioCreateRecordTool(credentialName).\n\nIntegration Workflow Pattern\n\nPattern: Agent invokes a workflow, and the workflow uses integrations.\n\nUse an integration workflow for complex multi-step operations that need deterministic orchestration.\n\nExample lead capture flow:\n\n1. Webhook trigger receives the event.\n2. Workflow creates an Attio contact.\n3. Workflow sends a Gmail notification.\n4. Workflow returns confirmation.\n\nCharacteristics:\n\n- Deterministic execution order.\n- Step-level error handling and retry.\n- Multiple integrations coordinated in one place.\n- Built-in audit trail through workflow execution.\n\nShared Integration Pattern\n\nPattern: Multiple resources share the same integration.\n\nUse shared integrations for organization-wide providers that should use one credential set.\n\nExample:\n\ntext\npackages/elevasis-operations/src/index.ts\n\nCharacteristics:\n\n- One credential per integration.\n- Centralized credential management.\n- Shared across agents and workflows.\n\nMulti-Account Pattern\n\nPattern: Same provider, different credentials.\n\nUse this pattern for department-specific provider instances or separate dev/prod environments.\n\nExample:\n\ntypescript\nconst salesTool = createAttioCreateRecordTool('attio-sales')\nconst supportTool = createAttioCreateRecordTool('attio-support')\n\nDisambiguate multi-account tools with explicit tool names:\n\ntypescript\nconst tool = createAttioToolNamed(\n  'attiosalescreaterecord',\n  'attio-sales',\n  'createRecord'\n)\n\nAuthentication Patterns\n\nOAuth 2.0 vs API Key\n\n| Aspect | OAuth 2.0 | API key |\n| --- | --- | --- |\n| Auth flow | Browser redirect plus token exchange | Direct API key |\n| Setup complexity | High: client ID, secret, redirect URL | Low: single API key |\n| Token refresh | Automatic refresh token rotation | Manual key rotation |\n| Scope control | Granular permission scopes | Full access or none |\n| User context | Per-user authorization | Service-level access |\n| Revocation | User can revoke anytime | Manual key deletion |\n\nOAuth 2.0 Pattern\n\nProviders include Gmail and Google Sheets.\n\nCredential format:\n\ntypescript\ninterface OAuthToken {\n  provider: string\n  accessToken: string\n  refreshToken: string\n  expiresAt: string\n  tokenType: 'Bearer'\n  scope?: string\n}\n\nexpiresAt is an ISO 8601 timestamp. The platform handles token refresh when supported by the provider and credential implementation.\n\nAPI Key Pattern\n\nProviders include Attio and custom APIs.\n\nCredential format:\n\ntypescript\ninterface APIKeyCredentials {\n  apiKey: string\n}\n\nProvider-specific validation belongs in the adapter. For Attio, see:\n\ntext\npackages/core/src/execution/engine/tools/integration/server/adapters/attio/attio-adapter.ts\n\nCredential Management\n\nCredentials are stored in the credentials table.\n\nKey columns:\n\n- organizationid for tenant isolation.\n- name, such as elevasis-attio.\n- provider, such as gmail or attio.\n- encryptedvalue containing encrypted JSON.\n\nSecurity rules:\n\n- RLS policies enforce tenant isolation.\n- Values are encrypted at rest.\n- Credentials do not cross organization boundaries.\n\nBest practices:\n\n- Store credentials encrypted in the database.\n- Use tenant-isolated credential names.\n- Validate credentials before API calls.\n- Rotate API keys regularly.\n- Use least-privilege OAuth scopes.\n\nDo not:\n\n- Hardcode credentials in code.\n- Share credentials across organizations.\n- Log credential values.\n- Store provider API keys in environment variables for tenant integrations.\n- Reuse the same credential name for dev and prod.\n\nCredential resolution flow:\n\n1. Tool requests a credential by name.\n2. Platform queries credentials with the current organizationid.\n3. Platform decrypts the credential.\n4. Adapter validates the credential against the provider schema.\n5. Tool passes the credential to the provider adapter.\n6. Usage is logged without credential values.\n\nImplementation reference:\n\ntext\npackages/core/src/execution/engine/tools/integration/tool.ts\n\nError Handling Patterns\n\nAdapters should convert provider errors into platform tooling errors.\n\nCommon error categories:\n\n- credentialsinvalid for invalid or missing credentials.\n- apierror for provider API errors.\n- networkerror for network or timeout failures.\n- validationerror for invalid parameters.\n- methodnotfound for unknown adapter methods.\n\nRetry strategy:\n\n- Network errors: retry with exponential backoff, commonly 1, 2, and 4 seconds.\n- Auth errors: fail immediately because the credential needs attention.\n- Validation errors: fail immediately because the input needs correction.\n- Rate limits: retry after reset when the provider exposes a reset time.\n- Workflow-level retries: commonly 3 attempts with 1, 4, and 9 minute delays.\n\nAdapter Development\n\nAdapter class location:\n\ntext\npackages/core/src/execution/engine/tools/integration/server/adapters/{provider}/{provider}-adapter.ts\n\nAdapter classes implement BaseIntegrationAdapter and contain call() and validateCredentials() methods.\n\nTool factory location:\n\ntext\npackages/core/src/execution/engine/tools/integration/server/adapters/{provider}/{provider}-tools.ts\n\nTool factories export create{Provider}{Operation}Tool(credentialName) functions.\n\nTests belong under:\n\ntext\npackages/core/src/execution/engine/tools/integration/server/adapters/{provider}/tests/\n\nRegistration happens in:\n\ntext\npackages/core/src/execution/engine/tools/integration/server/index.ts\n\nTesting Strategies\n\nUnit testing:\n\n- Mock external APIs.\n- Cover credential validation.\n- Cover API call construction.\n- Cover response parsing.\n- Cover error handling.\n\nIntegration testing:\n\n- Use real API calls only with test accounts or test workspaces.\n- Clean up test data after tests.\n- Run in CI only when secret credentials are available.\n- Keep provider behavior mocked in unit tests.\n\nAgent testing:\n\n- Test agents using integration tools at the resource boundary.\n- Tenant project agent tests normally live under external/{org}/src/agents/{agent}/tests/.\n\nRelated References\n\n- /knowledge read knowledge.platform-composition-patterns\n- /knowledge read knowledge.platform-command-view\n- /knowledge read knowledge.platform-capabilities"
+  },
+  {
+    id: "knowledge.what-is-elevasis",
+    title: "What is Elevasis",
+    summary: "Company overview, positioning, value proposition, and pricing for the AI orchestration platform",
+    bodyText: 'Executive Summary\n\nCompany: Bootstrapped AI orchestration platform for done-for-you business automation\n\nFounder: Solo (Alex, 34), bootstrapped\n\nMarket: Service-based SMBs that need practical AI automation without building internal AI teams\n\nGTM: Content-led marketing, proof assets, consultative sales, and land-and-expand pricing\n\nCompany Overview\n\nCurrent Status\n\nThe platform core is production-ready enough to support client-facing demonstrations and implementation work. Current business focus is client acquisition, proof-building, and turning the platform into a repeatable service delivery system.\n\nFounder Profile\n\nAlex, 34 \u2014 Solo founder with software engineering background (BSCS degree). Previous: Ecommerce platforms, Streaming technology. No formal AI background \u2014 practitioner, not academic.\n\nWhat We Are\n\nOperating layer for AI automation. We help SMBs operate with closed-loop feedback, decision capture, and continuous learning \u2014 at SMB pricing with done-for-you implementation (NOT self-service).\n\nTarget Market\n\nICP: Service-based SMBs (2-50 employees, USA, $200K-$5M revenue)\n\nCore Pain: Capacity crisis, pipeline problems, operational chaos, growth blockers \u2014 too busy serving clients to grow their own business.\n\nPricing (Land-and-Expand)\n\n- Tier 1 \u2014 Foundation (1-2 workflows): $500-2k/mo\n- Tier 2 \u2014 Scaled Operations (3-5 workflows): $2k-5k/mo\n- Tier 3 \u2014 AI-Powered Systems (6+ workflows): $5k-15k+/mo\n\nAdditional workflows cost less due to shared infrastructure.\n\nValue Proposition\n\n"We find one bottleneck in your business, build an AI solution to fix it, and you only pay if it actually saves you time or makes you money."'
+  },
+  {
+    id: "knowledge.platform-capabilities",
+    title: "Platform Capabilities",
+    summary: "Authoritative overview of the Elevasis AI Orchestration Platform \u2014 what's built, what it does, and how the pieces fit together",
+    bodyText: "Overview\n\nElevasis is a production AI orchestration platform that coordinates workflows, autonomous agents, and human approvals into a unified operating layer for SMBs. Everything described below is implemented and running in production.\n\nCore Architecture:\n\n| Layer | What It Does | Key Components |\n| --- | --- | --- |\n| Execution | Runs workflows and agents with schema validation | Workflow Engine, Agent Framework, Execution Runner |\n| Control | Human oversight, approvals, and decision capture | Command Queue (HITL), Dynamic Forms, Action System |\n| Intelligence | Autonomous reasoning, tool use, and memory management | ReAct Agents, Knowledge Map, Session Memory |\n| Observability | Real-time visibility into cost, performance, and health | Cost Tracking, Metrics, Activity Log, SSE Streaming |\n| Platform | Multi-tenancy, security, scheduling, integrations | Registry, RLS, Scheduler, Credential Vault, SDK |\n\nExecution Engine\n\nAI Workflows\n\nGraph-based workflow execution with schema-validated steps and conditional routing. Steps define explicit routing: linear, conditional (rule-based branching), or terminal. Context flows through the entire workflow.\n\nAutonomous Agents\n\nProduction-grade ReAct-style agents with tool use, memory management, and security hardening.\n\nLLM Provider Support: OpenAI (GPT-5), Google (Gemini 3 Flash), Anthropic (Claude Sonnet 4.5), OpenRouter (GLM-5)\n\nHuman-in-the-Loop (HITL)\n\nThe Command Queue surfaces pending approvals as structured tasks. Admin reviews, approves or edits, and the workflow continues. Every critical decision \u2014 sending emails to prospects, updating customer records, publishing content \u2014 requires human approval.\n\nKnowledge Map\n\nOrganizational knowledge loaded lazily into agent context. 80-95% token savings vs. always-loading full context. Nodes link to features, teams, and other nodes.\n\nIntegrations (13 active)\n\nAttio CRM, Cal.com, Instantly (cold email), Resend, Apify, Google Maps, Tomba, Mails.so, Supabase, Stripe, OpenAI, Google Gemini, Anthropic Claude.\n\nSDK\n\nTypeScript-based resource development with local testing, validation, and deployment pipeline. External consumers define workflows and agents in their own repos and deploy via elevasis-sdk deploy."
+  },
+  {
+    id: "knowledge.client-testimonials",
+    title: "Testimonials",
+    summary: "Customer testimonials and case study permissions from previous client work",
+    bodyText: `Status: 4 testimonials from 2 clients | Source: Upwork client work (2024)
+
+Testimonials
+
+Xero Automation \u2014 The Invoice Chase That Disappeared
+
+Client: Word of Mouth Agency
+
+Result: 10+ hours/week saved. Zero manual follow-up emails.
+
+> "Working with Alex at Elevasis to automate our Xero follow-ups has been a game-changer. We're set to save over 5 hours a week, but more importantly, it has completely removed the stress of chasing invoices. The process was smooth and professional."
+
+Permission: Case study approved with company name.
+
+Influencer Discovery \u2014 From Spreadsheet Hell to Strategic Decisions
+
+Client: Word of Mouth Agency (Perth, Australia)
+
+Result: 10+ hours/week saved. Research scope: 50 to 200+ influencers. Team focus shifted from data to strategy.
+
+> "Working with Alex at Elevasis to automate our Influencer Discovery has been a game-changer. We're set to save over 5 hours a week..."
+
+Permission: Case study approved with company name.
+
+EMRG Media \u2014 4 Automations for NYC's Premier Events Firm
+
+Client: EMRG Media (NYC, est. 2001). Clients include Google, YouTube, Sony Music, Fiverr, Equinox.
+
+What We Built:
+1. Case Study Generator \u2014 7-10 hours \u2192 2 hours. Publication rate: 1/quarter \u2192 2/month.
+2. EMRG Follow-Up Generator \u2014 Automated post-event follow-ups with signature management.
+3. Event Sponsor Tracker \u2014 Automated sponsor pipeline tracking and communications.
+4. Lead Scraper \u2014 Automated discovery of event planning prospects.
+
+Fame Stats:
+- 3,500+ attendees at The Event Planner Expo
+- 25+ year track record
+- Fortune 500 client roster
+
+Permission: Case study approved with company name.`
+  },
+  {
+    id: "knowledge.understanding-elevasis",
+    title: "Understanding Elevasis Overview",
+    summary: "Company overview, product positioning, and platform capability context for Elevasis AI orchestration platform",
+    bodyText: "Lean documentation explaining what Elevasis is and what the platform can do. This section provides the foundational context for business conversations and technical evaluation.\n\nElevasis is a done-for-you AI automation service backed by a production-grade platform. The company targets service-based SMBs (2-50 employees, $200K-$5M revenue) who are too busy serving clients to grow their own business.\n\nKey Facts\n\n- Stage: Pre-revenue, platform 100% complete, client acquisition active\n- Offer: Done-for-you AI automation -- we build and maintain the workflows, no coding required\n- ICP: Service-based SMBs (2-50 employees, $200K-$5M revenue, USA)\n- Pricing: $500-$2k/mo (Foundation) \u2192 $2k-$5k/mo (Scaled) \u2192 $5k-$15k+/mo (AI-Powered)\n- Market: Early Adopters stage, $23.77B TAM growing to $87.7B by 2032\n- Competitive position: No dominant done-for-you SMB AI provider exists; blue ocean\n\nWhen to Use Each Document\n\n| Situation | Document |\n| --- | --- |\n| First conversation with any audience | What is Elevasis |\n| Technical evaluation or demo prep | Platform Capabilities |\n\nDocumentation\n\n- What is Elevasis \u2014 AI orchestration platform overview, company stage, value proposition, and pricing tiers\n- Platform Capabilities \u2014 Authoritative overview of what is built, what it does, and how the pieces fit together"
+  },
+  {
+    id: "knowledge.marketing-overview",
+    title: "Marketing Overview",
+    summary: "Marketing documentation for Elevasis - strategy, website infrastructure, and content systems",
+    bodyText: "Welcome to the Elevasis marketing documentation. This section covers marketing strategy, website implementation, and content systems.\n\nDocumentation\n\nStrategy\n\n- Overview \u2014 Channel strategy, inbound content system, and proof-led demand generation\n\nWebsite\n\nThe marketing website's technical infrastructure, setup, and SEO docs now live under Architecture \u2192 Website."
+  },
+  {
+    id: "knowledge.ai-orchestration-principles",
+    title: "AI Orchestration Principles",
+    summary: "The 4 principles that separate production AI from toy automation",
+    bodyText: `Most AI automation fails. Not because the technology is bad, but because it's implemented without the principles that make AI systems work in production.
+
+These four principles separate toy automation from AI systems that actually run businesses.
+
+The 4 Principles
+
+1. Integrated: Works With Your Existing Systems
+
+Principle: AI must work with your existing tools, not replace them.
+
+AI that doesn't connect to your CRM, your email, your calendar, your existing workflows is a toy. Real AI automation works WITH what you already have \u2014 not instead of it.
+
+- Your 50 Zapier workflows keep running
+- Your CRM stays your CRM
+- AI adds intelligence on top, not a rip-and-replace
+
+The anti-pattern: "Use our AI instead of everything else." Creates vendor lock-in and throws away your existing investment.
+
+2. Improving: Gets Smarter Over Time
+
+Principle: AI must learn from every decision and improve continuously.
+
+Static automation is just fancy if-then logic. Real AI captures every approval, rejection, and edit \u2014 then uses that data to get smarter.
+
+The anti-pattern: "Set it and forget it." Systems that don't learn stay dumb forever.
+
+3. Observable: You See What AI Is Doing
+
+Principle: You must be able to see what AI systems are doing in real-time.
+
+Black-box automation is unacceptable for business operations. You need to see every action, every decision, every cost \u2014 as it happens.
+
+- Real-time activity feeds showing what's executing
+- Cost tracking per workflow, per execution
+- Token usage visibility
+- Execution logs for debugging
+
+The anti-pattern: "It just works, trust us." Systems without observability create anxiety and prevent adoption.
+
+4. Governed: Humans Control What Matters
+
+Principle: Humans must approve important actions before execution.
+
+AI should handle the grunt work. But critical decisions \u2014 sending emails to prospects, updating customer records, publishing content \u2014 require human approval.
+
+- AI researches 50 prospects and drafts personalized emails
+- Before anything sends, it lands in your approval queue
+- You spend 10 minutes reviewing, approve or tweak
+- Only then does it execute
+
+The anti-pattern: "Fully autonomous AI." Systems without governance create risk and erode trust.`
+  }
+];
+function buildSearchIndex(entries) {
+  return {
+    search(query) {
+      if (!query.trim()) return [];
+      const q = query.trim().toLowerCase();
+      const scored = [];
+      for (const entry of entries) {
+        let score = 0;
+        if (entry.title.toLowerCase().includes(q)) score += 3;
+        if (entry.summary.toLowerCase().includes(q)) score += 2;
+        if (entry.bodyText.toLowerCase().includes(q)) score += 1;
+        if (score > 0) scored.push({ id: entry.id, score });
+      }
+      return scored.sort((a, b) => b.score - a.score).map((s) => s.id);
+    }
+  };
+}
+function KnowledgeSearchBar({
+  knowledgeNodes,
+  onResults,
+  placeholder = "Search knowledge\u2026"
+}) {
+  const [query, setQuery] = useState("");
+  const indexRef = useRef(null);
+  useEffect(() => {
+    indexRef.current = buildSearchIndex(knowledge_search_index_default);
+  }, []);
+  const nodeMapRef = useRef(/* @__PURE__ */ new Map());
+  useEffect(() => {
+    const map = /* @__PURE__ */ new Map();
+    for (const node of knowledgeNodes) map.set(node.id, node);
+    nodeMapRef.current = map;
+  }, [knowledgeNodes]);
+  const handleChange = (value) => {
+    setQuery(value);
+    if (!value.trim()) {
+      onResults(null);
+      return;
+    }
+    const ids = indexRef.current?.search(value) ?? [];
+    const hits = ids.flatMap((id) => {
+      const node = nodeMapRef.current.get(id);
+      return node ? [node] : [];
+    });
+    onResults(hits);
+  };
+  const handleClear = () => {
+    setQuery("");
+    onResults(null);
+  };
+  return /* @__PURE__ */ jsx(
+    TextInput,
+    {
+      value: query,
+      onChange: (e) => handleChange(e.currentTarget.value),
+      placeholder,
+      leftSection: /* @__PURE__ */ jsx(IconSearch, { size: 16 }),
+      rightSection: query ? /* @__PURE__ */ jsx(IconX, { size: 14, style: { cursor: "pointer", color: "var(--color-text-subtle)" }, onClick: handleClear }) : null,
+      styles: {
+        input: {
+          backgroundColor: "var(--color-surface)",
+          borderColor: "var(--color-border)",
+          color: "var(--color-text)"
+        }
+      }
+    }
+  );
+}
+
+export { EdgeRelationshipGroup, KNOWLEDGE_ICON_TOKEN_BY_KIND, KeyField, KindChip, KnowledgeSearchBar, KnowledgeTree, NodeDescribeShell, NodeHeader, NodeMetadataFooter, RelatedKnowledgeSection, byKind, getKnowledgeIconToken };