@synap-core/workspace-templates 0.7.3 → 0.7.4

package/dist/index.js

@@ -9714,6 +9714,22 @@ var DATA = {
               "inactive"
             ]
           },
+          {
+            "slug": "commercialStage",
+            "label": "Commercial stage",
+            "valueType": "string",
+            "inputType": "select",
+            "enumValues": [
+              "draft",
+              "proposed",
+              "negotiating",
+              "won",
+              "lost"
+            ],
+            "constraints": {
+              "defaultValue": "draft"
+            }
+          },
           {
             "slug": "valueType",
             "label": "Value type",
@@ -12560,6 +12576,12 @@ var DATA = {
         "relation": "require",
         "reason": "The pipeline \u2014 contacts, leads, clients, and deals."
       },
+      {
+        "slug": "business-developer",
+        "kind": "workspace",
+        "relation": "require",
+        "reason": "The lead-first sales motion (crm-lead/crm-client roles, commercial proposals, commission handoff) that the CRM app runs on. Composes onto the CRM workspace above \u2014 without it the CRM lens is provisioned with pod-wide lead/client only and the app's pipeline is empty."
+      },
       {
         "slug": "content-os",
         "kind": "workspace",
@@ -22504,7 +22526,7 @@ var DATA = {
       {
         "key": "operations-daily-client-briefing",
         "name": "Daily client briefing",
-        "description": "Each morning, for every client, distil their recent comms into one batched digest, save it as a durable client-briefing, and post the recap to the client's internal TEAM channel (never the client-facing channel).",
+        "description": "Operations-native daily client briefing. Writes a durable, dated client-briefing ENTITY per client (queryable history, linked to the client) from their recent comms, and posts the recap to the client's internal TEAM channel (never the client-facing channel). Knowledge-building and entity-first \u2014 the delivery OS's structured memory of each client. For a lighter, portable message-only digest installable on any pod, use the client-comms-report capability.",
         "triggerType": "cron",
         "triggerConfig": {
           "expression": "0 8 * * *"
@@ -27002,6 +27024,11 @@ counter-evidence: research that only kept what agreed with it isn't research.
         }
       }
     ],
+    "integrations": [
+      {
+        "templateKey": "client-comms-report"
+      }
+    ],
     "onboarding": {
       "goal": "Name the cross-workspace initiatives that span the operating system and its private flagships \u2014 the few big things in flight that touch more than one lens \u2014 so The Arch is a real command layer, not just an aggregate of apps.\n",
       "framing": "THE FOUNDER'S COMMAND LAYER: Act from the seat above every lens. The whole\ncompany brain is installed \u2014 operating core plus the private grant, web3, and\ndev flagships. Your job is to surface the handful of initiatives that cut\nacross them and give each a stage, a lead, and a priority.\n",