@synap-core/workspace-templates 0.5.0 → 0.6.0

package/src/hr.yaml

@@ -37,6 +37,9 @@ profiles:
     icon: user-round
     color: indigo
     description: "A person on the team — the core people record."
+    profileKind: role
+    applicableKinds:
+      - person
     properties:
       - slug: role-title
         label: Role
@@ -123,6 +126,9 @@ profiles:
     icon: user-plus
     color: cyan
     description: "A person moving through the hiring pipeline for a role."
+    profileKind: role
+    applicableKinds:
+      - person
     properties:
       - slug: stage
         label: Stage

package/src/index.ts

@@ -36,6 +36,7 @@ export type {
   TemplateIntegration,
   TemplateAutomation,
   TemplateExtendsRef,
+  TemplateDependency,
   TemplateProfileEntityBentoTemplates,
   TemplateDefaultSource,
   TemplateSourceRole,
@@ -43,20 +44,20 @@ export type {
   TemplateOnboardingCollectTarget,
   TemplatePlaybook,
   TemplatePlaybookParam,
-} from './types.js';
+} from "./types.js";
 
 export {
   WORKSPACE_TEMPLATES,
   getWorkspaceTemplate,
   listWorkspaceTemplates,
   listPublicTemplates,
-} from './templates.js';
+} from "./templates.js";
 
-export type { WorkspaceTemplateSlug } from './templates.js';
+export type { WorkspaceTemplateSlug } from "./templates.js";
 
-export { toWorkspaceDefinition, toPackageDefinition } from './define.js';
+export { toWorkspaceDefinition, toPackageDefinition } from "./define.js";
 export type {
   WorkspaceDefinitionInput,
   ToDefinitionResult,
   PackageDefinitionOutput,
-} from './define.js';
+} from "./define.js";

package/src/internal-runbook.yaml

@@ -0,0 +1,499 @@
+# Internal Runbook workspace template — the company's OPERATING SYSTEM.
+# The head-of-ops / chief-of-staff layer: how the business actually runs day to
+# day — the documented procedures (SOPs), the recurring processes (workflows),
+# the tool stack and vendors behind them, the metrics/SLAs that keep them
+# honest, and the rituals/cadences that keep everyone aligned.
+# Provider of the `runbook` domain. Validated against types.ts at build time.
+
+meta:
+  slug: internal-runbook
+  name: Internal Runbook
+  description: The company's operating system — SOPs, workflows, vendors, tools, metrics, and rituals that keep the business running.
+  icon: settings-2
+  color: "#64748B"
+  tags: [operations, sops, vendors, workflows]
+  isPublic: true
+
+workspace:
+  name: Internal Runbook
+  description: The operating layer of the company — documented procedures, recurring processes, the tool stack and vendors behind them, operational metrics, and the rituals that keep the team aligned.
+  proposalId: operations-v1
+  subtype: internal-runbook
+  visibility: members
+  workspaceType: operational
+  capabilities:
+    - operations.sops
+    - operations.vendors
+    - operations.workflows
+  sourceRoles:
+    runbook: provider
+
+profiles:
+  - slug: sop
+    displayName: SOP
+    icon: book-open
+    color: "#64748B"
+    description: "A standard operating procedure or runbook — the documented, repeatable way to do a thing."
+    scope: WORKSPACE
+    properties:
+      - slug: category
+        label: Category
+        valueType: string
+        inputType: select
+        enumValues: [Onboarding, Finance, People, IT, Support, Sales, Legal, Facilities, Other]
+      - slug: sop-status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [Draft, Active, Needs Review, Deprecated]
+        constraints: { defaultValue: Draft }
+      - slug: owner
+        label: Owner
+        valueType: string
+        inputType: text
+        placeholder: Who owns this procedure?
+      - slug: trigger
+        label: When to run
+        valueType: string
+        inputType: textarea
+        placeholder: What situation triggers this procedure?
+      - slug: last-reviewed
+        label: Last Reviewed
+        valueType: date
+        inputType: date
+      - slug: steps
+        label: Steps
+        valueType: string
+        inputType: textarea
+        placeholder: The step-by-step procedure...
+
+  - slug: workflow
+    displayName: Workflow
+    icon: workflow
+    color: "#0EA5E9"
+    description: "A recurring business process — a repeatable flow with an owner, a cadence, and an input/output."
+    scope: WORKSPACE
+    properties:
+      - slug: workflow-status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [Backlog, Active, Blocked, Optimizing, Retired]
+        constraints: { defaultValue: Active }
+      - slug: frequency
+        label: Frequency
+        valueType: string
+        inputType: select
+        enumValues: [Ad-hoc, Daily, Weekly, Monthly, Quarterly]
+      - slug: owner
+        label: Owner
+        valueType: string
+        inputType: text
+        placeholder: Process owner
+      - slug: automation-level
+        label: Automation
+        valueType: string
+        inputType: select
+        enumValues: [Manual, Semi-automated, Automated]
+      - slug: input
+        label: Input
+        valueType: string
+        inputType: text
+        placeholder: What kicks it off?
+      - slug: output
+        label: Output
+        valueType: string
+        inputType: text
+        placeholder: What it produces
+
+  - slug: vendor
+    displayName: Vendor
+    icon: truck
+    color: "#8B5CF6"
+    description: "A supplier, contractor, or service provider the company pays and depends on."
+    scope: WORKSPACE
+    profileKind: role
+    applicableKinds:
+      - company
+    properties:
+      - slug: vendor-category
+        label: Category
+        valueType: string
+        inputType: select
+        enumValues: [Software, Service, Supplier, Contractor, Agency, Other]
+      - slug: vendor-status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [Active, Trial, Evaluating, Paused, Churned]
+        constraints: { defaultValue: Active }
+      - slug: owner
+        label: Owner
+        valueType: string
+        inputType: text
+        placeholder: Internal relationship owner
+      - slug: monthly-cost
+        label: "Monthly Cost (€)"
+        valueType: number
+        inputType: number
+        placeholder: "0"
+      - slug: renewal-date
+        label: Renewal Date
+        valueType: date
+        inputType: date
+      - slug: website
+        label: Website
+        valueType: string
+        inputType: url
+        placeholder: "https://..."
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  - slug: tool
+    displayName: Tool
+    icon: wrench
+    color: "#F59E0B"
+    description: "A tool in the company stack — the software the team actually uses to get work done."
+    scope: WORKSPACE
+    properties:
+      - slug: tool-category
+        label: Category
+        valueType: string
+        inputType: select
+        enumValues: [Productivity, Comms, Finance, Sales, Marketing, Dev, Design, Data, HR, Other]
+      - slug: tool-status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [Active, Trial, Deprecated]
+        constraints: { defaultValue: Active }
+      - slug: owner
+        label: Owner
+        valueType: string
+        inputType: text
+        placeholder: Admin / owner
+      - slug: seats
+        label: Seats
+        valueType: number
+        inputType: number
+        placeholder: "0"
+      - slug: monthly-cost
+        label: "Monthly Cost (€)"
+        valueType: number
+        inputType: number
+        placeholder: "0"
+      - slug: url
+        label: URL
+        valueType: string
+        inputType: url
+        placeholder: "https://..."
+
+  - slug: process-metric
+    displayName: Metric
+    icon: gauge
+    color: "#10B981"
+    description: "An operational SLA or KPI — a number the team commits to and tracks against a target."
+    scope: WORKSPACE
+    properties:
+      - slug: metric-type
+        label: Type
+        valueType: string
+        inputType: select
+        enumValues: [SLA, KPI, Health]
+      - slug: metric-status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [On Track, At Risk, Off Track]
+        constraints: { defaultValue: On Track }
+      - slug: target
+        label: Target
+        valueType: string
+        inputType: text
+        placeholder: e.g. < 4h, > 95%
+      - slug: current
+        label: Current
+        valueType: string
+        inputType: text
+        placeholder: Latest reading
+      - slug: cadence
+        label: Cadence
+        valueType: string
+        inputType: select
+        enumValues: [Daily, Weekly, Monthly, Quarterly]
+      - slug: owner
+        label: Owner
+        valueType: string
+        inputType: text
+        placeholder: Who's accountable?
+
+  - slug: ritual
+    displayName: Ritual
+    icon: repeat
+    color: "#EC4899"
+    description: "A recurring meeting or cadence — standups, reviews, retros, planning — that keeps the team aligned."
+    scope: WORKSPACE
+    properties:
+      - slug: cadence
+        label: Cadence
+        valueType: string
+        inputType: select
+        enumValues: [Daily, Weekly, Biweekly, Monthly, Quarterly]
+      - slug: ritual-date
+        label: Next Occurrence
+        valueType: date
+        inputType: date
+      - slug: owner
+        label: Facilitator
+        valueType: string
+        inputType: text
+        placeholder: Who runs it?
+      - slug: attendees
+        label: Attendees
+        valueType: string
+        inputType: text
+        placeholder: Who attends?
+      - slug: duration-min
+        label: Duration (min)
+        valueType: number
+        inputType: number
+        placeholder: "30"
+      - slug: agenda
+        label: Agenda
+        valueType: string
+        inputType: textarea
+        placeholder: Standing agenda...
+
+views:
+  - name: SOPs
+    slug: sops
+    type: table
+    scopeProfileSlug: sop
+    description: The documented procedures, by category and review status.
+    defaultView: true
+    config:
+      visibleColumns: [category, sop-status, owner, last-reviewed]
+      defaultSort: { field: last-reviewed, direction: asc }
+  - name: Workflows
+    slug: workflows
+    type: kanban
+    scopeProfileSlug: workflow
+    groupBy: workflow-status
+    description: Recurring processes on a board by status.
+    config:
+      groupByField: workflow-status
+      cardFields: [frequency, owner, automation-level]
+  - name: Vendors
+    slug: vendors
+    type: table
+    scopeProfileSlug: vendor
+    description: Suppliers and service providers, with cost, owner, and renewal.
+    config:
+      visibleColumns: [vendor-category, vendor-status, owner, monthly-cost, renewal-date]
+      defaultSort: { field: monthly-cost, direction: desc }
+  - name: Tool Stack
+    slug: tool-stack
+    type: table
+    scopeProfileSlug: tool
+    description: The software the team runs on.
+    config:
+      visibleColumns: [tool-category, tool-status, owner, seats, monthly-cost]
+      defaultSort: { field: monthly-cost, direction: desc }
+  - name: Metrics
+    slug: metrics
+    type: table
+    scopeProfileSlug: process-metric
+    description: Operational SLAs and KPIs against target.
+    config:
+      visibleColumns: [metric-type, metric-status, target, current, cadence, owner]
+  - name: Rituals
+    slug: rituals
+    type: calendar
+    scopeProfileSlug: ritual
+    description: Recurring meetings and cadences on a calendar.
+    config:
+      dateField: ritual-date
+      colorField: cadence
+
+# Schema-level links — give the relation picker and graph domain-specific
+# edges from day one, not just pod defaults.
+entityLinks:
+  - sourceProfileSlug: sop
+    targetProfileSlug: workflow
+    type: documents
+    label: Documents
+  - sourceProfileSlug: workflow
+    targetProfileSlug: tool
+    type: uses
+    label: Uses
+  - sourceProfileSlug: tool
+    targetProfileSlug: vendor
+    type: provided_by
+    label: Provided by
+  - sourceProfileSlug: process-metric
+    targetProfileSlug: workflow
+    type: measures
+    label: Measures
+  - sourceProfileSlug: ritual
+    targetProfileSlug: workflow
+    type: reviews
+    label: Reviews
+
+onboarding:
+  goal: Capture how the company actually runs — its core SOPs, its recurring workflows, the vendors and tools behind them, and the rituals that keep the team aligned — so the workspace mirrors the real operating system, not a generic template.
+  framing: >
+    THE OPERATOR: Act as a seasoned head of operations / chief of staff doing an
+    ops walkthrough. Be systems-minded and pragmatic — hunt for the procedures
+    that live only in someone's head, the processes that run every week, the
+    tools quietly draining budget, and the meetings that must happen. Refuse
+    vagueness: every workflow has an owner and a cadence, every SOP has a
+    trigger. Translate their answers into SOPs, workflows, vendors, tools, and
+    rituals.
+  expertise:
+    starters:
+      - >
+        Don't map the whole org or every process — start with the few recurring
+        processes that actually BREAK: the ones that cause fire drills, missed
+        handoffs, or "who was supposed to do that?" moments. Ask what went wrong last
+        month and reverse-engineer the workflow from the failure, not from an
+        idealized flowchart.
+      - >
+        SOP the highest-frequency × highest-pain work first. A daily task that hurts
+        every time beats a quarterly one that's annoying once. Propose that
+        prioritization out loud — "let's document the thing you do 50 times a month
+        before the thing you do twice a year" — instead of documenting alphabetically.
+      - >
+        Give every workflow a single named owner and a cadence before anything else.
+        Refuse "the team owns it" — that means no one does. If they can't name one
+        accountable person, that's the finding, and the workflow's real status is
+        "at risk", not "active".
+    blindSpots:
+      - >
+        A process nobody owns doesn't exist — it just hasn't failed publicly yet.
+        Hunt for the workflows that run on habit and goodwill with no owner; those
+        are the ones that collapse the week someone is on holiday.
+      - >
+        "It's all in my head" is a single point of failure, not a system. The most
+        dangerous SOPs are the undocumented ones the founder or one key person runs
+        from memory. Ask directly: what breaks if that person is out for two weeks? —
+        and document those first.
+      - >
+        Founders confuse activity with process. A recurring meeting or a busy Slack
+        channel isn't a workflow unless it has a defined input, a defined output, and
+        a trigger. If a "process" has no clear input→output, it's a habit; name it as
+        one and either give it structure or drop it.
+    bar: >
+      The workspace captures the handful of processes that actually run (and break)
+      the business — each with one accountable owner, a cadence, and a clear
+      input→output — the highest-frequency/highest-pain procedures are documented as
+      SOPs so they survive the owner leaving, and nothing critical lives only in one
+      person's head.
+  collect:
+    - profileSlug: sop
+      what: The core documented procedures / runbooks — the repeatable ways of doing key things.
+      cardinality: several
+      keyFields: [title, category, owner, sop-status]
+    - profileSlug: workflow
+      what: The recurring processes that run the business, each with an owner and a cadence.
+      cardinality: several
+      keyFields: [title, workflow-status, frequency, owner]
+    - profileSlug: vendor
+      what: The suppliers and service providers the company pays and depends on.
+      cardinality: few
+      keyFields: [title, vendor-category, monthly-cost, owner]
+    - profileSlug: tool
+      what: The main tools in the stack the team runs on.
+      cardinality: several
+      keyFields: [title, tool-category, owner, monthly-cost]
+    - profileSlug: ritual
+      what: The recurring meetings and cadences that keep the team aligned.
+      cardinality: few
+      keyFields: [title, cadence, owner]
+  openingQuestions:
+    - "What are the procedures that live only in someone's head today — the ones you'd need to write down if that person left?"
+    - "Which processes run on a fixed cadence — weekly, monthly — and who owns each?"
+    - "What tools and vendors is the company paying for, and who's the owner of each?"
+  doneWhen: A few core SOPs are documented with owners, the key recurring workflows exist with a cadence, the main vendors and tools are captured with cost, and the standing rituals are on the calendar.
+
+app:
+  kind: stored
+  cellKey: entity-detail
+
+layout:
+  defaultView: SOPs
+  defaultApp: null
+  pinnedApps: [dashboard, data, chat]
+  sidebarItems:
+    - kind: view
+      viewName: SOPs
+      label: SOPs
+      icon: book-open
+    - kind: view
+      viewName: Workflows
+      label: Workflows
+      icon: workflow
+    - kind: view
+      viewName: Vendors
+      label: Vendors
+      icon: truck
+    - kind: view
+      viewName: Tool Stack
+      label: Tool Stack
+      icon: wrench
+    - kind: view
+      viewName: Metrics
+      label: Metrics
+      icon: gauge
+    - kind: view
+      viewName: Rituals
+      label: Rituals
+      icon: repeat
+    - kind: app
+      appId: data
+      label: All Data
+      icon: database
+
+bento:
+  viewName: Operations Command Center
+  blocks:
+    - kind: widget
+      widgetType: welcome-header
+      pos: { x: 0, y: 0, w: 12, h: 2 }
+    - kind: widget
+      widgetType: entity-count
+      pos: { x: 0, y: 2, w: 3, h: 2 }
+      config:
+        profileSlug: sop
+        label: SOPs
+    - kind: widget
+      widgetType: entity-count
+      pos: { x: 3, y: 2, w: 3, h: 2 }
+      config:
+        profileSlug: workflow
+        label: Workflows
+    - kind: widget
+      widgetType: entity-count
+      pos: { x: 6, y: 2, w: 3, h: 2 }
+      config:
+        profileSlug: vendor
+        label: Vendors
+    - kind: widget
+      widgetType: entity-count
+      pos: { x: 9, y: 2, w: 3, h: 2 }
+      config:
+        profileSlug: tool
+        label: Tools
+    - kind: view
+      viewName: Workflows
+      pos: { x: 0, y: 4, w: 8, h: 5 }
+    - kind: view
+      viewName: Metrics
+      pos: { x: 8, y: 4, w: 4, h: 5 }
+    - kind: view
+      viewName: SOPs
+      pos: { x: 0, y: 9, w: 6, h: 4 }
+    - kind: view
+      viewName: Vendors
+      pos: { x: 6, y: 9, w: 6, h: 4 }

package/src/legal.yaml

@@ -67,7 +67,7 @@ profiles:
         valueType: string
         inputType: textarea
 
-  - slug: contract
+  - slug: legal-contract
     displayName: Contract
     icon: file-signature
     color: violet
@@ -292,7 +292,7 @@ views:
   - name: Contracts
     slug: contracts
     type: table
-    scopeProfileSlug: contract
+    scopeProfileSlug: legal-contract
     description: Every agreement, its counterparty, status, and term.
     defaultView: true
     config:
@@ -300,7 +300,7 @@ views:
   - name: Renewals
     slug: renewals
     type: kanban
-    scopeProfileSlug: contract
+    scopeProfileSlug: legal-contract
     groupBy: status
     description: Contracts by lifecycle stage — catch renewals and expirations before they bite.
     config:
@@ -339,7 +339,7 @@ views:
 
 # Schema-level relations — give the relation picker domain-specific links from day one.
 entityLinks:
-  - sourceProfileSlug: contract
+  - sourceProfileSlug: legal-contract
     targetProfileSlug: legal-entity
     type: party_to
     label: Party to
@@ -356,7 +356,7 @@ entityLinks:
     type: governed_by
     label: Governed by
   - sourceProfileSlug: legal-matter
-    targetProfileSlug: contract
+    targetProfileSlug: legal-contract
     type: concerns
     label: Concerns
 
@@ -416,7 +416,7 @@ onboarding:
       what: The company's legal entities and the jurisdictions they operate in.
       cardinality: few
       keyFields: [entityType, jurisdiction, status]
-    - profileSlug: contract
+    - profileSlug: legal-contract
       what: The key live agreements — the ones with real obligations, value, or renewal dates.
       cardinality: several
       keyFields: [contractType, status, counterparty, renewalDate]

package/src/marketing.yaml

@@ -10,6 +10,21 @@ meta:
   tags: [marketing, crm, outreach, leads, campaigns]
   isPublic: true
 
+# SSOT ordering guarantee — this template REFERENCES foundation's pod-wide
+# shared `lead` role. The apply engine seeds a shared profile's pod-wide BASE
+# property body from whichever template creates it FIRST, and adds a REUSING
+# template's extra props as workspace OVERLAYS. Without this dependency,
+# marketing-first would make the pod-wide `lead` base marketing's 10-prop body
+# for EVERY workspace. Requiring foundation makes the resolver install it first
+# (deps-first), so the base is always foundation's SSOT body (leadStage, notes)
+# and marketing's extras stay per-workspace overlays. `require`, not `compose`:
+# foundation is a real workspace, not an overlay.
+dependencies:
+  - slug: foundation
+    kind: workspace
+    relation: require
+    reason: "Provides the pod-wide lead role vocabulary (leadStage) this workspace reuses."
+
 workspace:
   name: Marketing Campaign OS
   description: "Track leads, manage campaigns, and let AI help run your outreach. Contacts, pipeline, tasks, and AI briefings — all connected."
@@ -20,6 +35,8 @@ workspace:
     - marketing.contacts
     - marketing.leads
   sourceRoles:
+    brand: consumer
+    content: consumer
     marketing: provider
 
 profiles:
@@ -80,6 +97,9 @@ profiles:
     color: blue
     description: "A person in your marketing contact list."
     semanticSlug: marketing.contact
+    profileKind: role
+    applicableKinds:
+      - person
     properties:
       - slug: contact-email
         label: Email
@@ -117,19 +137,26 @@ profiles:
         valueType: string
         inputType: text
 
+  # `scope: shared` dedups to the ONE pod-wide `lead` profile seeded by
+  # foundation.yaml (SSOT for leadStage). Ordering is guaranteed by the
+  # `require: foundation` dependency above — foundation always installs first,
+  # so the pod-wide BASE body is always foundation's and the props below are
+  # always workspace OVERLAYS on top of it. That is the legitimate extension
+  # mechanism: EXTRA props are fine. What is NOT fine is REDECLARING a prop
+  # foundation already owns (e.g. `leadStage`) with a divergent enum/default —
+  # that is base drift, and the SSOT tripwire fails on it.
+  # (Standards reference inherited base props like `leadStage` directly.)
   - slug: lead
     displayName: Lead
     icon: user-plus
     color: green
     description: "A potential customer or partner contact in your pipeline"
     semanticSlug: marketing.lead
+    scope: shared
+    profileKind: role
+    applicableKinds:
+      - person
     properties:
-      - slug: lead-stage
-        label: Stage
-        valueType: string
-        inputType: select
-        enumValues: [new, contacted, interested, qualified, demo, proposal, converted, lost]
-        constraints: { defaultValue: new }
       - slug: lead-source
         label: Source
         valueType: string
@@ -164,7 +191,7 @@ profiles:
         label: Last Contacted
         valueType: date
         inputType: date
-      - slug: lead-notes
+      - slug: notes
         label: Notes
         valueType: string
         inputType: textarea
@@ -190,7 +217,7 @@ views:
     slug: lead-pipeline
     type: kanban
     scopeProfileSlug: lead
-    groupBy: lead-stage
+    groupBy: leadStage
     description: "Lead pipeline kanban by stage."
 
 onboarding:
@@ -249,7 +276,7 @@ onboarding:
     - profileSlug: lead
       what: A few representative leads already in motion, placed at their true pipeline stage.
       cardinality: several
-      keyFields: [lead-stage, lead-source, lead-company]
+      keyFields: [leadStage, lead-source, lead-company]
     - profileSlug: contact
       what: Key marketing contacts — the people already on the list and how they got there.
       cardinality: few