@synap-core/workspace-templates 0.5.0 → 0.6.1

package/src/content-os.yaml

@@ -1,24 +1,63 @@
 # Content OS workspace template
-# Creator Operations / publishing hub — campaigns, posts, pillars, platforms,
-# newsletters, and brand deals in one relational workspace.
-# Distinct from content-studio.yaml (video render pipeline) — both are kept.
-# AI-generation-friendly YAML. Validated against types.ts at build time.
+# The editorial engine — turn thinking into a published content system.
+# View-driven workspace (app: stored / entity-detail), modeled on marketing.yaml.
+#
+# This is the EDITORIAL half that used to be absorbed inside content-studio.yaml.
+# content-studio stays video/render-only; Content OS owns the publishing model:
+# posts, pillars, platforms, and newsletters.
 
 meta:
   slug: content-os
   name: Content OS
-  description: "A sovereign content operating system. Plan campaigns, manage posts across platforms, track brand deals, and own your newsletter audience — all in one relational workspace you control forever."
-  icon: file-edit
+  description: "Your editorial operating system — pillars, posts, platforms, and newsletters. Turn raw thinking into a published content engine, all connected to your campaigns and brand voice."
+  icon: pen-tool
   color: "#6366F1"
-  tags: [content, creator, social-media, newsletter, campaigns]
+  tags: [content, editorial, publishing, creator, newsletter]
   isPublic: true
 
+# The editorial `post`/`newsletter` kinds REFERENCE profiles owned elsewhere:
+#   • `campaign` — the marketing-campaign template's kind. It ships pod-wide as a
+#     workspace-scoped `kind`; requiring marketing-campaign makes the resolver
+#     install it FIRST (deps-first), so its full property body is always the SSOT
+#     base. This template re-declares `campaign` below with the SAME body so the
+#     apply resolver REUSES + promotes marketing's row (same-user workspace→shared
+#     promotion in resolve-profile-for-apply.ts) rather than minting a duplicate.
+#   • `sponsor` — foundation's pod-wide `scope: shared` role. Requiring foundation
+#     guarantees its SSOT body is the base; this template re-declares `sponsor`
+#     below with `scope: shared` (identical to grants.yaml's shared-role reuse) so
+#     provisioning dedups to the ONE pod-wide row and grants THIS workspace access.
+# Both are `require` (not `compose`): each dependency is a real standalone
+# workspace, and this template creates its OWN workspace — it does not overlay onto
+# theirs.
+dependencies:
+  - slug: foundation
+    kind: workspace
+    relation: require
+    reason: "Provides the pod-wide sponsor role vocabulary this workspace's posts/newsletters reference."
+  - slug: marketing-campaign
+    kind: workspace
+    relation: require
+    reason: "Provides the campaign kind (and its SSOT property body) this workspace's posts/newsletters link to."
+
 workspace:
-  name: "Content OS — Creator Operations Hub"
-  description: "A sovereign content operating system. Plan campaigns, manage posts across platforms, track brand deals, and own your newsletter audience — all in one relational workspace you control forever."
+  name: Content OS
+  description: >
+    The editorial operating system — a view-driven workspace over your
+    content model. Organize by pillar, track every post from Idea to
+    Published, run your platforms and newsletters, and keep it all wired
+    to the campaigns and brand voice that give it context.
   proposalId: content-os-v1
-  subtype: content-studio
-  visibility: members
+  subtype: content-os
+  visibility: pod_visible
+  capabilities:
+    - content.editorial
+    - content.pillars
+    - content.calendar
+    - content.newsletter
+  sourceRoles:
+    brand: consumer
+    marketing: consumer
+    content: provider
 
 profiles:
   - slug: post
@@ -46,12 +85,18 @@ profiles:
       - slug: post-pillar
         label: Pillar
         valueType: entity_id
+        targetProfileSlug: pillar
+        inputType: entity_select
       - slug: post-campaign
         label: Campaign
         valueType: entity_id
+        targetProfileSlug: campaign
+        inputType: entity_select
       - slug: post-sponsor
         label: Sponsor
         valueType: entity_id
+        targetProfileSlug: sponsor
+        inputType: entity_select
       - slug: publish-date
         label: Publish Date
         valueType: date
@@ -89,64 +134,6 @@ profiles:
         placeholder: "https://..."
         constraints: { format: url }
 
-  - slug: campaign
-    displayName: Campaign
-    icon: target
-    color: "#F59E0B"
-    description: "A grouped content initiative — product launch, editorial series, seasonal push, or challenge."
-    scope: WORKSPACE
-    properties:
-      - slug: campaign-status
-        label: Status
-        valueType: string
-        inputType: select
-        enumValues: ["Planned", "Active", "Completed", "Paused", "Cancelled"]
-      - slug: campaign-type
-        label: Type
-        valueType: string
-        inputType: select
-        enumValues: ["Product Launch", "Editorial Series", "Seasonal", "Brand Partnership", "Challenge", "Evergreen", "Awareness", "Other"]
-      - slug: campaign-pillar
-        label: Primary Pillar
-        valueType: entity_id
-      - slug: campaign-start
-        label: Start Date
-        valueType: date
-      - slug: campaign-end
-        label: End Date
-        valueType: date
-      - slug: campaign-goal
-        label: Goal
-        valueType: string
-        inputType: text
-        placeholder: "What does success look like? Followers, sign-ups, revenue..."
-      - slug: campaign-kpi
-        label: Primary KPI
-        valueType: string
-        inputType: select
-        enumValues: ["Follower Growth", "Newsletter Sign-ups", "Engagement Rate", "Revenue", "Reach", "Brand Deals Closed", "Link Clicks", "Other"]
-      - slug: kpi-target
-        label: KPI Target
-        valueType: number
-        inputType: number
-        placeholder: "Numeric target for the primary KPI"
-      - slug: kpi-result
-        label: KPI Result
-        valueType: number
-        inputType: number
-        placeholder: "Fill when complete"
-      - slug: campaign-budget
-        label: "Budget (€)"
-        valueType: number
-        inputType: number
-      - slug: post-count
-        label: Post Count
-        valueType: number
-        inputType: number
-      - slug: campaign-tags
-        label: Tags
-        valueType: array
-
   - slug: pillar
     displayName: Pillar
     icon: columns
@@ -297,768 +284,262 @@ profiles:
       - slug: newsletter-sponsor
         label: Sponsor
         valueType: entity_id
+        targetProfileSlug: sponsor
+        inputType: entity_select
       - slug: newsletter-campaign
         label: Campaign
         valueType: entity_id
+        targetProfileSlug: campaign
+        inputType: entity_select
       - slug: newsletter-pillar
         label: Primary Pillar
         valueType: entity_id
+        targetProfileSlug: pillar
+        inputType: entity_select
       - slug: newsletter-tags
         label: Tags
         valueType: array
 
-  - slug: sponsor
-    displayName: Sponsor
-    icon: briefcase
-    color: "#F43F5E"
-    description: "A brand deal or sponsorship — from first contact to final payment. Track deliverables, deadlines, and performance in one place."
-    scope: WORKSPACE
+  # ── Campaign (reused kind — SSOT is marketing.yaml) ───────────────────────
+  # NOT a new kind: this REFERENCES the marketing-campaign template's `campaign`.
+  # The `require: marketing-campaign` dependency installs it FIRST, so at apply
+  # the resolver finds marketing's workspace-scoped `campaign`, and — because it
+  # belongs to the same user — PROMOTES it to `shared` and grants THIS workspace
+  # access (resolve-profile-for-apply.ts: the same-actor workspace→shared branch),
+  # instead of minting a duplicate. Scope is OMITTED (= workspace) to MATCH
+  # marketing's own declaration: the promotion to pod-wide is the resolver's job,
+  # not ours to assert — and on the standalone-create fallback a workspace scope
+  # never usurps the pod-wide SSOT seat. Body kept verbatim so no property drift.
+  - slug: campaign
+    displayName: Campaign
+    icon: megaphone
+    color: pink
+    description: "A marketing campaign — email, social, event, content, or partnership"
+    semanticSlug: marketing.campaign
     properties:
-      - slug: deal-status
-        label: Deal Status
+      - slug: campaign-status
+        label: Status
         valueType: string
         inputType: select
-        enumValues: ["Prospecting", "Outreach Sent", "In Negotiation", "Contract Signed", "Active", "Deliverables Pending", "Completed", "Invoiced", "Paid", "Declined"]
-      - slug: sponsor-type
-        label: Deal Type
+        enumValues: [planning, active, paused, completed, cancelled]
+        constraints: { defaultValue: planning }
+      - slug: campaign-channel
+        label: Channel
         valueType: string
         inputType: select
-        enumValues: ["Newsletter Sponsorship", "Social Post", "Podcast Ad", "Video Integration", "Affiliate", "Product Review", "Ambassador", "Event", "Other"]
-      - slug: contact-name
-        label: Contact Name
+        enumValues: [email, social, event, content, partnership, paid, organic, other]
+      - slug: campaign-goal
+        label: Goal
         valueType: string
-        inputType: text
-        placeholder: "Brand contact / campaign manager"
-      - slug: contact-email
-        label: Contact Email
+        inputType: textarea
+      - slug: campaign-target-audience
+        label: Target Audience
         valueType: string
-        inputType: text
-        placeholder: "contact@brand.com"
-        constraints: { format: email }
-      - slug: deal-value
-        label: "Deal Value (€)"
+        inputType: textarea
+      - slug: campaign-start-date
+        label: Start Date
+        valueType: date
+        inputType: date
+      - slug: campaign-end-date
+        label: End Date
+        valueType: date
+        inputType: date
+      - slug: campaign-budget
+        label: Budget
+        valueType: number
+        inputType: number
+      - slug: campaign-lead-count
+        label: Lead Count
         valueType: number
         inputType: number
-      - slug: payment-status
-        label: Payment Status
+      - slug: campaign-conversion-rate
+        label: Conversion Rate (%)
+        valueType: number
+        inputType: number
+      - slug: campaign-notes
+        label: Notes
         valueType: string
-        inputType: select
-        enumValues: ["Not Yet Due", "Invoice Sent", "Paid", "Overdue", "Disputed"]
-      - slug: contract-date
-        label: Contract Date
-        valueType: date
-      - slug: deliverable-deadline
-        label: Deliverable Deadline
-        valueType: date
-      - slug: exclusivity-end
-        label: Exclusivity End Date
-        valueType: date
-      - slug: deliverables
-        label: Deliverables
+        inputType: textarea
+
+  # ── Sponsor (shared ecosystem role — SSOT is foundation.yaml) ─────────────
+  # `scope: shared` dedups to the ONE pod-wide `sponsor` role seeded by
+  # foundation; provisioning grants THIS workspace access to it (SHARED profiles
+  # are grant-gated, so the reference is required — dropping it would leave the
+  # role invisible here). Shape matches foundation verbatim, so no property drift.
+  - slug: sponsor
+    displayName: Sponsor
+    icon: hand-coins
+    color: amber
+    description: A backer or sponsor of a program, round, or event.
+    scope: shared
+    profileKind: role
+    applicableKinds:
+      - person
+      - company
+    properties:
+      - slug: sponsorStatus
+        label: Status
         valueType: string
-        inputType: text
-        placeholder: "What exactly was promised? (2 posts, 1 newsletter mention, story, etc.)"
-      - slug: talking-points
-        label: Key Talking Points
+        inputType: select
+        enumValues:
+          - prospect
+          - active
+          - paused
+      - slug: sponsorType
+        label: Sponsor Type
         valueType: string
         inputType: text
-        placeholder: "Brand messages, required mentions, do-not-say list"
-      - slug: performance-notes
-        label: Performance Notes
+      - slug: notes
+        label: Notes
         valueType: string
-        inputType: text
-        placeholder: "What results did you report to the brand?"
-      - slug: sponsor-tags
-        label: Tags
-        valueType: array
+        inputType: textarea
 
+# CURATED views — the editorial spine
 views:
-  - name: Content Calendar
-    type: calendar
-    scopeProfileSlug: post
-    config:
-      dateField: publish-date
-      colorField: post-platform
-  - name: Post Pipeline
+  - name: Posts
+    slug: content-posts
     type: kanban
     scopeProfileSlug: post
-    config:
-      groupByField: post-status
-      cardFields: [post-format, post-platform, post-pillar, publish-date]
-  - name: All Posts
-    type: table
-    scopeProfileSlug: post
-    config:
-      visibleColumns: [post-status, post-format, post-platform, post-pillar, publish-date, engagement-score, post-reach]
-      defaultSort: { field: publish-date, direction: desc }
-      rowHeight: default
-  - name: Ideas Inbox
-    type: kanban
-    scopeProfileSlug: post
-    config:
-      groupByField: post-format
-      cardFields: [post-format, post-status, post-hook, post-tags]
-  - name: Repurposing Queue
-    type: table
-    scopeProfileSlug: post
-    config:
-      visibleColumns: [post-status, post-format, post-platform, post-pillar, repurposed-from, publish-date]
-      defaultSort: { field: post-platform, direction: asc }
-      rowHeight: default
-  - name: Content Graph
-    type: graph
-    scopeProfileSlugs: [post, campaign, pillar, newsletter, sponsor]
-    config:
-      layout: force
-      showRelations: true
-  - name: Campaigns
-    type: kanban
-    scopeProfileSlug: campaign
-    config:
-      groupByField: campaign-status
-      cardFields: [campaign-type, campaign-pillar, campaign-start, campaign-end, campaign-kpi]
-  - name: Campaign Timeline
-    type: timeline
-    scopeProfileSlug: campaign
-    config:
-      timeField: campaign-end
-      groupByField: campaign-status
+    groupBy: post-status
+    description: Content posts by status.
   - name: Pillars
-    type: table
+    slug: content-pillars
+    type: list
     scopeProfileSlug: pillar
-    config:
-      visibleColumns: [pillar-status, pillar-audience, pillar-goal, pillar-formats, posting-frequency, post-count-pillar, avg-engagement]
-      defaultSort: { field: pillar-status, direction: asc }
-      rowHeight: default
+    description: Content pillars — the recurring themes.
   - name: Platforms
+    slug: content-platforms
     type: table
     scopeProfileSlug: platform
-    config:
-      visibleColumns: [platform-type, platform-status, follower-count, follower-target, avg-engagement-rate, platform-posting-freq, last-post-date]
-      defaultSort: { field: follower-count, direction: desc }
-      rowHeight: default
-  - name: Newsletter Issues
-    type: table
-    scopeProfileSlug: newsletter
-    config:
-      visibleColumns: [newsletter-status, newsletter-series, issue-number, subject-line, send-date, subscriber-count, open-rate, click-rate, newsletter-sponsor]
-      defaultSort: { field: send-date, direction: desc }
-      rowHeight: default
-  - name: Newsletter Pipeline
+    description: Channels and their audience metrics.
+  - name: Newsletters
+    slug: content-newsletters
     type: kanban
     scopeProfileSlug: newsletter
-    config:
-      groupByField: newsletter-status
-      cardFields: [newsletter-series, issue-number, subject-line, send-date, newsletter-sponsor]
-  - name: Newsletter Calendar
-    type: calendar
-    scopeProfileSlug: newsletter
-    config:
-      dateField: send-date
-      colorField: newsletter-status
-  - name: Sponsor Tracker
-    type: kanban
-    scopeProfileSlug: sponsor
-    config:
-      groupByField: deal-status
-      cardFields: [sponsor-type, deal-value, deliverable-deadline, payment-status]
-  - name: Sponsors Table
-    type: table
-    scopeProfileSlug: sponsor
-    config:
-      visibleColumns: [deal-status, sponsor-type, contact-name, deal-value, payment-status, deliverable-deadline, exclusivity-end]
-      defaultSort: { field: deliverable-deadline, direction: asc }
-      rowHeight: default
-  - name: Sponsor Deadlines
-    type: calendar
-    scopeProfileSlug: sponsor
-    config:
-      dateField: deliverable-deadline
-      colorField: payment-status
-  - name: Post
-    type: bento
-    scopeProfileSlug: post
-    config:
-      layout: bento
-      blocks:
-        - id: post-header
-          kind: widget
-          widgetType: section-header
-          pos: { x: 0, y: 0, w: 12, h: 2 }
-          config: { title: Posts, icon: FileEdit, color: "#6366F1", profileSlug: post }
-        - id: post-count
-          kind: widget
-          widgetType: stat-card
-          pos: { x: 0, y: 2, w: 3, h: 3 }
-          config: { label: Total Posts, aggregation: count, profileSlug: post, color: "#6366F1" }
-        - id: post-pipeline
-          kind: view
-          viewName: Post Pipeline
-          pos: { x: 0, y: 9, w: 12, h: 8 }
-        - id: post-cal
-          kind: view
-          viewName: Content Calendar
-          pos: { x: 0, y: 19, w: 12, h: 8 }
-        - id: post-published
-          kind: widget
-          widgetType: entity-count
-          pos: { x: 3, y: 2, w: 3, h: 3 }
-          config: { profileSlug: post, label: Published, icon: Globe, filter: { status: published }, color: "#10B981" }
-        - id: post-drafts
-          kind: widget
-          widgetType: entity-count
-          pos: { x: 6, y: 2, w: 3, h: 3 }
-          config: { profileSlug: post, label: Drafts, icon: FileEdit, filter: { status: draft }, color: "#6B7280" }
-        - id: post-scheduled
-          kind: widget
-          widgetType: entity-count
-          pos: { x: 9, y: 2, w: 3, h: 3 }
-          config: { profileSlug: post, label: Scheduled, icon: Clock, filter: { status: scheduled }, color: "#F59E0B" }
-        - id: post-spotlight
-          kind: widget
-          widgetType: entity-spotlight
-          pos: { x: 0, y: 5, w: 5, h: 4 }
-          config: { profileSlug: post, seed: daily, layout: detail, subtitleField: platform, color: "#EC4899" }
-        - id: post-gallery
-          kind: widget
-          widgetType: entity-gallery
-          pos: { x: 5, y: 5, w: 7, h: 4 }
-          config: { profileSlug: post, coverField: thumbnail-url, title: Recent Posts, limit: 6 }
-      breakpoints:
-        lg: { cols: 12, rowHeight: 60, gap: 12 }
-        md: { cols: 10, rowHeight: 60, gap: 12 }
-        sm: { cols: 6, rowHeight: 60, gap: 12 }
-        xs: { cols: 4, rowHeight: 60, gap: 12 }
-        xxs: { cols: 2, rowHeight: 60, gap: 12 }
-  - name: Campaign
-    type: bento
-    scopeProfileSlug: campaign
-    config:
-      layout: bento
-      blocks:
-        - id: campaign-header
-          kind: widget
-          widgetType: section-header
-          pos: { x: 0, y: 0, w: 12, h: 2 }
-          config: { title: Campaigns, icon: Target, color: "#F59E0B", profileSlug: campaign }
-        - id: campaign-count
-          kind: widget
-          widgetType: stat-card
-          pos: { x: 0, y: 2, w: 3, h: 3 }
-          config: { label: Total Campaigns, aggregation: count, profileSlug: campaign, color: "#F59E0B" }
-        - id: campaign-board
-          kind: view
-          viewName: Campaigns
-          pos: { x: 0, y: 9, w: 12, h: 8 }
-        - id: campaign-timeline
-          kind: view
-          viewName: Campaign Timeline
-          pos: { x: 0, y: 19, w: 12, h: 8 }
-        - id: campaign-active
-          kind: widget
-          widgetType: entity-count
-          pos: { x: 3, y: 2, w: 3, h: 3 }
-          config: { profileSlug: campaign, label: Active, icon: Play, filter: { status: active }, color: "#10B981" }
-        - id: campaign-posts
-          kind: widget
-          widgetType: entity-count
-          pos: { x: 6, y: 2, w: 3, h: 3 }
-          config: { profileSlug: post, label: Campaign Posts, icon: FileText, color: "#EC4899" }
-        - id: campaign-spotlight
-          kind: widget
-          widgetType: entity-spotlight
-          pos: { x: 0, y: 5, w: 5, h: 4 }
-          config: { profileSlug: campaign, seed: daily, layout: detail, subtitleField: status, color: "#8B5CF6" }
-        - id: campaign-post-list
-          kind: widget
-          widgetType: entity-list
-          pos: { x: 5, y: 5, w: 7, h: 4 }
-          config: { profileSlug: post, title: Campaign Posts, limit: 6, variant: compact }
-      breakpoints:
-        lg: { cols: 12, rowHeight: 60, gap: 12 }
-        md: { cols: 10, rowHeight: 60, gap: 12 }
-        sm: { cols: 6, rowHeight: 60, gap: 12 }
-        xs: { cols: 4, rowHeight: 60, gap: 12 }
-        xxs: { cols: 2, rowHeight: 60, gap: 12 }
-  - name: Newsletter
-    type: bento
-    scopeProfileSlug: newsletter
-    config:
-      layout: bento
-      blocks:
-        - id: nl-header
-          kind: widget
-          widgetType: section-header
-          pos: { x: 0, y: 0, w: 12, h: 2 }
-          config: { title: Newsletters, icon: Mail, color: "#10B981", profileSlug: newsletter }
-        - id: nl-count
-          kind: widget
-          widgetType: stat-card
-          pos: { x: 0, y: 2, w: 3, h: 3 }
-          config: { label: Total Issues, aggregation: count, profileSlug: newsletter, color: "#10B981" }
-        - id: nl-pipeline
-          kind: view
-          viewName: Newsletter Pipeline
-          pos: { x: 0, y: 5, w: 12, h: 10 }
-        - id: nl-table
-          kind: view
-          viewName: Newsletter Issues
-          pos: { x: 0, y: 15, w: 12, h: 8 }
-      breakpoints:
-        lg: { cols: 12, rowHeight: 60, gap: 12 }
-        md: { cols: 10, rowHeight: 60, gap: 12 }
-        sm: { cols: 6, rowHeight: 60, gap: 12 }
-        xs: { cols: 4, rowHeight: 60, gap: 12 }
-        xxs: { cols: 2, rowHeight: 60, gap: 12 }
-  - name: Pillar
-    type: bento
-    scopeProfileSlug: pillar
-    config:
-      layout: bento
-      blocks:
-        - id: pillar-header
-          kind: widget
-          widgetType: section-header
-          pos: { x: 0, y: 0, w: 12, h: 2 }
-          config: { title: Content Pillars, icon: Layers, color: "#3B82F6", profileSlug: pillar }
-        - id: pillar-count
-          kind: widget
-          widgetType: stat-card
-          pos: { x: 0, y: 2, w: 3, h: 3 }
-          config: { label: Pillars, aggregation: count, profileSlug: pillar, color: "#3B82F6", icon: Layers }
-        - id: pillar-posts-count
-          kind: widget
-          widgetType: entity-count
-          pos: { x: 3, y: 2, w: 3, h: 3 }
-          config: { profileSlug: post, label: Posts in Pillar, icon: FileText, color: "#EC4899" }
-        - id: pillar-campaigns
-          kind: widget
-          widgetType: entity-count
-          pos: { x: 6, y: 2, w: 3, h: 3 }
-          config: { profileSlug: campaign, label: Campaigns, icon: Target, color: "#8B5CF6" }
-        - id: pillar-spotlight
-          kind: widget
-          widgetType: entity-spotlight
-          pos: { x: 0, y: 5, w: 6, h: 4 }
-          config: { profileSlug: pillar, seed: daily, layout: detail, color: "#3B82F6" }
-        - id: pillar-post-list
-          kind: widget
-          widgetType: entity-list
-          pos: { x: 6, y: 5, w: 6, h: 4 }
-          config: { profileSlug: post, title: Posts in this Pillar, limit: 6, variant: compact }
-        - id: pillar-table
-          kind: view
-          viewName: Pillars
-          pos: { x: 0, y: 9, w: 12, h: 8 }
+    groupBy: newsletter-status
+    description: Newsletter issues by status.
+
+# App reference — view-driven, no custom app (mirrors marketing.yaml)
+app:
+  kind: stored
+  cellKey: entity-detail
 
+# Layout config for browser sidebar
+layout:
+  pinnedApps: [dashboard, data]
+  defaultView: Posts
+  defaultApp: null
+  sidebarItems:
+    - kind: view
+      viewName: Posts
+      label: Posts
+      icon: file-edit
+    - kind: view
+      viewName: Pillars
+      label: Pillars
+      icon: columns
+    - kind: view
+      viewName: Platforms
+      label: Platforms
+      icon: share-2
+    - kind: view
+      viewName: Newsletters
+      label: Newsletters
+      icon: mail
+
+# Bento dashboard
+bento:
+  viewName: Posts
+  blocks:
+    - kind: view
+      viewName: Pillars
+      pos: { x: 0, y: 0, w: 6, h: 5 }
+    - kind: view
+      viewName: Newsletters
+      pos: { x: 6, y: 0, w: 6, h: 5 }
+
+# Editorial graph: connect posts to campaign / pillar / sponsor
 entityLinks:
-  - sourceProfileSlug: post
-    targetProfileSlug: pillar
-    type: under
   - sourceProfileSlug: post
     targetProfileSlug: campaign
-    type: part_of
+    type: part_of_campaign
+    label: Campaign
   - sourceProfileSlug: post
-    targetProfileSlug: sponsor
-    type: sponsored_by
-  - sourceProfileSlug: campaign
     targetProfileSlug: pillar
-    type: under
-  - sourceProfileSlug: newsletter
-    targetProfileSlug: campaign
-    type: part_of
-  - sourceProfileSlug: newsletter
-    targetProfileSlug: pillar
-    type: under
-  - sourceProfileSlug: newsletter
+    type: belongs_to_pillar
+    label: Pillar
+  - sourceProfileSlug: post
     targetProfileSlug: sponsor
     type: sponsored_by
-  - sourceProfileSlug: platform
-    targetProfileSlug: post
-    type: publishes
-
-displayTemplates:
-  - name: Post Card
-    description: "Content unit with status, format, platform, and performance metrics"
-    entityType: post
-    targetType: entity
-    isDefault: true
-    config:
-      layout:
-        structure:
-          header:
-            enabled: true
-            slots: [post-status, post-format, post-platform]
-            layout: horizontal
-            align: left
-          sidebar:
-            enabled: true
-            slots: [post-pillar, post-campaign, post-sponsor, publish-date]
-            position: right
-            width: 260px
-            layout: vertical
-          content:
-            enabled: true
-            slots: [post-hook, post-cta, engagement-score, post-reach]
-            layout: vertical
-        fieldMapping:
-          post-status:
-            slot: post-status
-            renderer: { type: badge, size: md }
-            showLabel: false
-            order: 1
-          post-format:
-            slot: post-format
-            renderer: { type: badge, variant: muted, size: sm }
-            showLabel: false
-            order: 2
-          post-platform:
-            slot: post-platform
-            renderer: { type: badge, variant: muted, size: sm }
-            showLabel: false
-            order: 3
-          engagement-score:
-            slot: engagement-score
-            renderer: { type: number, size: md }
-            label: Engagement
-            showLabel: true
-            order: 4
-          post-reach:
-            slot: post-reach
-            renderer: { type: number, size: md }
-            label: Reach
-            showLabel: true
-            order: 5
-          publish-date:
-            slot: publish-date
-            renderer: { type: date, format: relative }
-            order: 6
-      colors: { accent: "#8B5CF6" }
-      styling: { borderRadius: 10px }
-  - name: Sponsor Deal
-    description: "Brand deal with status, financials, and deliverable tracking"
-    entityType: sponsor
-    targetType: entity
-    isDefault: true
-    config:
-      layout:
-        structure:
-          header:
-            enabled: true
-            slots: [deal-status, deal-value]
-            layout: horizontal
-          sidebar:
-            enabled: true
-            slots: [payment-status, deliverable-deadline, exclusivity-end, contact-name, contact-email]
-            position: right
-            width: 280px
-            layout: vertical
-          content:
-            enabled: true
-            slots: [deliverables, talking-points, performance-notes]
-            layout: vertical
-        fieldMapping:
-          deal-status:
-            slot: deal-status
-            renderer: { type: badge, size: md }
-            showLabel: false
-            order: 1
-          deal-value:
-            slot: deal-value
-            renderer: { type: number, format: currency, size: lg }
-            label: Deal Value
-            order: 2
-          payment-status:
-            slot: payment-status
-            renderer: { type: badge, variant: muted, size: sm }
-            showLabel: true
-            order: 3
-          deliverable-deadline:
-            slot: deliverable-deadline
-            renderer: { type: date, format: relative }
-            label: Deadline
-            showLabel: true
-            order: 4
-      colors: { accent: "#F59E0B" }
-      styling: { borderRadius: 10px }
-  - name: Campaign Brief
-    description: "Campaign with timeline, KPI progress, and linked content"
-    entityType: campaign
-    targetType: entity
-    isDefault: true
-    config:
-      layout:
-        structure:
-          header:
-            enabled: true
-            slots: [campaign-status, campaign-type]
-            layout: horizontal
-          sidebar:
-            enabled: true
-            slots: [campaign-pillar, campaign-start, campaign-end, kpi-target, kpi-result, post-count]
-            position: right
-            width: 260px
-            layout: vertical
-          content:
-            enabled: true
-            slots: [campaign-goal, campaign-kpi, campaign-budget]
-            layout: vertical
-        fieldMapping:
-          campaign-status:
-            slot: campaign-status
-            renderer: { type: badge, size: md }
-            showLabel: false
-            order: 1
-          campaign-type:
-            slot: campaign-type
-            renderer: { type: badge, variant: muted, size: sm }
-            showLabel: false
-            order: 2
-          kpi-target:
-            slot: kpi-target
-            renderer: { type: number, size: md }
-            label: KPI Target
-            showLabel: true
-            order: 3
-          kpi-result:
-            slot: kpi-result
-            renderer: { type: number, size: md }
-            label: KPI Result
-            showLabel: true
-            order: 4
-          campaign-start:
-            slot: campaign-start
-            renderer: { type: date, format: relative }
-            label: Start
-            showLabel: true
-            order: 5
-          campaign-end:
-            slot: campaign-end
-            renderer: { type: date, format: relative }
-            label: End
-            showLabel: true
-            order: 6
-      colors: { accent: "#EC4899" }
-      styling: { borderRadius: 10px }
-  - name: Newsletter Issue
-    description: "Newsletter issue with open/click rates and sponsor linkage"
-    entityType: newsletter
-    targetType: entity
-    isDefault: true
-    config:
-      layout:
-        structure:
-          header:
-            enabled: true
-            slots: [newsletter-status, issue-number]
-            layout: horizontal
-          sidebar:
-            enabled: true
-            slots: [newsletter-sponsor, newsletter-campaign, newsletter-pillar, send-date, subscriber-count]
-            position: right
-            width: 260px
-            layout: vertical
-          content:
-            enabled: true
-            slots: [subject-line, preview-text, open-rate, click-rate]
-            layout: vertical
-        fieldMapping:
-          newsletter-status:
-            slot: newsletter-status
-            renderer: { type: badge, size: md }
-            showLabel: false
-            order: 1
-          open-rate:
-            slot: open-rate
-            renderer: { type: number, format: percent, size: md }
-            label: Open Rate
-            showLabel: true
-            order: 2
-          click-rate:
-            slot: click-rate
-            renderer: { type: number, format: percent, size: md }
-            label: Click Rate
-            showLabel: true
-            order: 3
-          send-date:
-            slot: send-date
-            renderer: { type: date, format: relative }
-            label: Sent
-            showLabel: true
-            order: 4
-      colors: { accent: "#14B8A6" }
-      styling: { borderRadius: 10px }
-
-# Home dashboard bento (maps from source bentoLayout — all blocks are widgets)
-bento:
-  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: 2, h: 2 }
-      config: { profileSlug: post, label: Posts }
-    - kind: widget
-      widgetType: entity-count
-      pos: { x: 2, y: 2, w: 2, h: 2 }
-      config: { profileSlug: campaign, label: Campaigns }
-    - kind: widget
-      widgetType: entity-count
-      pos: { x: 4, y: 2, w: 2, h: 2 }
-      config: { profileSlug: pillar, label: Pillars }
-    - kind: widget
-      widgetType: entity-count
-      pos: { x: 6, y: 2, w: 2, h: 2 }
-      config: { profileSlug: newsletter, label: Newsletters }
-    - kind: widget
-      widgetType: entity-count
-      pos: { x: 8, y: 2, w: 2, h: 2 }
-      config: { profileSlug: platform, label: Platforms }
-    - kind: widget
-      widgetType: entity-count
-      pos: { x: 10, y: 2, w: 2, h: 2 }
-      config: { profileSlug: sponsor, label: Sponsors }
-    - kind: widget
-      widgetType: entity-list
-      pos: { x: 0, y: 4, w: 5, h: 4 }
-      config: { profileSlug: post, title: Post Pipeline, limit: 8, variant: compact }
-    - kind: widget
-      widgetType: entity-list
-      pos: { x: 5, y: 4, w: 4, h: 4 }
-      config: { profileSlug: campaign, title: Active Campaigns, limit: 5, variant: detailed }
-    - kind: widget
-      widgetType: entity-list
-      pos: { x: 9, y: 4, w: 3, h: 4 }
-      config: { profileSlug: sponsor, title: Sponsor Tracker, limit: 5, variant: compact }
-    - kind: widget
-      widgetType: calendar
-      pos: { x: 0, y: 8, w: 5, h: 4 }
-    - kind: widget
-      widgetType: entity-list
-      pos: { x: 5, y: 8, w: 4, h: 4 }
-      config: { profileSlug: newsletter, title: Newsletter Issues, limit: 5, variant: compact }
-    - kind: widget
-      widgetType: feed
-      pos: { x: 9, y: 8, w: 3, h: 4 }
-
-# Per-profile entity detail bento layouts
-profileEntityBentoTemplates:
-  post:
-    blocks:
-      - id: post-eb-header
-        kind: widget
-        widgetType: entity-header
-        pos: { x: 0, y: 0, w: 12, h: 2 }
-      - id: post-eb-props
-        kind: widget
-        widgetType: entity-properties
-        pos: { x: 0, y: 2, w: 4, h: 8 }
-      - id: post-eb-content
-        kind: widget
-        widgetType: entity-content
-        pos: { x: 4, y: 2, w: 8, h: 4 }
-      - id: post-eb-similar
-        kind: widget
-        widgetType: entity-list
-        pos: { x: 4, y: 6, w: 8, h: 4 }
-        config: { profileSlug: post, title: Similar Posts, limit: 6, variant: compact }
-  campaign:
-    blocks:
-      - id: camp-eb-header
-        kind: widget
-        widgetType: entity-header
-        pos: { x: 0, y: 0, w: 12, h: 2 }
-      - id: camp-eb-props
-        kind: widget
-        widgetType: entity-properties
-        pos: { x: 0, y: 2, w: 4, h: 8 }
-      - id: camp-eb-posts
-        kind: widget
-        widgetType: entity-list
-        pos: { x: 4, y: 2, w: 8, h: 4 }
-        config: { profileSlug: post, title: Campaign Posts, limit: 8, variant: compact }
-      - id: camp-eb-content
-        kind: widget
-        widgetType: entity-content
-        pos: { x: 4, y: 6, w: 8, h: 4 }
-  pillar:
-    blocks:
-      - id: pillar-eb-header
-        kind: widget
-        widgetType: entity-header
-        pos: { x: 0, y: 0, w: 12, h: 2 }
-      - id: pillar-eb-props
-        kind: widget
-        widgetType: entity-properties
-        pos: { x: 0, y: 2, w: 4, h: 8 }
-      - id: pillar-eb-posts
-        kind: widget
-        widgetType: entity-list
-        pos: { x: 4, y: 2, w: 8, h: 8 }
-        config: { profileSlug: post, title: Posts in Pillar, limit: 10, variant: compact }
-
-# Capability templates to install on provisioning
-integrations:
-  - templateKey: nango-google
-
-# Session-template playbooks (none in source)
-playbooks: []
+    label: Sponsor
 
-# Per-workspace adaptive onboarding context — the "seasoned content strategist" framing
 onboarding:
-  goal: "Capture the user's brand voice, audience, content pillars, and publishing rhythm across channels — so the workspace reflects how they actually create and distribute content, not a generic calendar."
-  framing: "Act as a seasoned content strategist. Tease out their voice and positioning, who they're talking to, the recurring themes they own, the channels they publish on, and how often. Translate that into pillars, platforms, and a seeded content calendar."
+  goal: >
+    Stand up the editorial engine — the pillars you're known for, the platforms
+    you publish on, the cadence you can actually sustain, and a first post placed
+    in the system — so the workspace mirrors how you turn thinking into published
+    content, not a blank calendar.
+  framing: >
+    THE EDITOR-IN-CHIEF: Act as a seasoned content strategist who has grown owned
+    audiences from zero. Anchor everything on PILLARS — the two-to-four recurring
+    themes an audience comes to you for — because pillars are what make a content
+    engine compound instead of drift. Pull voice and identity from Brand and the
+    target audience from Foundation so every piece lands on-strategy. Push for a
+    cadence they can hold for a year, not a heroic month. Be concrete: real
+    platforms, real formats, a real first post — a fuzzy "I'll post more" helps
+    no one.
   expertise:
     starters:
       - >
-        Most creators over-index on one format and burn out. Propose 3–4 pillars
-        that mix TEACH (how it works), PROVE (customer/results), and PROVOKE
-        (point of view) — then adapt the mix to their niche. Don't ask for pillars
-        from a blank slate; offer a starting set and let them react.
+        Pillars before posts. A creator known for 2–4 clear themes compounds; one
+        posting about everything stays noise. Propose naming the pillars FIRST —
+        each with the audience it speaks to and the transformation it delivers —
+        then hang every post off one of them.
       - >
-        Better to own ONE channel consistently than be thin on four. If they list
-        many platforms, propose a primary channel + a cadence they can actually
-        sustain, and treat the rest as repurposing targets, not separate efforts.
+        Cadence you can sustain beats cadence that impresses. A weekly post held
+        for a year outperforms daily-for-three-weeks-then-silence. Propose a
+        realistic per-platform frequency and let the calendar enforce it, rather
+        than an ambitious number that collapses.
       - >
-        Every pillar should ladder to a business goal — awareness, trust, or
-        conversion. If a pillar is just "stuff we post", propose the job it should
-        do and tie it to a specific audience segment.
+        One idea, many formats — design for repurposing from the start. A single
+        strong thought becomes a thread, a short video, a newsletter section, and
+        a carousel. Propose the repurpose chain up front so one capture yields a
+        week of output, tracked via `repurposed-from`.
     blindSpots:
       - >
-        Distribution is the silent killer — great content nobody sees. If they
-        haven't said HOW each piece gets discovered (SEO, a platform's algorithm,
-        an email list, founder-led amplification), raise it before moving on.
+        No pillars = brand drift. If they list a dozen post ideas but can't name
+        the 2–4 themes underneath, that's the gap — surface it before filling the
+        calendar, because unpillared posting never builds an identity.
       - >
-        No repurposing plan = 5× the work for 1× the reach. If they treat each
-        post as one-and-done, propose a chain: one deep piece → clips → posts →
-        newsletter.
+        The owned-audience channel is the one most creators under-invest in. If
+        they're all-in on algorithmic platforms with no newsletter or list, name
+        it: the newsletter is the audience they actually own when a platform
+        changes the rules.
       - >
-        Pillars with no audience attached reach no one. Tie each pillar to a
-        specific segment — "content for everyone" is content for nobody.
+        Chasing every platform at once guarantees all of them stay shallow. If
+        they name five channels, push back: which ONE or two get real cadence and
+        attention now, and which are experiments?
     bar: >
-      The pillars + primary platform + cadence read like a system a small team
-      could actually run for 3 months without burning out — where every pillar has
-      a clear audience, a clear job, and a way to get discovered.
+      The workspace reads like a running publication: a handful of named pillars
+      each tied to an audience, the platforms actually committed to with a
+      sustainable cadence, an owned newsletter channel, and a first post placed in
+      a pillar — so a strategist could see at a glance what the brand is about,
+      where it publishes, and what ships next.
   collect:
     - profileSlug: pillar
-      what: "Their recurring content themes / brand voice — the lenses their audience knows them for, and who each speaks to"
+      what: The recurring themes you're known for — the 2–4 lenses your audience comes to you for, each with the segment it speaks to and the goal it serves.
       cardinality: few
-      keyFields: [title, pillar-audience, pillar-goal, posting-frequency]
+      keyFields: [pillar-status, pillar-audience, pillar-formats]
     - profileSlug: platform
-      what: "The channels they publish on and the rhythm of each"
+      what: The channels you actually publish on — the social accounts, newsletter, or podcast — with their status and the cadence you can hold.
       cardinality: several
-      keyFields: [title, platform-type, platform-posting-freq, follower-count]
+      keyFields: [platform-type, platform-status, platform-posting-freq]
     - profileSlug: post
-      what: "A few real or upcoming pieces to seed the content calendar"
+      what: A first post or two already in motion, each placed on a pillar and a platform at its true status (Idea through Published).
       cardinality: few
-      keyFields: [title, post-platform, post-pillar, publish-date]
-    - profileSlug: campaign
-      what: "Any active initiative or launch the content ladders up to"
-      cardinality: one
-      keyFields: [title, campaign-type, campaign-kpi]
+      keyFields: [post-status, post-format, post-platform]
   openingQuestions:
-    - "How would you describe your voice, and who are you really creating for?"
-    - "What are the 3-4 themes you keep coming back to — the things your audience knows you for?"
-    - "Which channels do you publish on, and how often on each?"
-  doneWhen: "Their pillars and primary platforms exist with a realistic cadence, and a handful of posts sit on the content calendar."
+    - "What are the 2–4 themes your audience comes to you for — the pillars everything you make ties back to?"
+    - "Which platforms do you actually publish on, and what cadence can you genuinely sustain on each?"
+    - "Do you run (or want) a newsletter — the audience you own outright — and what's the first post you'd place in the system?"
+  doneWhen: at least one pillar + one platform with a cadence + a first post placed on a pillar.