@synap-core/workspace-templates 0.5.0 → 0.6.1

package/src/operations.yaml

@@ -1,496 +1,222 @@
-# Operations 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 `operations` domain. Validated against types.ts at build time.
+# Operations workspace template — client-delivery domain.
+# How client work gets delivered end to end: the engagements you're running, the
+# deliverables due inside them, and the contracts that govern them. Consumes the `crm` domain, provides `operations`.
+# Validated against types.ts at build time.
 
 meta:
   slug: operations
   name: Operations
-  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]
+  description: "Deliver client work end to end — the engagements you're running, the deliverables due inside them, and the contracts that govern them. Won deals from CRM hand off into engagements here."
+  icon: briefcase
+  color: "#0F766E"
+  tags: [operations, delivery, clients, engagements]
   isPublic: true
 
 workspace:
   name: Operations
-  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
+  description: "The client-delivery layer — active engagements, their deliverables, and the contracts that govern them."
   subtype: operations
-  visibility: members
-  workspaceType: operational
+  visibility: pod_visible
   capabilities:
-    - operations.sops
-    - operations.vendors
-    - operations.workflows
+    - operations.engagements
+    - operations.deliverables
+    - operations.contracts
   sourceRoles:
+    crm: consumer
     operations: 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
+  - slug: engagement
+    displayName: Engagement
+    icon: briefcase
+    color: "#0F766E"
+    description: "A unit of client work — a project or retainer delivered for a company, with scope, dates, and value."
     properties:
-      - slug: category
-        label: Category
-        valueType: string
-        inputType: select
-        enumValues: [Onboarding, Finance, People, IT, Support, Sales, Legal, Facilities, Other]
-      - slug: sop-status
+      - slug: engagement-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
+        enumValues: [proposed, active, on-hold, completed, cancelled]
+        constraints: { defaultValue: proposed }
+      - slug: engagement-client
+        label: Client
+        valueType: entity_id
+        targetProfileSlug: company
+        inputType: entity_select
+      - slug: engagement-start
+        label: Start Date
+        valueType: date
+        inputType: date
+      - slug: engagement-end
+        label: End Date
         valueType: date
         inputType: date
-      - slug: steps
-        label: Steps
+      - slug: engagement-value
+        label: Value
+        valueType: number
+        inputType: number
+      - slug: engagement-scope
+        label: Scope
         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
+      - slug: engagement-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
+      - slug: engagement-notes
+        label: Notes
         valueType: string
-        inputType: text
-        placeholder: What it produces
+        inputType: textarea
 
-  - slug: vendor
-    displayName: Vendor
-    icon: truck
-    color: "#8B5CF6"
-    description: "A supplier, contractor, or service provider the company pays and depends on."
-    scope: WORKSPACE
+  - slug: deliverable
+    displayName: Deliverable
+    icon: package-check
+    color: "#0EA5E9"
+    description: "A concrete output owed inside an engagement — with a due date, an owner, and a status."
     properties:
-      - slug: vendor-category
-        label: Category
-        valueType: string
-        inputType: select
-        enumValues: [Software, Service, Supplier, Contractor, Agency, Other]
-      - slug: vendor-status
+      - slug: deliverable-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
+        enumValues: [not-started, in-progress, in-review, delivered, accepted]
+        constraints: { defaultValue: not-started }
+      - slug: deliverable-engagement
+        label: Engagement
+        valueType: entity_id
+        targetProfileSlug: engagement
+        inputType: entity_select
+      - slug: due-date
+        label: Due Date
+        valueType: date
+        inputType: date
+      - slug: delivered-date
+        label: Delivered Date
         valueType: date
         inputType: date
-      - slug: website
-        label: Website
+      - slug: deliverable-owner
+        label: Owner
         valueType: string
-        inputType: url
-        placeholder: "https://..."
-      - slug: notes
+        inputType: text
+      - slug: deliverable-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
+  - slug: contract
+    displayName: Contract
+    icon: file-signature
+    color: "#8B5CF6"
+    description: "The agreement that governs an engagement — its status, value, term, and signed document."
     properties:
-      - slug: tool-category
-        label: Category
-        valueType: string
-        inputType: select
-        enumValues: [Productivity, Comms, Finance, Sales, Marketing, Dev, Design, Data, HR, Other]
-      - slug: tool-status
+      - slug: contract-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 (€)"
+        enumValues: [draft, sent, signed, active, expired, terminated]
+        constraints: { defaultValue: draft }
+      - slug: contract-engagement
+        label: Engagement
+        valueType: entity_id
+        targetProfileSlug: engagement
+        inputType: entity_select
+      - slug: contract-value
+        label: Value
         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
+      - slug: start-date
+        label: Start Date
         valueType: date
         inputType: date
-      - slug: owner
-        label: Facilitator
-        valueType: string
-        inputType: text
-        placeholder: Who runs it?
-      - slug: attendees
-        label: Attendees
+      - slug: end-date
+        label: End Date
+        valueType: date
+        inputType: date
+      - slug: contract-url
+        label: Document
         valueType: string
-        inputType: text
-        placeholder: Who attends?
-      - slug: duration-min
-        label: Duration (min)
-        valueType: number
-        inputType: number
-        placeholder: "30"
-      - slug: agenda
-        label: Agenda
+        inputType: url
+      - slug: contract-notes
+        label: Notes
         valueType: string
         inputType: textarea
-        placeholder: Standing agenda...
 
+# CURATED views — the delivery motion, not one per profile
 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
+  - name: Engagements
+    slug: engagements
     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
+    scopeProfileSlug: engagement
+    groupBy: engagement-status
+    description: "Client engagements on a board by status."
+  - name: Deliverables
+    slug: deliverables
+    type: kanban
+    scopeProfileSlug: deliverable
+    groupBy: deliverable-status
+    description: "Deliverables on a board by status."
+  - name: Contracts
+    slug: contracts
     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
+    scopeProfileSlug: contract
+    description: "Contracts with their status, value, and term."
 
 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.
+  goal: >
+    Capture the real client-delivery motion — the engagements running now, the
+    deliverables due inside them, and the contracts that govern them — so the
+    workspace mirrors how client work actually ships here.
   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.
+    THE DELIVERY LEAD: Act as a sharp delivery / operations lead. Anchor every
+    piece of work to a real client engagement — a deliverable that isn't tied to
+    an engagement is work nobody agreed to. Push for the concrete: named owners,
+    real due dates, real scope. Refuse "we're working on it" — ask which
+    engagement, who owns it, and when it's due.
   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.
+    - profileSlug: engagement
+      what: The client engagements live right now — one per real project or retainer, with its client and dates.
       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.
+      keyFields: [engagement-status, engagement-client, engagement-end]
+    - profileSlug: deliverable
+      what: The deliverables due inside those engagements, placed at their true status with a due date.
       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]
+      keyFields: [deliverable-status, due-date]
   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.
+    - "Which client engagements are active right now, and who's the client on each?"
+    - "What's due next — which deliverables are in flight, and when are they owed?"
+    - "Which engagements have a contract behind them, and which are still on a handshake?"
+  doneWhen: at least one active engagement with a deliverable placed inside it.
 
+# App reference — no custom app for operations
 app:
   kind: stored
   cellKey: entity-detail
 
+# Layout config for browser sidebar
 layout:
-  defaultView: SOPs
+  pinnedApps: [dashboard, data]
+  defaultView: Engagements
   defaultApp: null
-  pinnedApps: [dashboard, data, chat]
   sidebarItems:
     - kind: view
-      viewName: SOPs
-      label: SOPs
-      icon: book-open
+      viewName: Engagements
+      label: Engagements
+      icon: briefcase
     - kind: view
-      viewName: Workflows
-      label: Workflows
-      icon: workflow
+      viewName: Deliverables
+      label: Deliverables
+      icon: package-check
     - 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
+      viewName: Contracts
+      label: Contracts
+      icon: file-signature
 
+# Bento dashboard
 bento:
-  viewName: Operations Command Center
+  viewName: Engagements
   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 }
+      viewName: Deliverables
+      pos: { x: 0, y: 0, w: 6, h: 5 }
     - kind: view
-      viewName: Vendors
-      pos: { x: 6, y: 9, w: 6, h: 4 }
+      viewName: Contracts
+      pos: { x: 6, y: 0, w: 6, h: 5 }