@synap-core/workspace-templates 0.7.2 → 0.7.4

package/src/content-os.yaml

@@ -8,6 +8,7 @@
 
 meta:
   slug: content-os
+  domain: content
   name: Content OS
   description: "Your editorial operating system — pillars, posts, platforms, and newsletters. Turn raw thinking into a published content engine, all connected to your campaigns and brand voice."
   icon: pen-tool
@@ -71,17 +72,51 @@ profiles:
         label: Status
         valueType: string
         inputType: select
-        enumValues: ["Idea", "Briefed", "In Draft", "Review", "Scheduled", "Published", "Archived"]
+        enumValues:
+          [
+            "Idea",
+            "Briefed",
+            "In Draft",
+            "Review",
+            "Scheduled",
+            "Published",
+            "Archived",
+          ]
       - slug: post-format
         label: Format
         valueType: string
         inputType: select
-        enumValues: ["Article", "Thread", "Short Video", "Long Video", "Carousel", "Image Post", "Story", "Newsletter Section", "Podcast Episode", "Other"]
+        enumValues:
+          [
+            "Article",
+            "Thread",
+            "Short Video",
+            "Long Video",
+            "Carousel",
+            "Image Post",
+            "Story",
+            "Newsletter Section",
+            "Podcast Episode",
+            "Other",
+          ]
       - slug: post-platform
         label: Platform
         valueType: string
         inputType: select
-        enumValues: ["LinkedIn", "Instagram", "TikTok", "YouTube", "Twitter / X", "Threads", "Bluesky", "Newsletter", "Podcast", "Blog", "Other"]
+        enumValues:
+          [
+            "LinkedIn",
+            "Instagram",
+            "TikTok",
+            "YouTube",
+            "Twitter / X",
+            "Threads",
+            "Bluesky",
+            "Newsletter",
+            "Podcast",
+            "Blog",
+            "Other",
+          ]
       - slug: post-pillar
         label: Pillar
         valueType: entity_id
@@ -160,7 +195,16 @@ profiles:
         label: Primary Formats
         valueType: string
         inputType: select
-        enumValues: ["Articles + Threads", "Short Video", "Long Video", "Newsletter", "Podcast", "Carousel", "Mixed"]
+        enumValues:
+          [
+            "Articles + Threads",
+            "Short Video",
+            "Long Video",
+            "Newsletter",
+            "Podcast",
+            "Carousel",
+            "Mixed",
+          ]
       - slug: post-count-pillar
         label: Total Posts Published
         valueType: number
@@ -178,23 +222,61 @@ profiles:
         label: Target Frequency
         valueType: string
         inputType: select
-        enumValues: ["Daily", "3x / week", "2x / week", "Weekly", "Bi-weekly", "Monthly", "Ad hoc"]
+        enumValues:
+          [
+            "Daily",
+            "3x / week",
+            "2x / week",
+            "Weekly",
+            "Bi-weekly",
+            "Monthly",
+            "Ad hoc",
+          ]
       - slug: pillar-tags
         label: Tags
         valueType: array
 
+  # `platform` is the ONE pod-wide publishing-account *vocabulary*. `scope: shared`
+  # makes it a single pod-wide profile row that a `require`-consumer (e.g.
+  # social.yaml) can adopt by RE-DECLARING this slug — the resolver writes the
+  # grant on declare, giving that workspace the same vocabulary instead of forking
+  # its own `channel` kind. (This shares the profile DEFINITION, not the account
+  # entities — `platform` has no `entityScope: pod`, so each workspace's platform
+  # rows stay its own.) This is the deterministic form of the campaign reuse
+  # pattern (there, a workspace kind is promoted to shared at apply; here the
+  # SSOT is shared from the start). The re-declared body in social must not
+  # conflict with this one — guarded locally by the shared-role SSOT check, not a
+  # CI gate.
   - slug: platform
     displayName: Platform
     icon: share-2
     color: "#06B6D4"
     description: "A social account, newsletter publication, or podcast channel. Each platform has its own audience metrics and publishing rhythm."
-    scope: WORKSPACE
+    scope: shared
     properties:
       - slug: platform-type
         label: Type
         valueType: string
         inputType: select
-        enumValues: ["LinkedIn", "Instagram", "TikTok", "YouTube", "Twitter / X", "Threads", "Bluesky", "Newsletter", "Podcast", "Blog / Website", "Other"]
+        enumValues:
+          [
+            "LinkedIn",
+            "Instagram",
+            "TikTok",
+            "YouTube",
+            "Twitter / X",
+            "Threads",
+            "Bluesky",
+            "Newsletter",
+            "Podcast",
+            "Blog / Website",
+            "Other",
+          ]
+      - slug: handle
+        label: Handle
+        valueType: string
+        inputType: text
+        placeholder: "@username"
       - slug: platform-status
         label: Status
         valueType: string
@@ -222,7 +304,16 @@ profiles:
         label: Posting Frequency
         valueType: string
         inputType: select
-        enumValues: ["Daily", "3x / week", "2x / week", "Weekly", "Bi-weekly", "Monthly", "As Needed"]
+        enumValues:
+          [
+            "Daily",
+            "3x / week",
+            "2x / week",
+            "Weekly",
+            "Bi-weekly",
+            "Monthly",
+            "As Needed",
+          ]
       - slug: last-post-date
         label: Last Post Date
         valueType: date
@@ -246,7 +337,8 @@ profiles:
         label: Status
         valueType: string
         inputType: select
-        enumValues: ["Idea", "Drafting", "Editing", "Scheduled", "Sent", "Archived"]
+        enumValues:
+          ["Idea", "Drafting", "Editing", "Scheduled", "Sent", "Archived"]
       - slug: newsletter-series
         label: Series
         valueType: string
@@ -327,7 +419,8 @@ profiles:
         label: Channel
         valueType: string
         inputType: select
-        enumValues: [email, social, event, content, partnership, paid, organic, other]
+        enumValues:
+          [email, social, event, content, partnership, paid, organic, other]
       - slug: campaign-goal
         label: Goal
         valueType: string

package/src/content-studio.yaml

@@ -3,6 +3,7 @@
 
 meta:
   slug: content-studio
+  domain: content
   name: Content Studio
   description: HyperFrames + Remotion video pipeline — script, design, compose, render, publish.
   icon: clapperboard

package/src/crm.yaml

@@ -6,6 +6,7 @@
 
 meta:
   slug: crm
+  domain: revenue
   name: CRM
   description: Sales pipeline and contact management from first contact to handoff.
   icon: handshake
@@ -177,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/define.ts

@@ -404,6 +404,7 @@ export interface PackageDefinitionOutput {
     slug: string;
     icon?: string;
     color?: string;
+    domain?: string;
     tags?: string[];
     isPublic?: boolean;
     requiredTier?: string | null;
@@ -442,13 +443,11 @@ export interface PackageDefinitionOutput {
   automations?: PackageAutomationWire[];
   /**
    * Entity-detail action placements — carried verbatim (authored form IS the
-   * wire form). NOTE: the Hub `PackageApplySchema` (synap-backend
-   * `hub-protocol/rest/packages.ts`) is a plain `z.object` and does not yet
-   * declare `actionPlacements`, so on the CLI/Hub install path this field is
-   * STRIPPED before `applyPackagePostWorkspace` sees it. The tRPC
-   * `createFromDefinition` door DOES carry it. Named follow-up: add an
-   * `ActionPlacementSchema` field to `PackageApplySchema` to close the Hub half
-   * (out of the T2 fence — flagged in the handoff).
+   * wire form). The Hub `PackageApplySchema` (synap-backend
+   * `hub-protocol/rest/packages.ts`) now declares `actionPlacements`
+   * (`z.array(ActionPlacementSchema).optional()`), so BOTH the tRPC
+   * `createFromDefinition` door and the CLI/Hub install path carry it through to
+   * `applyPackagePostWorkspace` — the parity is closed.
    */
   actionPlacements?: WorkspaceYaml['actionPlacements'];
   onboarding?: WorkspaceYaml['onboarding'];
@@ -481,6 +480,7 @@ export function toPackageDefinition(
       slug: tpl.meta.slug,
       icon: tpl.meta.icon,
       color: tpl.meta.color,
+      domain: tpl.meta.domain,
       tags: tpl.meta.tags,
       isPublic: tpl.meta.isPublic ?? true,
     },
@@ -535,7 +535,7 @@ type PackageDefinitionForwarded =
   | 'integrations'  // → capabilities
   | 'playbooks'
   | 'automations'   // → mapped to the apply door's flowDefinition wire shape
-  | 'actionPlacements' // → carried verbatim (Hub inbound schema decl is a follow-up)
+  | 'actionPlacements' // → carried verbatim (Hub inbound schema declares it — parity closed)
   | 'onboarding'
   | 'dependencies';
 

package/src/dev-dashboard.yaml

@@ -7,6 +7,7 @@
 
 meta:
   slug: dev-dashboard
+  domain: build
   name: "Synap Dev — Infrastructure Command Center"
   description: "Internal DevOps dashboard for monitoring Synap infrastructure. Tracks services, vendors, and environments with health status, architecture flow map, and quick access to admin panels."
   icon: server
@@ -123,7 +124,8 @@ profiles:
         label: Vendor Type
         valueType: string
         inputType: select
-        enumValues: [Hosting, AI, Auth, Database, Monitoring, CI/CD, DNS, Email, Other]
+        enumValues:
+          [Hosting, AI, Auth, Database, Monitoring, CI/CD, DNS, Email, Other]
       - slug: vendor-url
         label: Vendor URL
         valueType: string
@@ -271,7 +273,8 @@ profiles:
         label: Type
         valueType: string
         inputType: select
-        enumValues: [api_key, ssh_key, password, token, certificate, env_variable, other]
+        enumValues:
+          [api_key, ssh_key, password, token, certificate, env_variable, other]
         placeholder: "Select credential type"
       - slug: service-name
         label: Service
@@ -418,7 +421,14 @@ views:
     type: table
     scopeProfileSlug: service
     config:
-      visibleColumns: [service-type, environment, deployment-branch, last-deploy, health-status]
+      visibleColumns:
+        [
+          service-type,
+          environment,
+          deployment-branch,
+          last-deploy,
+          health-status,
+        ]
       sortBy: last-deploy
       sortDirection: desc
 
@@ -854,12 +864,36 @@ bento:
       config:
         title: Quick Links
         links:
-          - { label: GitHub, url: "https://github.com/synapsh", color: "#24292E" }
-          - { label: Hetzner Console, url: "https://console.hetzner.cloud", color: "#D50C2D" }
-          - { label: Vercel Dashboard, url: "https://vercel.com/dashboard", color: "#000000" }
-          - { label: Ory Console, url: "https://console.ory.sh", color: "#5528FF" }
-          - { label: Cloudflare, url: "https://dash.cloudflare.com", color: "#F38020" }
-          - { label: OpenRouter, url: "https://openrouter.ai/dashboard", color: "#6366F1" }
+          - {
+              label: GitHub,
+              url: "https://github.com/synapsh",
+              color: "#24292E",
+            }
+          - {
+              label: Hetzner Console,
+              url: "https://console.hetzner.cloud",
+              color: "#D50C2D",
+            }
+          - {
+              label: Vercel Dashboard,
+              url: "https://vercel.com/dashboard",
+              color: "#000000",
+            }
+          - {
+              label: Ory Console,
+              url: "https://console.ory.sh",
+              color: "#5528FF",
+            }
+          - {
+              label: Cloudflare,
+              url: "https://dash.cloudflare.com",
+              color: "#F38020",
+            }
+          - {
+              label: OpenRouter,
+              url: "https://openrouter.ai/dashboard",
+              color: "#6366F1",
+            }
     - kind: widget
       widgetType: entity-list
       pos: { x: 0, y: 7, w: 6, h: 5 }

package/src/domains.test.ts

@@ -0,0 +1,117 @@
+/**
+ * Unit tests for the domain taxonomy — the "works for any template" contract.
+ * Run: `npx vitest run packages/workspace-templates` (from the repo root).
+ */
+
+import { describe, expect, it } from "vitest";
+import {
+  groupByDomain,
+  domainLabel,
+  TEMPLATE_DOMAINS,
+  OTHER_DOMAIN_ID,
+  isKnownDomain,
+} from "./domains.js";
+
+type Row = { slug: string; domain?: string };
+const domainOf = (r: Row) => r.domain;
+
+describe("domainLabel", () => {
+  it("returns the registry label for a known domain", () => {
+    expect(domainLabel("revenue")).toBe("Sales & Marketing");
+  });
+  it("returns 'More' for a missing domain", () => {
+    expect(domainLabel(undefined)).toBe("More");
+    expect(domainLabel(null)).toBe("More");
+    expect(domainLabel("")).toBe("More");
+  });
+  it("title-cases an unknown-but-declared domain so it still reads", () => {
+    expect(domainLabel("supply-chain")).toBe("Supply Chain");
+    expect(domainLabel("bizops")).toBe("Bizops");
+  });
+});
+
+describe("groupByDomain — works for ANY template", () => {
+  it("orders known domains by the registry, never alphabetically", () => {
+    const rows: Row[] = [
+      { slug: "a", domain: "knowledge" }, // registry order 5
+      { slug: "b", domain: "strategy" }, // registry order 0
+      { slug: "c", domain: "content" }, // registry order 2
+    ];
+    const groups = groupByDomain(rows, domainOf);
+    expect(groups.map((g) => g.id)).toEqual(["strategy", "content", "knowledge"]);
+  });
+
+  it("preserves input order WITHIN a section", () => {
+    const rows: Row[] = [
+      { slug: "z", domain: "content" },
+      { slug: "a", domain: "content" },
+    ];
+    const [content] = groupByDomain(rows, domainOf);
+    expect(content.items.map((r) => r.slug)).toEqual(["z", "a"]);
+  });
+
+  it("places an unknown-but-declared domain AFTER all known ones", () => {
+    const rows: Row[] = [
+      { slug: "x", domain: "supply-chain" }, // unknown
+      { slug: "y", domain: "build" }, // known
+    ];
+    const groups = groupByDomain(rows, domainOf);
+    expect(groups.map((g) => g.id)).toEqual(["build", "supply-chain"]);
+    expect(groups[1].label).toBe("Supply Chain");
+  });
+
+  it("sorts multiple unknown domains alphabetically, before 'other'", () => {
+    const rows: Row[] = [
+      { slug: "1", domain: "zeta" },
+      { slug: "2" }, // missing → other
+      { slug: "3", domain: "alpha" },
+      { slug: "4", domain: "revenue" }, // known
+    ];
+    const groups = groupByDomain(rows, domainOf);
+    expect(groups.map((g) => g.id)).toEqual([
+      "revenue",
+      "alpha",
+      "zeta",
+      OTHER_DOMAIN_ID,
+    ]);
+  });
+
+  it("routes a MISSING domain into the 'More' bucket, always LAST", () => {
+    const rows: Row[] = [
+      { slug: "1" },
+      { slug: "2", domain: "strategy" },
+    ];
+    const groups = groupByDomain(rows, domainOf);
+    expect(groups[groups.length - 1].id).toBe(OTHER_DOMAIN_ID);
+    expect(groups[groups.length - 1].label).toBe("More");
+  });
+
+  it("NEVER drops an item — count in equals count out", () => {
+    const rows: Row[] = [
+      { slug: "1", domain: "build" },
+      { slug: "2", domain: "made-up" },
+      { slug: "3" },
+      { slug: "4", domain: "build" },
+    ];
+    const total = groupByDomain(rows, domainOf).reduce(
+      (n, g) => n + g.items.length,
+      0
+    );
+    expect(total).toBe(rows.length);
+  });
+
+  it("omits empty sections", () => {
+    const groups = groupByDomain([{ slug: "1", domain: "build" }], domainOf);
+    expect(groups).toHaveLength(1);
+    expect(groups[0].id).toBe("build");
+  });
+});
+
+describe("isKnownDomain", () => {
+  it("recognises every registry id and rejects the rest", () => {
+    for (const d of TEMPLATE_DOMAINS) expect(isKnownDomain(d.id)).toBe(true);
+    expect(isKnownDomain("made-up")).toBe(false);
+    expect(isKnownDomain(undefined)).toBe(false);
+    expect(isKnownDomain(OTHER_DOMAIN_ID)).toBe(false);
+  });
+});

package/src/domains.ts

@@ -0,0 +1,102 @@
+/**
+ * Template DOMAIN taxonomy — the authored, cross-surface grouping that sections
+ * the marketplace (CLI `market list`, browser New Space + catalog, marketplace).
+ *
+ * WHY A FIELD, NOT DERIVED FROM TAGS. Grouping is a property of the template, so
+ * it lives ON the template (`meta.domain`) — authored once, read by every
+ * surface. The alternative was a hardcoded slug→group map (or a tag heuristic)
+ * inside each consumer; that map drifts the instant a template is added, and no
+ * one authoring a template can see it. Same lesson as the vocabulary work: a
+ * declared relationship should live where it can be verified, not re-guessed.
+ *
+ * NOT `category`. The catalog already uses `category` for the PACKAGE TYPE
+ * (`workspace`/`capability`/`skill`/…). `domain` is the human subject area.
+ *
+ * WORKS FOR ANY TEMPLATE. A template may declare a domain absent from this
+ * registry, or none at all — `groupByDomain` never drops one. Known domains
+ * render first in registry order; an unknown-but-declared domain renders after
+ * them (its id title-cased); a missing domain falls into the `other` bucket,
+ * always last. So a NEW template appears correctly without touching this file —
+ * adding it here only controls a domain's ORDER and LABEL.
+ */
+
+export interface TemplateDomain {
+  id: string;
+  label: string;
+}
+
+export const OTHER_DOMAIN_ID = "other";
+export const OTHER_DOMAIN_LABEL = "More";
+
+/** Known domains, in display order (the order sections appear in a listing). */
+export const TEMPLATE_DOMAINS: readonly TemplateDomain[] = [
+  { id: "strategy", label: "Strategy & Market" },
+  { id: "revenue", label: "Sales & Marketing" },
+  { id: "content", label: "Content & Social" },
+  { id: "company", label: "Company & Operations" },
+  { id: "build", label: "Build & Operate" },
+  { id: "knowledge", label: "Knowledge & Research" },
+];
+
+const KNOWN = new Map(
+  TEMPLATE_DOMAINS.map((d, i) => [d.id, { label: d.label, order: i }] as const)
+);
+
+/** Every valid domain id the registry knows about (excludes `other`). */
+export function isKnownDomain(id: string | undefined | null): boolean {
+  return id != null && KNOWN.has(id);
+}
+
+/** Display label for a domain id. Missing → "More"; unknown-declared → title-cased id. */
+export function domainLabel(id: string | undefined | null): string {
+  if (!id) return OTHER_DOMAIN_LABEL;
+  const known = KNOWN.get(id);
+  if (known) return known.label;
+  return id
+    .replace(/[-_]/g, " ")
+    .replace(/\b\w/g, (c) => c.toUpperCase());
+}
+
+export interface DomainGroup<T> {
+  id: string;
+  label: string;
+  items: T[];
+}
+
+/**
+ * Partition `items` into ordered domain sections: known domains first (registry
+ * order), then unknown-but-declared domains (alphabetical), then the missing
+ * "More" bucket, always last. Empty sections are omitted; nothing is dropped.
+ * Item order WITHIN a section is preserved from the input.
+ */
+export function groupByDomain<T>(
+  items: readonly T[],
+  domainOf: (item: T) => string | undefined | null
+): DomainGroup<T>[] {
+  const buckets = new Map<string, T[]>();
+  for (const item of items) {
+    const id = domainOf(item) || OTHER_DOMAIN_ID;
+    const bucket = buckets.get(id);
+    if (bucket) bucket.push(item);
+    else buckets.set(id, [item]);
+  }
+
+  const rank = (id: string): number => {
+    if (id === OTHER_DOMAIN_ID) return Number.MAX_SAFE_INTEGER;
+    const known = KNOWN.get(id);
+    return known ? known.order : 1_000_000; // unknown-declared: after known, before "other"
+  };
+
+  return [...buckets.entries()]
+    .sort(([a], [b]) => {
+      const ra = rank(a);
+      const rb = rank(b);
+      if (ra !== rb) return ra - rb;
+      return a < b ? -1 : a > b ? 1 : 0;
+    })
+    .map(([id, groupItems]) => ({
+      id,
+      label: id === OTHER_DOMAIN_ID ? OTHER_DOMAIN_LABEL : domainLabel(id),
+      items: groupItems,
+    }));
+}

package/src/ecosystem.yaml

@@ -8,6 +8,7 @@
 
 meta:
   slug: ecosystem
+  domain: strategy
   name: Ecosystem
   description: Map the market you operate in — the partners, competitors, and players, the segments and trends, and the relationships between them.
   icon: radar
@@ -170,7 +171,8 @@ profiles:
         label: Type
         valueType: string
         inputType: select
-        enumValues: [raise, partnership, launch, acquisition, listing, conference, other]
+        enumValues:
+          [raise, partnership, launch, acquisition, listing, conference, other]
       - slug: event-date
         label: Date
         valueType: date
@@ -390,9 +392,19 @@ playbooks:
       profileSlug: competitor
     params:
       - { name: competitor, type: entity, label: Competitor, required: true }
-      - { name: focus, type: text, label: Focus area, defaultValue: "product, pricing, and positioning" }
+      - {
+          name: focus,
+          type: text,
+          label: Focus area,
+          defaultValue: "product, pricing, and positioning",
+        }
       - { name: companyContext, type: text, label: Our company context }
-      - { name: outputTypes, type: text, label: Outputs, defaultValue: "a head-to-head comparison summary and an updated competitor profile" }
+      - {
+          name: outputTypes,
+          type: text,
+          label: Outputs,
+          defaultValue: "a head-to-head comparison summary and an updated competitor profile",
+        }
     executor: is-agent
     # A radar MONITOR: bound to the competitor KIND + a schedule → the backing
     # cron automation fans out (query→loop→playbook_run) and runs this once per
@@ -423,7 +435,12 @@ playbooks:
       angles you covered, and why each new one matters.
     schedule: { cron: "0 9 * * 1", enabled: false }
     params:
-      - { name: ourSpace, type: text, label: Our market / category, required: true }
+      - {
+          name: ourSpace,
+          type: text,
+          label: Our market / category,
+          required: true,
+        }
     executor: is-agent
     grants:
       - exa_search

package/src/enterprise-os.yaml

@@ -20,6 +20,7 @@
 
 meta:
   slug: enterprise-os
+  domain: company
   name: Enterprise OS
   description: Stand up a company's public operating core in one install — strategy, market, operations, and pipeline — plus a command tower to track objectives across them.
   icon: layout-dashboard
@@ -47,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