@synap-core/workspace-templates 0.5.0 → 0.6.0

package/package.json

@@ -1,14 +1,14 @@
 {
   "name": "@synap-core/workspace-templates",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "type": "module",
   "packageManager": "pnpm@9.15.4",
   "description": "Canonical workspace definitions — YAML source + typed exports for browser, backend, CLI, and marketplace",
   "exports": {
     ".": {
-      "types": "./src/index.ts",
+      "types": "./dist/index.d.ts",
       "node": "./dist/index.js",
-      "default": "./src/index.ts"
+      "default": "./dist/index.js"
     }
   },
   "files": [
@@ -18,10 +18,10 @@
   "scripts": {
     "type-check": "tsc --noEmit",
     "build:yaml": "node build.mjs",
-    "build": "node build.mjs && tsc -p tsconfig.build.json",
+    "build": "node build.mjs && tsup",
     "provision": "node scripts/provision.mjs",
     "eval": "node scripts/eval-standard.mjs",
-    "prepublishOnly": "node build.mjs && tsc -p tsconfig.build.json"
+    "prepublishOnly": "node build.mjs && tsup"
   },
   "dependencies": {
     "zod": "^3.0.0",
@@ -30,6 +30,7 @@
   "devDependencies": {
     "@types/js-yaml": "^4.0.9",
     "@types/node": "^22.0.0",
+    "tsup": "^8.0.0",
     "typescript": "^5.5.0"
   },
   "publishConfig": {

package/src/blockchain-ecosystem.yaml

@@ -0,0 +1,372 @@
+# Blockchain Ecosystem — PRIVATE OVERLAY on the Ecosystem workspace.
+# AI-generation-friendly YAML. Validated against types.ts at build time.
+#
+# This is an OVERLAY, not a standalone workspace: it `compose`s onto the
+# Ecosystem base and layers its web3 market actors (market-makers, auditors,
+# dev-shops, KOLs, agencies), the actor↔actor relations, and a couple of curated
+# views ADDITIVELY onto that base. No separate workspace is created.
+#
+# Overlay-safety: subtype MATCHES the base (`ecosystem`, a no-op on the additive
+# reconcile), and workspace `visibility`/`capabilities` are OMITTED so the base
+# Ecosystem keeps its own identity (the reconcile REPLACES those when set).
+# The 6 web3 role-profiles are moved here verbatim from grants.yaml. company/person
+# are NOT redeclared — the reconcile resolves base profiles the overlay references.
+
+meta:
+  slug: blockchain-ecosystem
+  name: Blockchain Ecosystem
+  description: "Web3 market actors — market-makers, auditors, dev shops, KOLs — and how they connect. Overlays the Ecosystem workspace."
+  icon: boxes
+  color: "#8B5CF6"
+  tags: [blockchain, web3, ecosystem, market-makers]
+  isPublic: false
+
+# OVERLAY on Ecosystem — composes additively onto the base workspace.
+dependencies:
+  - slug: ecosystem
+    kind: workspace
+    relation: compose
+    reason: "Adds web3 market actors + relations onto your Ecosystem."
+
+workspace:
+  name: Ecosystem
+  description: "Web3 market actors and the relationships between them, layered onto your Ecosystem."
+  subtype: ecosystem
+
+profiles:
+  # ── Web3 actor roles (facets on company/person) ─────────────────────────────
+  # Moved here VERBATIM from grants.yaml — web3-specific service roles an actor
+  # plays. `scope: shared` dedups to the ONE pod-wide role profile.
+
+  # ── Market Maker (liquidity provider for a token) ─────────────────────────
+  - slug: market-maker
+    displayName: Market Maker
+    icon: candlestick-chart
+    color: sky
+    description: A liquidity provider — makes markets and provides depth for a token.
+    scope: shared
+    profileKind: role
+    applicableKinds:
+      - company
+      - person
+    properties:
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues:
+          - prospect
+          - active
+          - paused
+          - churned
+      - slug: exchanges
+        label: Exchanges / Venues
+        valueType: array
+        inputType: text
+      - slug: engagementStartDate
+        label: Engagement Start
+        valueType: date
+        inputType: date
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  # ── Security Auditor (smart-contract / protocol audits) ───────────────────
+  - slug: security-auditor
+    displayName: Security Auditor
+    icon: shield-check
+    color: red
+    description: A security firm or individual that audits smart contracts and protocols.
+    scope: shared
+    profileKind: role
+    applicableKinds:
+      - company
+      - person
+    properties:
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues:
+          - prospect
+          - active
+          - paused
+          - churned
+      - slug: specialty
+        label: Specialty
+        valueType: string
+        inputType: text
+      - slug: engagementStartDate
+        label: Engagement Start
+        valueType: date
+        inputType: date
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  # ── Dev Shop (outsourced engineering / build partner) ─────────────────────
+  - slug: dev-shop
+    displayName: Dev Shop
+    icon: code
+    color: violet
+    description: An outsourced engineering studio or build partner.
+    scope: shared
+    profileKind: role
+    applicableKinds:
+      - company
+      - person
+    properties:
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues:
+          - prospect
+          - active
+          - paused
+          - churned
+      - slug: specialty
+        label: Specialty
+        valueType: string
+        inputType: text
+      - slug: engagementStartDate
+        label: Engagement Start
+        valueType: date
+        inputType: date
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  # ── Marketing Agency (brand / growth / content marketing) ─────────────────
+  - slug: marketing-agency
+    displayName: Marketing Agency
+    icon: megaphone
+    color: pink
+    description: A brand, growth, or content marketing agency.
+    scope: shared
+    profileKind: role
+    applicableKinds:
+      - company
+      - person
+    properties:
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues:
+          - prospect
+          - active
+          - paused
+          - churned
+      - slug: specialty
+        label: Specialty
+        valueType: string
+        inputType: text
+      - slug: engagementStartDate
+        label: Engagement Start
+        valueType: date
+        inputType: date
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  # ── Paid-Ads Agency (performance / paid media buying) ─────────────────────
+  - slug: paid-ads-agency
+    displayName: Paid-Ads Agency
+    icon: badge-dollar-sign
+    color: orange
+    description: A performance / paid-media buying agency.
+    scope: shared
+    profileKind: role
+    applicableKinds:
+      - company
+      - person
+    properties:
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues:
+          - prospect
+          - active
+          - paused
+          - churned
+      - slug: channels
+        label: Channels
+        valueType: array
+        inputType: text
+      - slug: engagementStartDate
+        label: Engagement Start
+        valueType: date
+        inputType: date
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  # ── KOL (key opinion leader / influencer) ─────────────────────────────────
+  - slug: kol
+    displayName: KOL
+    icon: star
+    color: yellow
+    description: A key opinion leader or influencer who amplifies reach.
+    scope: shared
+    profileKind: role
+    applicableKinds:
+      - company
+      - person
+    properties:
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues:
+          - prospect
+          - active
+          - paused
+          - churned
+      - slug: platform
+        label: Primary Platform
+        valueType: string
+        inputType: text
+      - slug: audienceSize
+        label: Audience Size
+        valueType: number
+        inputType: number
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+# Web3 actor↔actor relations (company→company). `company` resolves from the
+# Ecosystem base — not redeclared here.
+entityLinks:
+  - sourceProfileSlug: company
+    targetProfileSlug: company
+    type: audited_by
+    label: Audited by
+  - sourceProfileSlug: company
+    targetProfileSlug: company
+    type: makes_market_for
+    label: Makes market for
+  - sourceProfileSlug: company
+    targetProfileSlug: company
+    type: built_by
+    label: Built by
+  - sourceProfileSlug: company
+    targetProfileSlug: company
+    type: advises
+    label: Advises
+
+# Curated views over the web3 roles (companies wearing each role).
+views:
+  - name: Market Makers
+    slug: market-makers
+    type: table
+    scopeProfileSlug: market-maker
+    description: Liquidity providers you work with, by status.
+    config:
+      columns: [title, status, exchanges, engagementStartDate]
+  - name: Auditors
+    slug: auditors
+    type: table
+    scopeProfileSlug: security-auditor
+    description: Security auditors you work with, by status.
+    config:
+      columns: [title, status, specialty, engagementStartDate]
+  - name: Dev Shops
+    slug: dev-shops
+    type: table
+    scopeProfileSlug: dev-shop
+    description: Build partners and engineering studios you work with.
+    config:
+      columns: [title, status, specialty, engagementStartDate]
+
+onboarding:
+  goal: >
+    Map the web3 service ecosystem — which market-makers, auditors, dev-shops,
+    and KOLs you work with, and how they connect to the projects and companies in
+    your Ecosystem — so the map shows not just the players but the service graph
+    around them.
+  framing: |
+    THE WEB3 ECOSYSTEM LEAD: Act as a sharp web3 ecosystem lead who knows the
+    service layer of the market — who provides liquidity, who audits, who ships
+    code, who moves attention. Push for REAL named firms and the concrete edges
+    between them: who audits whom, who makes markets for which token, who built
+    which product. Tag the role onto the real company, then draw the edge — a list
+    of service providers with no relationships is just a directory.
+  expertise:
+    starters:
+      - >
+        Tag the role onto the real company, don't spin up a new one. A market-maker
+        or auditor is a HAT a company wears — attach the role to the existing
+        Ecosystem company (match on domain / name first) rather than creating a
+        second entity for the same firm.
+      - >
+        The service layer is a graph, not a list. For every provider you log,
+        propose at least one real edge — audited_by, makes_market_for, built_by,
+        advises — because the value is in who serves whom, not in the roster alone.
+    blindSpots:
+      - >
+        Founders track the loud KOLs and forget the load-bearing providers — the
+        auditor gating a launch, the market-maker holding the book. Surface the
+        quiet, critical relationships, not just the visible ones.
+      - >
+        A service provider with no engagement status and no edge is a bookmark, not
+        a relationship. Force the status (prospect/active/paused/churned) and at
+        least one connection to a real project or company.
+    bar: >
+      The web3 service graph reads true: named firms wearing the right role
+      (market-maker, auditor, dev-shop, KOL), each with an engagement status and at
+      least one real edge to the company or project it serves — so a glance shows
+      who's providing liquidity, who's auditing, who's building, and who's amplifying.
+  collect:
+    - profileSlug: market-maker
+      what: The market-makers / liquidity providers you work with, tagged onto the real company.
+      cardinality: few
+      keyFields: [status, exchanges]
+    - profileSlug: security-auditor
+      what: The security auditors you work with, tagged onto the real firm.
+      cardinality: few
+      keyFields: [status, specialty]
+  openingQuestions:
+    - "Which market-makers or liquidity providers are in your orbit, and are they active?"
+    - "Who audits the projects you work with — which security firms do you trust?"
+    - "Which dev-shops or KOLs are part of your ecosystem, and how do they connect to your projects?"
+  doneWhen: a couple of web3 actors tagged onto real companies with an engagement status.
+
+app:
+  kind: stored
+  cellKey: entity-detail
+
+layout:
+  defaultView: Market Makers
+  defaultApp: null
+  pinnedApps: [dashboard, data]
+  sidebarItems:
+    - kind: view
+      viewName: Market Makers
+      label: Market Makers
+      icon: candlestick-chart
+    - kind: view
+      viewName: Auditors
+      label: Auditors
+      icon: shield-check
+    - kind: view
+      viewName: Dev Shops
+      label: Dev Shops
+      icon: code
+
+bento:
+  viewName: Market Makers
+  blocks:
+    - kind: view
+      viewName: Market Makers
+      pos: { x: 0, y: 0, w: 6, h: 5 }
+    - kind: view
+      viewName: Auditors
+      pos: { x: 6, y: 0, w: 6, h: 5 }