@synap-core/workspace-templates 0.7.3 → 0.7.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@synap-core/workspace-templates",
-  "version": "0.7.3",
+  "version": "0.7.4",
   "type": "module",
   "packageManager": "pnpm@9.15.4",
   "description": "Canonical workspace definitions — YAML source + typed exports for browser, backend, CLI, and marketplace",

package/src/crm.yaml

@@ -178,6 +178,17 @@ profiles:
           - won
           - lost
           - inactive
+      - slug: commercialStage
+        label: Commercial stage
+        valueType: string
+        inputType: select
+        enumValues:
+          - draft
+          - proposed
+          - negotiating
+          - won
+          - lost
+        constraints: { defaultValue: draft }
       - slug: valueType
         label: Value type
         valueType: string

package/src/enterprise-os.yaml

@@ -48,6 +48,10 @@ dependencies:
     kind: workspace
     relation: require
     reason: "The pipeline — 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 — 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
     relation: require

package/src/operations.yaml

@@ -355,9 +355,13 @@ automations:
   - 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).
+      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 — 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 * * *"

package/src/templates.ts

@@ -9699,6 +9699,22 @@ const 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",
@@ -12543,6 +12559,12 @@ const DATA = {
         "relation": "require",
         "reason": "The pipeline — 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 — 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",
@@ -22466,7 +22488,7 @@ const 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 — 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 * * *"
@@ -26944,6 +26966,11 @@ const DATA = {
         }
       }
     ],
+    "integrations": [
+      {
+        "templateKey": "client-comms-report"
+      }
+    ],
     "onboarding": {
       "goal": "Name the cross-workspace initiatives that span the operating system and its private flagships — the few big things in flight that touch more than one lens — 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 — 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",

package/src/the-arch.yaml

@@ -109,6 +109,16 @@ views:
     config:
       groupBy: stage
 
+# The Arch now OWNS the per-client comms digest capability. `client-comms-report`
+# is the one capability no constituent template installs today — the portable,
+# message-only client digest that any pod can run. The Arch, as the full company
+# brain, is where it belongs: it rides in alongside the operations-native durable
+# briefing so the founder has BOTH the entity-first record and the lightweight
+# recap. (discord-bot / agency-skills / stellar-grant-client already ride in via
+# the `grants` constituent's own integrations, so they are not re-declared here.)
+integrations:
+  - templateKey: client-comms-report
+
 onboarding:
   goal: >
     Name the cross-workspace initiatives that span the operating system and its