@synap-core/workspace-templates 0.6.0 → 0.6.2

package/src/content-os.yaml

@@ -0,0 +1,567 @@
+# Content OS workspace template
+# 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: "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, 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
+  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-os
+  visibility: pod_visible
+  capabilities:
+    - content.editorial
+    - content.pillars
+    - content.calendar
+    - content.newsletter
+  sourceRoles:
+    brand: consumer
+    marketing: consumer
+    content: provider
+
+profiles:
+  - slug: post
+    displayName: Post
+    icon: file-edit
+    color: "#6366F1"
+    description: "Your atomic content unit. One idea, multiple platform formats — tracked from spark to publication."
+    scope: WORKSPACE
+    properties:
+      - slug: post-status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: ["Idea", "Briefed", "In Draft", "Review", "Scheduled", "Published", "Archived"]
+      - slug: post-format
+        label: Format
+        valueType: string
+        inputType: select
+        enumValues: ["Article", "Thread", "Short Video", "Long Video", "Carousel", "Image Post", "Story", "Newsletter Section", "Podcast Episode", "Other"]
+      - slug: post-platform
+        label: Platform
+        valueType: string
+        inputType: select
+        enumValues: ["LinkedIn", "Instagram", "TikTok", "YouTube", "Twitter / X", "Threads", "Bluesky", "Newsletter", "Podcast", "Blog", "Other"]
+      - 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
+      - slug: post-hook
+        label: "Hook / Headline"
+        valueType: string
+        inputType: text
+        placeholder: "Opening line or headline that stops the scroll"
+      - slug: post-cta
+        label: CTA
+        valueType: string
+        inputType: text
+        placeholder: "What should the audience do?"
+      - slug: post-tags
+        label: Tags
+        valueType: array
+      - slug: engagement-score
+        label: Engagement Score
+        valueType: number
+        inputType: number
+        placeholder: "Numeric performance metric (likes + comments + shares)"
+      - slug: post-reach
+        label: "Reach / Views"
+        valueType: number
+        inputType: number
+      - slug: repurposed-from
+        label: Repurposed From
+        valueType: string
+        inputType: text
+        placeholder: "Source post or content this was adapted from"
+      - slug: post-url
+        label: Published URL
+        valueType: string
+        inputType: text
+        placeholder: "https://..."
+        constraints: { format: url }
+
+  - slug: pillar
+    displayName: Pillar
+    icon: columns
+    color: "#8B5CF6"
+    description: "A recurring content theme — the lens through which your audience knows you. The organizing principle of your brand."
+    scope: WORKSPACE
+    properties:
+      - slug: pillar-status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: ["Active", "Developing", "Paused", "Retired"]
+      - slug: pillar-audience
+        label: Audience Segment
+        valueType: string
+        inputType: text
+        placeholder: "Who does this pillar speak to?"
+      - slug: pillar-goal
+        label: Audience Goal
+        valueType: string
+        inputType: text
+        placeholder: "What should the audience think, feel, or do after consuming this pillar?"
+      - slug: pillar-formats
+        label: Primary Formats
+        valueType: string
+        inputType: select
+        enumValues: ["Articles + Threads", "Short Video", "Long Video", "Newsletter", "Podcast", "Carousel", "Mixed"]
+      - slug: post-count-pillar
+        label: Total Posts Published
+        valueType: number
+        inputType: number
+      - slug: avg-engagement
+        label: Avg Engagement Score
+        valueType: number
+        inputType: number
+      - slug: top-post
+        label: Top Performing Post
+        valueType: string
+        inputType: text
+        placeholder: "Title of best performing post in this pillar"
+      - slug: posting-frequency
+        label: Target Frequency
+        valueType: string
+        inputType: select
+        enumValues: ["Daily", "3x / week", "2x / week", "Weekly", "Bi-weekly", "Monthly", "Ad hoc"]
+      - slug: pillar-tags
+        label: Tags
+        valueType: array
+
+  - slug: platform
+    displayName: Platform
+    icon: share-2
+    color: "#06B6D4"
+    description: "A social account, newsletter publication, or podcast channel. Each platform has its own audience metrics and publishing rhythm."
+    scope: WORKSPACE
+    properties:
+      - slug: platform-type
+        label: Type
+        valueType: string
+        inputType: select
+        enumValues: ["LinkedIn", "Instagram", "TikTok", "YouTube", "Twitter / X", "Threads", "Bluesky", "Newsletter", "Podcast", "Blog / Website", "Other"]
+      - slug: platform-status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: ["Active", "Building", "Maintenance Mode", "Inactive"]
+      - slug: platform-url
+        label: Profile URL
+        valueType: string
+        inputType: text
+        placeholder: "https://..."
+        constraints: { format: url }
+      - slug: follower-count
+        label: "Follower / Subscriber Count"
+        valueType: number
+        inputType: number
+      - slug: follower-target
+        label: Target Count
+        valueType: number
+        inputType: number
+      - slug: avg-engagement-rate
+        label: "Avg Engagement Rate (%)"
+        valueType: number
+        inputType: number
+      - slug: platform-posting-freq
+        label: Posting Frequency
+        valueType: string
+        inputType: select
+        enumValues: ["Daily", "3x / week", "2x / week", "Weekly", "Bi-weekly", "Monthly", "As Needed"]
+      - slug: last-post-date
+        label: Last Post Date
+        valueType: date
+      - slug: platform-notes
+        label: Notes
+        valueType: string
+        inputType: text
+        placeholder: "What works here? Tone, format, best times..."
+      - slug: platform-tags
+        label: Tags
+        valueType: array
+
+  - slug: newsletter
+    displayName: Newsletter
+    icon: mail
+    color: "#10B981"
+    description: "A newsletter issue — your direct channel to an owned audience. No algorithm, no platform fee, no intermediary."
+    scope: WORKSPACE
+    properties:
+      - slug: newsletter-status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: ["Idea", "Drafting", "Editing", "Scheduled", "Sent", "Archived"]
+      - slug: newsletter-series
+        label: Series
+        valueType: string
+        inputType: text
+        placeholder: "Which newsletter series is this issue part of?"
+      - slug: issue-number
+        label: Issue Number
+        valueType: number
+        inputType: number
+      - slug: subject-line
+        label: Subject Line
+        valueType: string
+        inputType: text
+        placeholder: "The subject line — your most important copy"
+      - slug: preview-text
+        label: Preview Text
+        valueType: string
+        inputType: text
+        placeholder: "45-character preview shown in inbox (after subject)"
+      - slug: send-date
+        label: Send Date
+        valueType: date
+      - slug: subscriber-count
+        label: Subscriber Count at Send
+        valueType: number
+        inputType: number
+      - slug: open-rate
+        label: "Open Rate (%)"
+        valueType: number
+        inputType: number
+      - slug: click-rate
+        label: "Click Rate (%)"
+        valueType: number
+        inputType: number
+      - 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
+
+  # ── 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: campaign-status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [planning, active, paused, completed, cancelled]
+        constraints: { defaultValue: planning }
+      - slug: campaign-channel
+        label: Channel
+        valueType: string
+        inputType: select
+        enumValues: [email, social, event, content, partnership, paid, organic, other]
+      - slug: campaign-goal
+        label: Goal
+        valueType: string
+        inputType: textarea
+      - slug: campaign-target-audience
+        label: Target Audience
+        valueType: string
+        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: campaign-conversion-rate
+        label: Conversion Rate (%)
+        valueType: number
+        inputType: number
+      - slug: campaign-notes
+        label: Notes
+        valueType: string
+        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: select
+        enumValues:
+          - prospect
+          - active
+          - paused
+      - slug: sponsorType
+        label: Sponsor Type
+        valueType: string
+        inputType: text
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+# CURATED views — the editorial spine
+views:
+  - name: Posts
+    slug: content-posts
+    type: kanban
+    scopeProfileSlug: post
+    groupBy: post-status
+    description: Content posts by status.
+  - name: Pillars
+    slug: content-pillars
+    type: list
+    scopeProfileSlug: pillar
+    description: Content pillars — the recurring themes.
+  - name: Platforms
+    slug: content-platforms
+    type: table
+    scopeProfileSlug: platform
+    description: Channels and their audience metrics.
+  - name: Newsletters
+    slug: content-newsletters
+    type: kanban
+    scopeProfileSlug: newsletter
+    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: campaign
+    type: part_of_campaign
+    label: Campaign
+  - sourceProfileSlug: post
+    targetProfileSlug: pillar
+    type: belongs_to_pillar
+    label: Pillar
+  - sourceProfileSlug: post
+    targetProfileSlug: sponsor
+    type: sponsored_by
+    label: Sponsor
+
+# Playbooks — session templates seeded with the workspace.
+# `subjectProfile` binds this playbook to the `post` kind so the Capture → Session
+# matcher (playbooks.subject_profile->>'profileSlug') can offer it when a post is
+# captured. The captured post is passed as the `post` entity param and substituted
+# into the goalTemplate; the agent carries it from raw idea to a scheduled draft.
+playbooks:
+  - name: Produce Content
+    description: Take a captured post idea and carry it from spark to a scheduled, platform-ready draft.
+    goalTemplate: >-
+      Produce content for {platform} from this idea ({post}). Take the raw idea,
+      shape it into a {format} draft with a scroll-stopping hook and a clear CTA,
+      keep it aligned to the post's pillar and the operator's brand voice, then
+      move it to Scheduled with a publish date.
+    subjectProfile:
+      profileSlug: post
+    params:
+      - { name: post, type: entity, label: Post, required: true }
+      - { name: platform, type: text, label: Platform, required: true }
+      - { name: format, type: text, label: Format }
+    executor: is-agent
+    status: active
+
+onboarding:
+  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:
+      - >
+        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.
+      - >
+        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.
+      - >
+        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:
+      - >
+        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.
+      - >
+        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.
+      - >
+        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 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: 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: [pillar-status, pillar-audience, pillar-formats]
+    - profileSlug: platform
+      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: [platform-type, platform-status, platform-posting-freq]
+    - profileSlug: post
+      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: [post-status, post-format, post-platform]
+  openingQuestions:
+    - "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.