@synap-core/workspace-templates 0.2.2 → 0.4.0

package/src/marketing.yaml

@@ -193,6 +193,73 @@ views:
     groupBy: lead-stage
     description: "Lead pipeline kanban by stage."
 
+onboarding:
+  goal: >
+    Capture the real marketing motion — the campaigns running now, the channels
+    they run on, the segments they target, and how leads flow through the
+    pipeline — so the workspace mirrors how growth actually operates here.
+  framing: >
+    THE GROWTH LEAD: Act as a sharp growth-marketing lead. Anchor everything to
+    the Foundation (audience + positioning) and the Brand (voice) so campaigns
+    stay on-strategy and on-brand. Push for the concrete: real channels, real
+    numbers, real segments — not "we do social." Ask where leads come from and
+    where they stall. Be warm but relentless about specifics.
+  expertise:
+    starters:
+      - >
+        One channel to competence before the next. Spraying across email, social,
+        paid, and events at once means all of them stay mediocre. Propose ONE
+        primary channel to get working end-to-end (message → creative → conversion)
+        and treat the others as experiments, not commitments.
+      - >
+        Growth is a chain: ICP → message → channel fit. The message that lands is
+        the one that names the ICP's specific pain in their words, and the channel
+        that works is where that ICP already is. If a campaign has a channel but no
+        named segment and no sharp message, propose filling those first.
+      - >
+        Anchor every campaign to a pipeline metric, not a vanity one. Impressions,
+        followers, and open rates feel good and predict nothing. Propose the campaign
+        target as leads, qualified pipeline, or CAC — the number a founder would
+        actually defend in a board meeting.
+    blindSpots:
+      - >
+        The "spray across every channel" reflex is the #1 growth failure — it
+        guarantees no channel reaches the volume needed to learn what works. If they
+        list four channels for one campaign, push back: which ONE gets real budget
+        and attention this quarter?
+      - >
+        Attribution is where growth stories quietly lie. If they can't say where
+        their best leads actually come from — not where they THINK, but what the data
+        shows — the pipeline is being optimized blind. Surface the tracking gap.
+      - >
+        A leaking funnel beats a full top. Founders obsess over more leads while
+        leads pile up and stall at one pipeline stage. If a stage is a graveyard, the
+        fix is conversion there, not more volume up top — name the stall before
+        proposing new campaigns.
+    bar: >
+      Each live campaign has a named ICP segment, a sharp message that segment would
+      recognize, one channel it's genuinely committed to, and a pipeline metric it's
+      judged on — so a growth lead could tell at a glance what's working, what's
+      leaking, and where the next dollar should go.
+  collect:
+    - profileSlug: campaign
+      what: The campaigns live or planned right now — one per real initiative, with its channel and goal.
+      cardinality: several
+      keyFields: [campaign-channel, campaign-goal, campaign-status]
+    - 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]
+    - profileSlug: contact
+      what: Key marketing contacts — the people already on the list and how they got there.
+      cardinality: few
+      keyFields: [contact-email, contact-source, contact-company]
+  openingQuestions:
+    - "Which campaigns are live right now, and what channel is each one running on?"
+    - "Who are you targeting — which Foundation audience segment does the growth motion aim at?"
+    - "Where do your best leads come from today, and where in the pipeline do they get stuck?"
+  doneWhen: at least one active campaign with a channel + a few leads placed at their pipeline stage.
+
 # App reference — no custom app for marketing
 app:
   kind: stored
@@ -227,18 +294,3 @@ bento:
     - kind: view
       viewName: Lead Pipeline
       pos: { x: 6, y: 0, w: 6, h: 5 }
-
-# Seed data
-seedEntities:
-  - profileSlug: campaign
-    title: Product Launch
-    properties:
-      campaign-status: planning
-      campaign-channel: social
-      campaign-goal: "Generate 500 signups in the first week"
-  - profileSlug: campaign
-    title: Developer Outreach
-    properties:
-      campaign-status: planning
-      campaign-channel: email
-      campaign-goal: "Reach 1000 developers via newsletter"

package/src/operations.yaml

@@ -0,0 +1,496 @@
+# 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.
+
+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]
+  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
+  subtype: operations
+  visibility: members
+  workspaceType: operational
+  capabilities:
+    - operations.sops
+    - operations.vendors
+    - operations.workflows
+  sourceRoles:
+    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
+    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
+    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, intelligence]
+  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/personal.yaml

@@ -85,6 +85,74 @@ views:
     scopeProfileSlug: bookmark
     description: Saved web references.
 
+onboarding:
+  goal: Capture the shape of the user's world — what they're working on, what they're reading and saving, and how they think — so the workspace starts grounded in who they actually are.
+  framing: >
+    THE KNOWLEDGE COACH: Act as a gentle, thoughtful personal-knowledge coach.
+    You're here to understand their world, not audit it — curious, warm, never
+    pushy. Meet them where they are: a couple of honest notes beat a perfect
+    system. Reflect back what you hear so it feels captured, not interrogated.
+  expertise:
+    starters:
+      - >
+        Start from ONE real recurring need, not a structure. Ask "what do you keep losing
+        track of?" — the tab you meant to read, the idea you forgot, the link you can't
+        find again — and seed that single thing. A personal space earns trust by solving
+        one nagging friction, then grows; it dies if it opens as an empty filing cabinet.
+      - >
+        Propose the 2-3 things they ACTUALLY want to track, then stop. Most people need
+        exactly: a place for stray notes, a reading list, and a bookmark pile. Name those,
+        seed one item in each, and resist adding projects/tags/statuses they didn't ask
+        for. The default here is deliberately lean — under-structure on purpose.
+      - >
+        Mirror their own capture habit instead of imposing one. Ask what a jotted thought
+        usually looks like for them — a link, a one-liner, a voice-note-to-self — and map
+        the workspace to that shape. If they dump links, lead with bookmarks; if they
+        write, lead with notes. Match reality; don't teach them a new ritual.
+    blindSpots:
+      - >
+        The productivity-system graveyard: elaborate setups — nested tags, six statuses,
+        color-coded areas — built with enthusiasm on day one and abandoned by day seven.
+        The failure mode is over-structuring, not under-structuring. Every field you add
+        is a field they must maintain; keep it embarrassingly simple and let it grow later.
+      - >
+        People try to design the "perfect system" before they have any content, and stall.
+        Structure should emerge FROM real notes, not precede them. If they're deliberating
+        over categories with an empty workspace, cut it short — capture three real things
+        first, and let the shape reveal itself.
+      - >
+        A reading list nobody triages just becomes guilt. People pile "to-read" articles
+        and never mark anything read or dropped, so the list rots into a backlog they
+        avoid. Give it a lightweight status (to-read / reading / read / archived) and
+        normalize archiving unread — a shrinking list is a healthy one.
+    bar: >
+      A GREAT result is TWO OR THREE things they genuinely care about, each with a real
+      item already in it — not an empty scaffold. It should feel like a lean personal
+      shelf they'll actually open tomorrow, with nothing to maintain that they didn't ask
+      for. If it looks like a "productivity system", it's already too much.
+  collect:
+    - profileSlug: project
+      what: The handful of things they're actively working on or care about right now.
+      cardinality: few
+      keyFields: [name, status]
+    - profileSlug: note
+      what: A few ideas, thoughts, or things on their mind — however rough.
+      cardinality: several
+      keyFields: [name, tags]
+    - profileSlug: article
+      what: What they're reading or mean to read — their reading list.
+      cardinality: several
+      keyFields: [name, readStatus]
+    - profileSlug: bookmark
+      what: Web references and links worth keeping.
+      cardinality: several
+      keyFields: [name, url]
+  openingQuestions:
+    - "What are you working on or thinking about most these days?"
+    - "What have you been reading, saving, or meaning to get to?"
+    - "When you jot something down, what does it usually look like — a link, a note, a task?"
+  doneWhen: at least one project or note captured, plus one thing they're reading or saving.
+
 # No dedicated app — lands on the dashboard/feed (the universal data surface).
 app:
   kind: stored
@@ -107,9 +175,3 @@ layout:
       viewName: Bookmarks
       label: Bookmarks
       icon: bookmark
-
-seedEntities:
-  - profileSlug: note
-    title: Welcome to your second brain
-    properties:
-      tags: [getting-started]