@synap-core/workspace-templates 0.5.0 → 0.6.1

package/src/ecosystem.yaml

@@ -0,0 +1,478 @@
+# Ecosystem workspace template
+# The BASE market-graph domain: the players you operate around (partners,
+# competitors, companies, people), the segments and trends that matter, and —
+# the net-new value — the TYPED RELATIONSHIPS between actors (who partners with,
+# competes with, invested in, integrates with whom).
+# Merges + supersedes the old Radar template (carries its market-segment, trend,
+# inspiration kinds, its competitor role, and its graph "Radar Map" view forward).
+
+meta:
+  slug: ecosystem
+  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
+  color: "#0EA5E9"
+  tags: [ecosystem, market, partners, competitors, graph]
+  isPublic: true
+
+# SSOT ordering guarantee — this template REFERENCES foundation's pod-wide
+# shared `partner` 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. Requiring foundation makes the
+# resolver install it first (deps-first), so the base is always foundation's
+# SSOT body and never this template's. `require`, not `compose`: foundation is a
+# real workspace, not an overlay. (`competitor` is owned HERE — not foundation's.)
+dependencies:
+  - slug: foundation
+    kind: workspace
+    relation: require
+    reason: "Provides the pod-wide partner role vocabulary this workspace reuses."
+
+workspace:
+  name: Ecosystem
+  description: Map the market you operate in — the partners, competitors, and players, the segments and trends, and the relationships between them.
+  subtype: ecosystem
+  visibility: pod_visible
+  capabilities:
+    - ecosystem.actors
+    - ecosystem.graph
+    - ecosystem.segments
+  sourceRoles:
+    ecosystem: provider
+
+profiles:
+  # ── Actors ────────────────────────────────────────────────────────────────
+  # The pod-wide person and company kinds — declared minimally here so facets
+  # (competitor/partner) and actor↔actor relations resolve. Kept light on
+  # purpose: this is the base agnostic identity, not a full CRM record.
+  - slug: person
+    displayName: Person
+    icon: user
+    color: amber
+    description: A person in the ecosystem — a founder, operator, or contact.
+    properties:
+      - slug: email
+        label: Email
+        valueType: string
+        inputType: email
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  - slug: company
+    displayName: Company
+    icon: building-2
+    color: "#10B981"
+    description: A company in the ecosystem — a player you operate around.
+    properties:
+      - slug: website
+        label: Website
+        valueType: string
+        inputType: url
+      - slug: industry
+        label: Industry
+        valueType: string
+        inputType: text
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  # ── Market structure (carried verbatim from Radar) ──────────────────────────
+  - slug: market-segment
+    displayName: Market Segment
+    icon: pie-chart
+    color: blue
+    description: A slice of the market with its own size, maturity, and dynamics.
+    properties:
+      - slug: description
+        label: Description
+        valueType: string
+        inputType: textarea
+      - slug: tam
+        label: TAM
+        valueType: string
+        inputType: text
+      - slug: sam
+        label: SAM
+        valueType: string
+        inputType: text
+      - slug: som
+        label: SOM
+        valueType: string
+        inputType: text
+      - slug: ocean
+        label: Ocean
+        valueType: string
+        inputType: select
+        enumValues: [blue, red]
+      - slug: maturity
+        label: Maturity
+        valueType: string
+        inputType: select
+        enumValues: [emerging, growing, mature, declining]
+
+  - slug: trend
+    displayName: Trend
+    icon: trending-up
+    color: violet
+    description: A directional shift in the market, tech, or behavior worth tracking.
+    properties:
+      - slug: description
+        label: Description
+        valueType: string
+        inputType: textarea
+      - slug: direction
+        label: Direction
+        valueType: string
+        inputType: select
+        enumValues: [rising, steady, fading]
+      - slug: sources
+        label: Sources
+        valueType: array
+        inputType: text
+      - slug: relevance
+        label: Relevance
+        valueType: string
+        inputType: select
+        enumValues: [low, medium, high]
+        constraints: { defaultValue: medium }
+
+  - slug: inspiration
+    displayName: Inspiration
+    icon: sparkles
+    color: amber
+    description: A brand, founder, product, or campaign worth learning from.
+    properties:
+      - slug: kind
+        label: Kind
+        valueType: string
+        inputType: select
+        enumValues: [brand, founder, product, campaign]
+      - slug: why
+        label: Why
+        valueType: string
+        inputType: textarea
+      - slug: url
+        label: URL
+        valueType: string
+        inputType: url
+
+  # ── Market event (NEW) ──────────────────────────────────────────────────────
+  - slug: ecosystem-event
+    displayName: Ecosystem Event
+    icon: zap
+    color: orange
+    description: A notable market event — a raise, partnership, launch, acquisition, or listing.
+    properties:
+      - slug: event-type
+        label: Type
+        valueType: string
+        inputType: select
+        enumValues: [raise, partnership, launch, acquisition, listing, conference, other]
+      - slug: event-date
+        label: Date
+        valueType: date
+        inputType: date
+      - slug: event-actor
+        label: Actor
+        valueType: entity_id
+        targetProfileSlug: company
+        inputType: entity_select
+      - slug: event-summary
+        label: Summary
+        valueType: string
+        inputType: textarea
+      - slug: event-url
+        label: URL
+        valueType: string
+        inputType: url
+      - slug: event-impact
+        label: Impact
+        valueType: string
+        inputType: select
+        enumValues: [low, medium, high]
+
+  # ── Actor roles (facets — the generic hats an actor plays) ──────────────────
+  # Competitor: carried verbatim from Radar.
+  - slug: competitor
+    displayName: Competitor
+    icon: crosshair
+    color: red
+    description: A rival or alternative a buyer would compare you to.
+    # Shared like the other actor roles (partner/client/sponsor): defined once,
+    # pod-wide, so any workspace that needs the hat reuses THIS row + a grant
+    # rather than forking a workspace-scoped twin.
+    scope: shared
+    profileKind: role
+    applicableKinds:
+      - company
+    properties:
+      - slug: positioning
+        label: Positioning
+        valueType: string
+        inputType: textarea
+      - slug: strengths
+        label: Strengths
+        valueType: string
+        inputType: textarea
+      - slug: weaknesses
+        label: Weaknesses
+        valueType: string
+        inputType: textarea
+      - slug: pricing
+        label: Pricing
+        valueType: string
+        inputType: text
+      - slug: url
+        label: URL
+        valueType: string
+        inputType: url
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [watching, active-threat, adjacent, archived]
+        constraints: { defaultValue: watching }
+
+  # Partner (shared ecosystem role — SSOT is foundation.yaml) ─────────────────
+  # `scope: shared` dedups to the ONE pod-wide `partner` profile seeded by
+  # foundation; provisioning grants THIS workspace access to it (SHARED profiles
+  # are grant-gated, so the reference is required). Shapes match foundation
+  # verbatim, so no property drift.
+  - slug: partner
+    displayName: Partner
+    icon: handshake
+    color: teal
+    description: A partner relationship — both a referral source and a co-delivery collaborator, distinguished by partner type.
+    scope: shared
+    profileKind: role
+    applicableKinds:
+      - company
+      - person
+    properties:
+      - slug: partnerStatus
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues:
+          - prospect
+          - active
+          - paused
+          - churned
+      - slug: partnerType
+        label: Partner Type
+        valueType: string
+        inputType: select
+        enumValues:
+          - referral
+          - co-delivery
+          - both
+      - slug: accountManager
+        label: Account Manager
+        valueType: string
+        inputType: text
+      - slug: engagementStartDate
+        label: Engagement Start
+        valueType: date
+        inputType: date
+      - slug: satisfactionScore
+        label: Satisfaction
+        valueType: number
+        inputType: number
+      - slug: lifetimeValue
+        label: Lifetime Value
+        valueType: number
+        inputType: number
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+      - slug: contractValue
+        label: Contract Value
+        valueType: number
+        inputType: number
+      - slug: renewalDate
+        label: Renewal Date
+        valueType: date
+        inputType: date
+      - slug: healthScore
+        label: Health
+        valueType: string
+        inputType: select
+        enumValues:
+          - healthy
+          - at_risk
+          - critical
+
+views:
+  - name: Ecosystem Map
+    slug: ecosystem-map
+    type: graph
+    scopeProfileSlugs: [company, market-segment, trend, ecosystem-event]
+    description: The market landscape as a connected map — actors, segments, trends, and events, with the edges between them.
+    defaultView: true
+  - name: Segments
+    slug: segments
+    type: table
+    scopeProfileSlug: market-segment
+    description: Market slices with rough size, ocean, and maturity.
+    config:
+      columns: [title, ocean, tam, maturity]
+  - name: Trends
+    slug: trends
+    type: table
+    scopeProfileSlug: trend
+    description: Directional shifts to track, by relevance.
+    config:
+      columns: [title, direction, relevance, description]
+  - name: Events
+    slug: events
+    type: table
+    scopeProfileSlug: ecosystem-event
+    description: Notable market events — raises, partnerships, launches, and more.
+    config:
+      columns: [title, event-type, event-date, event-impact]
+
+# Schema-level relations — the market GRAPH. This is the net-new value: actor↔actor
+# edges are first-class (source and target can both be `company`), so the Ecosystem
+# Map and relation picker carry domain-specific links from day one.
+entityLinks:
+  - sourceProfileSlug: company
+    targetProfileSlug: company
+    type: partners_with
+    label: Partners with
+  - sourceProfileSlug: company
+    targetProfileSlug: company
+    type: competes_with
+    label: Competes with
+  - sourceProfileSlug: company
+    targetProfileSlug: company
+    type: invested_in
+    label: Invested in
+  - sourceProfileSlug: company
+    targetProfileSlug: company
+    type: integrates_with
+    label: Integrates with
+  - sourceProfileSlug: competitor
+    targetProfileSlug: market-segment
+    type: competes_in
+    label: Competes in
+  - sourceProfileSlug: trend
+    targetProfileSlug: market-segment
+    type: shapes
+    label: Shapes
+  - sourceProfileSlug: ecosystem-event
+    targetProfileSlug: company
+    type: involves
+    label: Involves
+
+onboarding:
+  goal: >
+    Map the real ecosystem — the key players (companies and people), who partners
+    and competes with whom, and the segments and trends that matter — so strategy
+    is grounded in the actual market, not a vague "the market".
+  framing: |
+    THE ECOSYSTEM LEAD: Act as a sharp ecosystem lead who maps the market
+    landscape AND the relationships inside it. Push for REAL named players — not
+    "the incumbents", but the actual companies — and for the concrete edges
+    between them: who partners with whom, who competes, who invested in whom.
+    A map with no edges is just a list; the value is in the relationships.
+  expertise:
+    starters:
+      - >
+        Name the actors, then draw the edges. A list of logos tells strategy
+        nothing; the market is a GRAPH. For every company you log, propose at least
+        one real relationship — partners_with, competes_with, invested_in,
+        integrates_with — because the edges are where the leverage and the threats
+        live.
+      - >
+        Map the CATEGORY, not just named rivals. Buyers compare across tiers:
+        direct competitors, adjacent tools that solve the same job differently, and
+        the status quo ("a spreadsheet", "do nothing"). Attach the competitor role
+        to real companies and place each one in the segment it competes in.
+      - >
+        Separate players from structure. Companies and people are the ACTORS;
+        segments and trends are the STRUCTURE they move within. Anchor each trend to
+        a direction and a "so what for us", and each segment to a rough size and
+        ocean — an untimed "AI is big" tells strategy nothing.
+    blindSpots:
+      - >
+        "We have no competitors" is a red flag, not a moat — it usually means the
+        category is undefined or the buyer's real alternative (a manual workaround)
+        hasn't been named. Push to name what a buyer does TODAY instead of buying.
+      - >
+        Founders over-watch the loud incumbent and miss the fast-moving insurgent
+        one tier down, and they log companies with no relationships at all. Surface
+        the insurgents, and force at least one real edge per key player.
+      - >
+        A trend or event with no stance is just a headline. Every trend needs a
+        direction (rising/steady/fading) and a "so what"; every logged event needs
+        an actor and an impact. Force the meaning, not just the mention.
+    bar: >
+      The map reads like a real ecosystem: named companies placed in their segments,
+      real edges between them (who partners, competes, invested), and each trend
+      carrying a direction and a "so what" — so a strategist can see the alliances,
+      the threats, and the open lane, not just a pile of logos.
+  collect:
+    - profileSlug: company
+      what: The real companies in your ecosystem — the players you operate around.
+      cardinality: several
+      keyFields: [industry, website]
+    - profileSlug: market-segment
+      what: The market slices you play in, with rough size and ocean.
+      cardinality: few
+      keyFields: [ocean, tam]
+    - profileSlug: trend
+      what: Directional shifts in tech, market, or behavior that affect you.
+      cardinality: few
+      keyFields: [direction, relevance]
+  openingQuestions:
+    - "Who are the key players in your space — the 3-5 companies that matter most?"
+    - "How do they relate — who partners with, competes with, or invested in whom?"
+    - "Which market segment matters most right now, and what trend is reshaping it?"
+  doneWhen: A few companies captured, with at least one relationship edge between them, plus one market segment.
+
+app:
+  kind: stored
+  cellKey: entity-detail
+
+layout:
+  defaultView: Ecosystem Map
+  defaultApp: null
+  pinnedApps: [dashboard, data]
+  sidebarItems:
+    - kind: view
+      viewName: Ecosystem Map
+      label: Ecosystem Map
+      icon: radar
+    - kind: view
+      viewName: Segments
+      label: Segments
+      icon: pie-chart
+    - kind: view
+      viewName: Trends
+      label: Trends
+      icon: trending-up
+    - kind: view
+      viewName: Events
+      label: Events
+      icon: zap
+    - kind: app
+      appId: data
+      label: Data
+      icon: database
+
+bento:
+  viewName: Ecosystem Map
+  blocks:
+    - kind: view
+      viewName: Ecosystem Map
+      pos: { x: 0, y: 0, w: 8, h: 6 }
+    - kind: view
+      viewName: Segments
+      pos: { x: 8, y: 0, w: 4, h: 3 }
+    - kind: view
+      viewName: Trends
+      pos: { x: 8, y: 3, w: 4, h: 3 }

package/src/enterprise-os.yaml

@@ -0,0 +1,183 @@
+# Enterprise OS — the public operating system suite
+# ==================================================
+# A SUITE template: it stands up a whole company's public operating core in one
+# install by REQUIRING its constituent workspaces (deps-first), then adds a thin
+# "command tower" home of its own — a place to track the company's objectives
+# across the lenses it just installed.
+#
+# What it composes (all public, all bundled):
+#   • foundation — strategic DNA (mission, audience, positioning, principles)
+#   • ecosystem  — the market graph (partners, competitors, segments, trends)
+#   • operations — how the company runs (the operational lens)
+#   • crm        — the pipeline (contacts, leads, clients, deals)
+#
+# It uses `require` (not `compose`): each constituent is a REAL workspace, not an
+# overlay. Deps-first resolution installs foundation first (the SSOT role
+# vocabulary provider), so every downstream lens reuses foundation's pod-wide
+# roles rather than forking twins. Installing Enterprise OS a second time is
+# idempotent — the resolver reuses existing constituent workspaces by slug.
+
+meta:
+  slug: enterprise-os
+  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
+  color: "#4F46E5"
+  tags: [suite, enterprise, os, foundation, crm, operations, ecosystem]
+  isPublic: true
+
+# Deps-first: foundation is the pod-wide role-vocabulary provider, so it must
+# resolve before ecosystem/operations/crm reuse its shared roles. `require` (not
+# `compose`): each is a standalone workspace, not an additive overlay.
+dependencies:
+  - slug: foundation
+    kind: workspace
+    relation: require
+    reason: "Strategic DNA + the pod-wide role vocabulary (partner/client/lead) every other lens reuses. Must resolve first."
+  - slug: ecosystem
+    kind: workspace
+    relation: require
+    reason: "The market graph — the players, segments, and trends the company operates around."
+  - slug: operations
+    kind: workspace
+    relation: require
+    reason: "How the company runs — the operational lens."
+  - slug: crm
+    kind: workspace
+    relation: require
+    reason: "The pipeline — contacts, leads, clients, and deals."
+
+workspace:
+  name: Enterprise OS
+  description: The command tower for the company operating system — track strategic objectives across the strategy, market, operations, and pipeline lenses this suite installs.
+  subtype: enterprise-os
+  visibility: pod_visible
+  sourceRoles:
+    strategy: consumer
+
+profiles:
+  # The one native profile the command tower owns: a strategic objective the
+  # company is driving across the lenses this suite installs. Deliberately light
+  # — the depth lives in the constituent workspaces; this is the cross-cutting
+  # scoreboard that ties them together.
+  - slug: objective
+    displayName: Objective
+    icon: target
+    color: "#4F46E5"
+    description: A company objective the operating system is driving toward — the cross-cutting outcome the lenses serve.
+    properties:
+      - slug: outcome
+        label: Outcome
+        valueType: string
+        inputType: textarea
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [on-track, at-risk, off-track, achieved]
+        constraints: { defaultValue: on-track }
+      - slug: horizon
+        label: Horizon
+        valueType: string
+        inputType: select
+        enumValues: [now, next, later]
+        constraints: { defaultValue: now }
+      - slug: owner
+        label: Owner
+        valueType: string
+        inputType: text
+      - slug: targetDate
+        label: Target Date
+        valueType: date
+        inputType: date
+
+views:
+  - name: Objectives
+    slug: objectives
+    type: table
+    scopeProfileSlug: objective
+    description: The company's strategic objectives across every lens, by horizon and status.
+    defaultView: true
+    config:
+      columns: [title, status, horizon, owner, targetDate]
+  - name: Objective Board
+    slug: objective-board
+    type: kanban
+    scopeProfileSlug: objective
+    description: Objectives grouped by status — a running scoreboard for the operating system.
+    config:
+      groupBy: status
+
+onboarding:
+  goal: >
+    Stand up the company's operating core and name the handful of strategic
+    objectives it is driving — so strategy, market, operations, and pipeline are
+    all in place and pointed at the same outcomes from day one.
+  framing: |
+    THE CHIEF OF STAFF: Act as a sharp chief of staff standing up the company OS.
+    The four lenses (foundation, ecosystem, operations, CRM) are already
+    installed — your job is to name the 3-5 objectives that cut across them, so
+    the operating system has a scoreboard, not just structure.
+  expertise:
+    starters:
+      - >
+        Name few, real objectives. An operating system with 20 objectives has
+        none; force the 3-5 that actually decide the year, each with an owner and
+        a horizon (now / next / later).
+      - >
+        Tie each objective to a lens. A good objective names where it lives —
+        pipeline growth (CRM), a market move (ecosystem), an operational fix
+        (operations), or a positioning shift (foundation) — so the scoreboard
+        maps to the structure underneath it.
+    blindSpots:
+      - >
+        Objectives with no owner and no date are wishes. Every one needs a single
+        owner and a target date, or it will not move.
+      - >
+        "Grow the business" is not an objective — it is a category. Push for the
+        specific outcome that would make this quarter a win.
+    bar: >
+      A short, honest scoreboard: 3-5 objectives, each owned, dated, placed on a
+      horizon, and tied to the lens that serves it — sitting on top of a fully
+      installed operating core.
+  collect:
+    - profileSlug: objective
+      what: The 3-5 strategic objectives the company is driving this horizon.
+      cardinality: few
+      keyFields: [status, horizon, owner]
+  openingQuestions:
+    - "What are the 3-5 objectives that will decide this year for the company?"
+    - "Who owns each one, and is it a now, next, or later horizon?"
+  doneWhen: A few objectives captured, each with an owner and a horizon.
+
+app:
+  kind: stored
+  cellKey: entity-detail
+
+layout:
+  defaultView: Objectives
+  defaultApp: null
+  pinnedApps: [dashboard, data]
+  sidebarItems:
+    - kind: view
+      viewName: Objectives
+      label: Objectives
+      icon: target
+    - kind: view
+      viewName: Objective Board
+      label: Board
+      icon: kanban-square
+    - kind: app
+      appId: data
+      label: Data
+      icon: database
+
+bento:
+  viewName: Objectives
+  blocks:
+    - kind: view
+      viewName: Objectives
+      pos: { x: 0, y: 0, w: 8, h: 4 }
+    - kind: view
+      viewName: Objective Board
+      pos: { x: 8, y: 0, w: 4, h: 4 }