@synap-core/workspace-templates 0.2.2 → 0.3.0

package/src/content-os.yaml

@@ -677,397 +677,6 @@ entityLinks:
     targetProfileSlug: post
     type: publishes
 
-seedEntities:
-  - profileSlug: pillar
-    title: Data Sovereignty
-    properties:
-      pillar-status: Active
-      pillar-audience: "Founders, developers, and privacy-conscious professionals"
-      pillar-goal: "Position Synap as the infrastructure layer for personal data ownership — make the audience feel that sovereignty is not technical, it is a right"
-      pillar-formats: "Articles + Threads"
-      post-count-pillar: 12
-      avg-engagement: 340
-      top-post: "Why your data is not yours — and how to fix that"
-      posting-frequency: "2x / week"
-      pillar-tags: [sovereignty, synap, infrastructure]
-  - profileSlug: pillar
-    title: Product Building
-    properties:
-      pillar-status: Active
-      pillar-audience: "Indie hackers, founders, and early-stage builders"
-      pillar-goal: "Share the authentic journey of building Synap — decisions, mistakes, architecture choices — building trust through transparency"
-      pillar-formats: "Articles + Threads"
-      post-count-pillar: 8
-      avg-engagement: 210
-      top-post: "How we designed Synap's entity model from scratch"
-      posting-frequency: Weekly
-      pillar-tags: [building-in-public, synap, product]
-  - profileSlug: pillar
-    title: Creator Economy
-    properties:
-      pillar-status: Developing
-      pillar-audience: "Creators, solopreneurs, and content entrepreneurs"
-      pillar-goal: "Establish Synap's authority in the creator tools space — explain why the current tool stack is broken and what a sovereign alternative looks like"
-      pillar-formats: "Articles + Threads"
-      post-count-pillar: 4
-      avg-engagement: 180
-      posting-frequency: Weekly
-      pillar-tags: [creator-economy, content-os, tools]
-  - profileSlug: platform
-    title: LinkedIn
-    properties:
-      platform-status: Active
-      platform-url: "https://linkedin.com/in/your-handle"
-      follower-count: 3200
-      follower-target: 10000
-      avg-engagement-rate: 4.2
-      platform-posting-freq: "3x / week"
-      last-post-date: "2026-02-23"
-      platform-notes: "Long-form articles perform 3x better than short posts. Best engagement on Monday 8am and Thursday 6pm. CET. Professional tone, avoid jargon."
-      platform-tags: [linkedin, b2b, professional]
-  - profileSlug: platform
-    title: "Twitter / X"
-    properties:
-      platform-status: Active
-      platform-url: "https://x.com/your-handle"
-      follower-count: 1800
-      follower-target: 5000
-      avg-engagement-rate: 2.1
-      platform-posting-freq: Daily
-      last-post-date: "2026-02-23"
-      platform-notes: "Threads outperform single tweets 4:1. Tech and sovereignty threads go viral occasionally. Engage before posting — reply to 5 accounts before publishing."
-      platform-tags: [twitter, threads, tech]
-  - profileSlug: platform
-    title: Synap Newsletter
-    properties:
-      platform-type: Newsletter
-      platform-status: Building
-      follower-count: 420
-      follower-target: 2000
-      avg-engagement-rate: 38
-      platform-posting-freq: Weekly
-      last-post-date: "2026-02-17"
-      platform-notes: "35-40% open rate. Audience is tech-adjacent, values depth over brevity. Tuesdays at 7am CET performs best. Personal voice + one tactical insight + one product update."
-      platform-tags: [newsletter, owned, sovereign]
-  - profileSlug: campaign
-    title: "Synap Template Launch — Q1 2026"
-    properties:
-      campaign-status: Active
-      campaign-type: Product Launch
-      campaign-pillar: "ref:pillar:Product Building"
-      campaign-start: "2026-02-01"
-      campaign-end: "2026-03-31"
-      campaign-goal: "Drive 500 new workspace template activations and grow newsletter to 1,000 subscribers"
-      campaign-kpi: "Newsletter Sign-ups"
-      kpi-target: 500
-      post-count: 12
-      campaign-tags: [launch, templates, q1-2026]
-    content: |-
-      # Campaign Brief: Synap Template Launch — Q1 2026
-
-      ## Objective
-
-      Drive 500 template activations and 1,000 new newsletter subscribers by March 31, 2026. This is Synap's first public-facing product moment — the goal is not just installs but proof that the entity-first model resonates with creators who think in systems.
-
-      ## Target audience
-
-      Content creators and founder-creators managing multi-channel presence across 2+ platforms. They've tried Notion templates. They've paid for Buffer and Later. They feel the friction. They're ready for something built differently.
-
-      ## Content plan
-
-      12 posts across LinkedIn and Twitter/X over 8 weeks:
-
-      - **Week 1-2**: Problem framing — the creator stack is broken, context-switching cost, no unified operating record
-      - **Week 3-4**: Solution reveal — what a Content OS actually looks like, entity model walkthrough
-      - **Week 5-6**: Template demo — what's included, how seed data works, the graph view
-      - **Week 7-8**: Social proof + launch push — install CTA, newsletter integration, community feedback
-
-      ## KPIs
-
-      | Metric | Target |
-      |--------|--------|
-      | Template activations | 500 |
-      | Newsletter subs added | 1,000 |
-      | LinkedIn post avg reach | 8,000+ |
-      | Twitter thread avg impressions | 15,000+ |
-
-      ## Budget
-
-      €0 paid. Organic only. Brand deals (Mintlify, Anytype) offset production time.
-
-      ## Dependencies
-
-      - Template JSON validated and live in install flow
-      - Synap Newsletter Issue 13 dedicated to template walkthrough
-      - Mintlify sponsorship confirmed for Issue 12
-  - profileSlug: campaign
-    title: Data Sovereignty Series
-    properties:
-      campaign-status: Active
-      campaign-type: Editorial Series
-      campaign-pillar: "ref:pillar:Data Sovereignty"
-      campaign-start: "2026-01-15"
-      campaign-end: "2026-04-30"
-      campaign-goal: "Establish Synap's thought leadership in the sovereignty space — 10 long-form posts that define the narrative"
-      campaign-kpi: "Follower Growth"
-      kpi-target: 1000
-      post-count: 6
-      campaign-tags: [sovereignty, series, thought-leadership]
-  - profileSlug: post
-    title: "Why your subscriber list is not yours — and what to do about it"
-    properties:
-      post-status: Published
-      post-format: Article
-      post-platform: LinkedIn
-      post-pillar: "ref:pillar:Data Sovereignty"
-      post-campaign: "ref:campaign:Data Sovereignty Series"
-      publish-date: "2026-02-10"
-      post-hook: "You have 3,000 newsletter subscribers. If Substack disappears tomorrow, how many of them can you reach?"
-      post-cta: "Download our free guide to migrating your subscriber list to sovereign infrastructure"
-      post-tags: [sovereignty, newsletter, substack]
-      engagement-score: 520
-      post-reach: 12400
-    content: |-
-      # Why Your Subscriber List Is Not Yours — And What to Do About It
-
-      ## Core argument
-
-      When you build an audience on Substack, Mailchimp, or Beehiiv, you don't own the relationship. The platform does. They store the emails. They control deliverability. They set the terms of export. And if they change their pricing, get acquired, or shut down — your list goes with them.
-
-      This is not a hypothetical risk. It is the default architecture of every major newsletter platform.
-
-      ## What ownership actually means
-
-      Owning your subscriber list means three things:
-
-      1. **You hold the data.** The email addresses, open history, click behavior, and preferences live in infrastructure you control — not on a vendor's server.
-      2. **You choose the delivery layer.** You can switch from Mailchimp to Postmark to SES without asking permission and without migration friction.
-      3. **You set the rules.** GDPR compliance, data retention, deletion requests — you handle them directly, not through a third-party dashboard.
-
-      ## The sovereignty architecture
-
-      The alternative is treating your subscriber database as a first-class entity in your own data infrastructure. A record per subscriber. Properties for consent date, source, segment, engagement history. Relationships to the newsletter issues they opened, the posts that drove the sign-up.
-
-      This is what Synap enables with the Newsletter profile — your subscriber data lives in your pod, queryable by you, portable to any email provider, never held hostage.
-
-      ## The ask
-
-      Follow if you believe your audience relationship is a business asset — not a vendor dependency.
-
-      ---
-      *Published: LinkedIn · Data Sovereignty pillar · Data Sovereignty Series campaign*
-  - profileSlug: post
-    title: "Synap's entity model: why we ditched the database-first approach"
-    properties:
-      post-status: In Draft
-      post-format: Article
-      post-platform: LinkedIn
-      post-pillar: "ref:pillar:Product Building"
-      post-campaign: "ref:campaign:Synap Template Launch — Q1 2026"
-      publish-date: "2026-03-03"
-      post-hook: "Every other tool gives you a database. We built a network of entities — and the difference is everything."
-      post-cta: "Try the Second Brain template in Synap — free"
-      post-tags: [product, synap, architecture]
-  - profileSlug: post
-    title: "Thread: The creator tool stack is broken — here is why"
-    properties:
-      post-status: Scheduled
-      post-format: Thread
-      post-platform: "Twitter / X"
-      post-pillar: "ref:pillar:Creator Economy"
-      post-campaign: "ref:campaign:Synap Template Launch — Q1 2026"
-      publish-date: "2026-02-25"
-      post-hook: "I talked to 40 creators this month. Every single one uses 5+ tools that don't talk to each other. Here's what they all want:"
-      post-cta: "Follow for the full Creator Economy report"
-      post-tags: [creator-economy, tools, research]
-  - profileSlug: post
-    title: "Content OS template — what's included and why we built it"
-    properties:
-      post-status: Idea
-      post-format: Short Video
-      post-platform: LinkedIn
-      post-pillar: "ref:pillar:Product Building"
-      post-campaign: "ref:campaign:Synap Template Launch — Q1 2026"
-      post-hook: "We spent 3 weeks researching 8 creator tools before building Synap's Content OS template. Here is what we found."
-      post-tags: [content-os, templates, synap, research]
-  - profileSlug: post
-    title: "Data sovereignty is not a technical concept — it is a political one"
-    properties:
-      post-status: Idea
-      post-format: Article
-      post-platform: LinkedIn
-      post-pillar: "ref:pillar:Data Sovereignty"
-      post-campaign: "ref:campaign:Data Sovereignty Series"
-      post-hook: "The Sovereign Individual was published in 1997. It predicted exactly what is happening right now with AI and personal data."
-      post-tags: [sovereignty, philosophy, ai]
-  - profileSlug: post
-    title: "How Synap templates are seeded: the JSON-first approach"
-    properties:
-      post-status: Review
-      post-format: Article
-      post-platform: LinkedIn
-      post-pillar: "ref:pillar:Product Building"
-      post-campaign: "ref:campaign:Synap Template Launch — Q1 2026"
-      publish-date: "2026-03-10"
-      post-hook: "Most SaaS products show you an empty database on day one. Synap shows you a fully functional workspace. Here is how we do it."
-      post-cta: "Read the full technical deep-dive on our blog"
-      post-tags: [engineering, synap, templates, onboarding]
-  - profileSlug: newsletter
-    title: "The Sovereign Stack — Issue 12"
-    properties:
-      newsletter-status: Sent
-      newsletter-series: The Sovereign Stack
-      issue-number: 12
-      subject-line: "The 3 databases that own your content career (and how to escape)"
-      preview-text: "Your Substack list, your Buffer posts, your Notion brain..."
-      send-date: "2026-02-17"
-      subscriber-count: 390
-      open-rate: 39.2
-      click-rate: 6.8
-      newsletter-sponsor: "ref:sponsor:Mintlify"
-      newsletter-campaign: "ref:campaign:Data Sovereignty Series"
-      newsletter-pillar: "ref:pillar:Data Sovereignty"
-      newsletter-tags: [sovereignty, creator-tools, newsletter]
-  - profileSlug: newsletter
-    title: "The Sovereign Stack — Issue 13"
-    properties:
-      newsletter-status: Scheduled
-      newsletter-series: The Sovereign Stack
-      issue-number: 13
-      subject-line: "Inside Synap's Content OS template — what we built and why"
-      preview-text: "6 profiles, 16 views, 1 relational graph you own forever"
-      send-date: "2026-02-24"
-      newsletter-campaign: "ref:campaign:Synap Template Launch — Q1 2026"
-      newsletter-pillar: "ref:pillar:Product Building"
-      newsletter-tags: [content-os, templates, synap]
-  - profileSlug: newsletter
-    title: "The Sovereign Stack — Issue 14"
-    properties:
-      newsletter-status: Drafting
-      newsletter-series: The Sovereign Stack
-      issue-number: 14
-      subject-line: "Why we picked Ghost over Substack (and what it cost us)"
-      preview-text: "Honest numbers: subscriber growth, open rates, and the SEO truth"
-      send-date: "2026-03-03"
-      newsletter-pillar: "ref:pillar:Data Sovereignty"
-      newsletter-tags: [ghost, substack, sovereignty, newsletter]
-      newsletter-campaign: "ref:campaign:Data Sovereignty Series"
-  - profileSlug: sponsor
-    title: Mintlify
-    properties:
-      deal-status: Active
-      sponsor-type: Newsletter Sponsorship
-      contact-name: Alex Chen
-      contact-email: "alex@mintlify.com"
-      deal-value: 800
-      payment-status: Invoice Sent
-      contract-date: "2026-02-10"
-      deliverable-deadline: "2026-02-28"
-      exclusivity-end: "2026-03-15"
-      deliverables: "1 newsletter mention in Issue 12 (primary placement, 80–100 words). 1 LinkedIn post tagging Mintlify. Approved copy to be provided by sponsor."
-      talking-points: "Mintlify writes beautiful docs from your codebase. For developer-facing teams. Mention the GitHub integration."
-      performance-notes: "Issue 12: 39.2% open rate, 6.8% click rate. Sponsor link received 47 clicks. Will share screenshot report."
-      sponsor-tags: [developer-tools, newsletter, q1-2026]
-    content: |-
-      # Sponsor Brief: Mintlify — Issue 12
-
-      ## Deal summary
-
-      - **Format**: Primary newsletter placement, Issue 12 (The Sovereign Stack)
-      - **Value**: €800
-      - **Deliverables**: 1 newsletter mention (80-100 words, primary placement) + 1 LinkedIn post tagging Mintlify
-      - **Exclusivity**: No competing dev-tool sponsors until March 15, 2026
-      - **Payment**: Invoice sent Feb 17 — awaiting transfer
-
-      ## Approved copy (newsletter)
-
-      Mintlify builds documentation that actually gets read. If you're a developer or building developer-facing tools, Mintlify generates beautiful docs directly from your codebase — with GitHub integration, versioning, and AI-powered search. Worth 10 minutes to see what your docs could look like.
-
-      ## Performance report (to send)
-
-      Issue 12 stats to share with Alex:
-      - Open rate: 39.2% (industry avg ~22%)
-      - Click rate: 6.8%
-      - Sponsor link clicks: 47
-      - Screenshot attached in follow-up email
-
-      ## Notes
-
-      Alex Chen is responsive on email. They're considering a Q2 campaign (3 issues). Keep performance data clean and send within 48h of issue send. Relationship worth nurturing — philosophically aligned audience.
-  - profileSlug: sponsor
-    title: Anytype
-    properties:
-      deal-status: Prospecting
-      sponsor-type: Social Post
-      contact-name: Pavel K.
-      deal-value: 600
-      payment-status: Not Yet Due
-      deliverables: "1 LinkedIn post (honest review format). 1 Twitter thread. Not exclusive."
-      talking-points: "Anytype is open-source, local-first, object-based PKM. Philosophically aligned with Synap audience."
-      sponsor-tags: [pkm, local-first, sovereignty]
-
-suggestedRelations:
-  - sourceRef: "post:Why your subscriber list is not yours — and what to do about it"
-    targetRef: "campaign:Data Sovereignty Series"
-    type: belongs_to_project
-  - sourceRef: "post:Synap's entity model: why we ditched the database-first approach"
-    targetRef: "campaign:Synap Template Launch — Q1 2026"
-    type: belongs_to_project
-  - sourceRef: "post:Thread: The creator tool stack is broken — here is why"
-    targetRef: "campaign:Synap Template Launch — Q1 2026"
-    type: belongs_to_project
-  - sourceRef: "post:Content OS template — what's included and why we built it"
-    targetRef: "campaign:Synap Template Launch — Q1 2026"
-    type: belongs_to_project
-  - sourceRef: "post:Data sovereignty is not a technical concept — it is a political one"
-    targetRef: "campaign:Data Sovereignty Series"
-    type: belongs_to_project
-  - sourceRef: "post:How Synap templates are seeded: the JSON-first approach"
-    targetRef: "campaign:Synap Template Launch — Q1 2026"
-    type: belongs_to_project
-  - sourceRef: "post:Why your subscriber list is not yours — and what to do about it"
-    targetRef: "pillar:Data Sovereignty"
-    type: relates_to
-  - sourceRef: "post:Synap's entity model: why we ditched the database-first approach"
-    targetRef: "pillar:Product Building"
-    type: relates_to
-  - sourceRef: "post:Thread: The creator tool stack is broken — here is why"
-    targetRef: "pillar:Creator Economy"
-    type: relates_to
-  - sourceRef: "post:Content OS template — what's included and why we built it"
-    targetRef: "pillar:Product Building"
-    type: relates_to
-  - sourceRef: "post:Data sovereignty is not a technical concept — it is a political one"
-    targetRef: "pillar:Data Sovereignty"
-    type: relates_to
-  - sourceRef: "post:How Synap templates are seeded: the JSON-first approach"
-    targetRef: "pillar:Product Building"
-    type: relates_to
-  - sourceRef: "newsletter:The Sovereign Stack — Issue 12"
-    targetRef: "campaign:Data Sovereignty Series"
-    type: belongs_to_project
-  - sourceRef: "newsletter:The Sovereign Stack — Issue 13"
-    targetRef: "campaign:Synap Template Launch — Q1 2026"
-    type: belongs_to_project
-  - sourceRef: "newsletter:The Sovereign Stack — Issue 12"
-    targetRef: "pillar:Data Sovereignty"
-    type: relates_to
-  - sourceRef: "newsletter:The Sovereign Stack — Issue 13"
-    targetRef: "pillar:Product Building"
-    type: relates_to
-  - sourceRef: "newsletter:The Sovereign Stack — Issue 14"
-    targetRef: "pillar:Data Sovereignty"
-    type: relates_to
-  - sourceRef: "newsletter:The Sovereign Stack — Issue 12"
-    targetRef: "sponsor:Mintlify"
-    type: relates_to
-  - sourceRef: "campaign:Data Sovereignty Series"
-    targetRef: "pillar:Data Sovereignty"
-    type: relates_to
-  - sourceRef: "campaign:Synap Template Launch — Q1 2026"
-    targetRef: "pillar:Product Building"
-    type: relates_to
-
 displayTemplates:
   - name: Post Card
     description: "Content unit with status, format, platform, and performance metrics"

package/src/content-studio.yaml

@@ -288,25 +288,35 @@ entityLinks:
     type: used_in
     label: Composition
 
-seedEntities:
-  - profileSlug: content-template
-    title: Instagram Reel — Fast
-    properties:
-      template-kind: hyperframes
-      aspect-ratio: "9:16"
-      template-status: approved
-      template-config: '{"mode":"fast","pipeline":["script","hyperframes","render"],"description":"Quick social cut: write a script, get HyperFrames HTML, browser-capture to MP4."}'
-  - profileSlug: content-template
-    title: Product Demo — Quality
-    properties:
-      template-kind: hybrid
-      aspect-ratio: "16:9"
-      template-status: approved
-      template-config: '{"mode":"quality","pipeline":["script","hyperframes","remotion","render"],"description":"Premium product video: HyperFrames design exploration → Remotion production render with springs + audio sync."}'
-  - profileSlug: content-template
-    title: Data Recap — Data-Driven
-    properties:
-      template-kind: remotion
-      aspect-ratio: "16:9"
-      template-status: approved
-      template-config: '{"mode":"data","pipeline":["data","remotion","render"],"description":"Synap-powered: pull entities via calculateMetadata(), animate charts, render weekly recap."}'
+onboarding:
+  goal: Capture how you actually produce video and motion content — your real pipelines, your reusable templates, and the assets you cut from — so the studio mirrors your production line, not a generic setup.
+  framing: >
+    THE PRODUCER: Act as a seasoned motion/video production lead who has shipped
+    thousands of frames. This is a HyperFrames/Remotion render pipeline, NOT a
+    publishing calendar — anchor on how work gets MADE: formats, aspect ratios,
+    durations, and the templates that make output repeatable. Push for the shows
+    and series they actually run, not one-off ideas. Pull voice and visual identity
+    from Brand and target audience from Foundation so every piece lands on-brand.
+    Be concrete about specs; a fuzzy "we make videos" helps no one.
+  collect:
+    - profileSlug: content-pipeline
+      what: The recurring productions you run — the shows, series, or content lines that generate output on a cadence (e.g. weekly reels, product demos, explainer drops).
+      cardinality: few
+      keyFields: [pipeline-kind, pipeline-platform, pipeline-mode]
+    - profileSlug: content-template
+      what: The reusable HyperFrames/Remotion templates that make production repeatable — your title cards, lower-thirds, intros/outros, and full-video shells. These carry Brand voice and visual identity into every render.
+      cardinality: several
+      keyFields: [template-kind, aspect-ratio, template-status]
+    - profileSlug: content-asset
+      what: The asset sources you cut from — brand footage, stock, audio/music beds, and fonts. Note whether each comes from Brand, is uploaded, or is generated.
+      cardinality: several
+      keyFields: [asset-kind, source-kind, source-url]
+    - profileSlug: content-composition
+      what: Any compositions already in flight — specific videos being built, with their aspect ratio and duration, tied back to a pipeline.
+      cardinality: few
+      keyFields: [aspect-ratio, duration-seconds, pipeline-ref]
+  openingQuestions:
+    - "What do you actually produce on repeat — the shows or series, and for which platforms and aspect ratios?"
+    - "Which motion templates do you reuse every time — intros, lower-thirds, outros — and are they HyperFrames, Remotion, or hybrid?"
+    - "Where do your assets come from — Brand footage and fonts, uploaded clips, or AI-generated — and where do you pull music from?"
+  doneWhen: at least one pipeline + one reusable template + one asset source captured.