@synap-core/workspace-templates 0.2.2 → 0.4.0

package/src/project-management.yaml

@@ -643,384 +643,6 @@ displayTemplates:
       colors:
         accent: "#D97706"
 
-seedEntities:
-  - profileSlug: person
-    title: Antoine
-    properties:
-      person-role: Founder
-      person-email: antoine@synap.io
-      person-focus: Synap template stack and PM OS launch
-      person-okr-owner: true
-      person-availability: 40
-      person-timezone: Europe/Paris
-
-  - profileSlug: person
-    title: Léa Moreau
-    properties:
-      person-role: Engineer
-      person-email: lea@synap.io
-      person-focus: Display template rendering and entity graph view
-      person-okr-owner: false
-      person-availability: 35
-      person-timezone: Europe/Paris
-
-  - profileSlug: okr
-    title: "Launch Synap PM OS — Q1 2026"
-    properties:
-      okr-status: Active
-      okr-quarter: "Q1 2026"
-      okr-owner: "ref:person:Antoine"
-      okr-type: Company
-      kr1-label: Template validated and live in staging
-      kr1-target: 1
-      kr1-current: 0
-      kr1-unit: milestone
-      kr2-label: Onboarding guide published (1,000 words min)
-      kr2-target: 1
-      kr2-current: 0
-      kr2-unit: doc
-      kr3-label: Demo video recorded and embedded on landing page
-      kr3-target: 1
-      kr3-current: 0
-      kr3-unit: video
-      okr-confidence: High
-      okr-review-date: "2026-03-28"
-    content: |
-      # OKR Brief: Launch Synap PM OS — Q1 2026
-
-      ## Objective
-      Ship a fully functional, entity-first project management workspace template that demonstrates the core Synap thesis: goals, projects, sprints, and tasks as a connected relationship graph — not siloed tools.
-
-      ## Why This Matters
-      The PM software market is $9.76B and growing at 15.4% CAGR, but every major tool treats OKRs and task execution as separate concerns. Asana Goals, Monday OKR boards, ClickUp Goals — all bolted on. None architecturally connects an Objective to the tasks that should advance it.
-
-      Synap PM OS is the proof of concept that our entity model solves this. Before we can tell founders and small teams that Synap replaces their PM stack, we need to show them what that looks like at the template layer.
-
-      ## Success Definition
-      By March 31, 2026:
-      - Template JSON validated and live in staging with all 5 profiles, 15 views, 4 display templates, and 26 seed entity relations
-      - Onboarding guide published: covers OKR setup, sprint configuration, and the relationship graph demo in under 15 minutes of reading
-      - Demo video (3-5 minutes) showing the OKR → Project → Task traversal from the entity card and the relationship graph view
-
-      ## Key Risks
-      - Graph view rendering performance on entity-dense workspaces needs testing before public launch
-      - OKR progress bar computation logic (KR current / KR target) must be validated against edge cases (zero targets, >100% completion)
-
-      ## Dependencies
-      - Display template renderer must support progress-bar for numeric fields before template goes live
-      - Seed entity relation pipeline must resolve `ref:` values for all 5 profiles
-
-  - profileSlug: okr
-    title: "Grow Template Activations — Q1 2026"
-    properties:
-      okr-status: Active
-      okr-quarter: "Q1 2026"
-      okr-owner: "ref:person:Antoine"
-      okr-type: Company
-      kr1-label: Template activations (installs)
-      kr1-target: 500
-      kr1-current: 0
-      kr1-unit: activations
-      kr2-label: Newsletter subscribers from PM OS launch campaign
-      kr2-target: 300
-      kr2-current: 0
-      kr2-unit: subscribers
-      kr3-label: LinkedIn post impressions on PM OS launch thread
-      kr3-target: 15000
-      kr3-current: 0
-      kr3-unit: impressions
-      okr-confidence: Medium
-      okr-review-date: "2026-03-28"
-
-  - profileSlug: project
-    title: Build PM OS Template
-    properties:
-      project-status: In Progress
-      project-priority: Critical
-      project-linked-okr: "ref:okr:Launch Synap PM OS — Q1 2026"
-      project-owner: "ref:person:Antoine"
-      project-start: "2026-02-17"
-      project-deadline: "2026-03-07"
-      project-milestone: Template JSON validated in staging
-      project-health: Green
-      project-effort: 12
-      project-tags: [Product, Engineering]
-      project-outcome: "A fully functional PM OS workspace template demonstrating the OKR → Project → Task entity graph"
-    content: |
-      # Project Brief: Build PM OS Template
-
-      ## Scope
-      Design, build, and validate the Synap PM OS workspace template JSON. This includes 5 entity profiles (OKR, Project, Task, Sprint, Person), 15 views, a 12-widget dashboard, 4 display templates, 19 seed entities, and 26 suggested relations.
-
-      ## Deliverables
-      1. **pm-os-template.json** — Complete workspace template with all profiles, views, dashboard, display templates, seed entities, and suggestedRelations
-      2. **Validation report** — Confirms all ref: values resolve correctly, all entity_id properties point to valid targetProfileSlugs, all views reference existing profiles
-      3. **Graph demo check** — Confirms the OKR → Project → Task traversal is visible in the relationship graph view from both the OKR entity card and the Task entity card
-
-      ## Architecture Decisions
-      - **5 profiles, not 6**: Milestone considered as a sixth profile but folded into Project as a property to reduce complexity for first-time users. Can be promoted to a full profile in v2.
-      - **Sprint as first-class entity**: Unlike Asana/Monday which treat sprints as a view filter or folder, Sprint is a proper entity with velocity tracking and retrospective document content.
-      - **OKR progress via three KR fields**: Rather than a dynamic KR sub-entity (complex to render), KR1/KR2/KR3 are direct properties with label + target + current + unit. Keeps the OKR card readable without a sub-table.
-
-      ## Timeline
-      - Week 1 (Feb 17–21): Profile schemas and property definitions
-      - Week 2 (Feb 24–28): Views, dashboard, display templates
-      - Week 3 (Mar 2–7): Seed entities, relations, content, validation
-
-  - profileSlug: project
-    title: Publish PM OS Onboarding Guide
-    properties:
-      project-status: Backlog
-      project-priority: High
-      project-linked-okr: "ref:okr:Launch Synap PM OS — Q1 2026"
-      project-owner: "ref:person:Antoine"
-      project-start: "2026-03-03"
-      project-deadline: "2026-03-21"
-      project-milestone: Guide live at synap.io/templates/pm-os
-      project-health: Green
-      project-effort: 4
-      project-tags: [Product, Marketing]
-      project-outcome: Founders and small teams can install and configure the PM OS in under 15 minutes using the guide
-
-  - profileSlug: project
-    title: PM OS Distribution Campaign
-    properties:
-      project-status: Planning
-      project-priority: High
-      project-linked-okr: "ref:okr:Grow Template Activations — Q1 2026"
-      project-owner: "ref:person:Antoine"
-      project-start: "2026-03-10"
-      project-deadline: "2026-03-31"
-      project-milestone: Launch LinkedIn thread + Newsletter Issue 14
-      project-health: Green
-      project-effort: 5
-      project-tags: [Marketing]
-      project-outcome: 500 template activations and 300 newsletter subs from PM OS launch
-
-  - profileSlug: project
-    title: Waitlist Landing Page
-    properties:
-      project-status: Planning
-      project-priority: Medium
-      project-linked-okr: "ref:okr:Grow Template Activations — Q1 2026"
-      project-owner: "ref:person:Antoine"
-      project-start: "2026-03-01"
-      project-deadline: "2026-03-14"
-      project-milestone: Landing page live with waitlist form
-      project-health: Yellow
-      project-effort: 3
-      project-tags: [Product, Marketing]
-      project-outcome: Dedicated landing page for PM OS with activation count display and waitlist CTA
-
-  - profileSlug: sprint
-    title: "Sprint 3 — Content OS & Second Brain Final"
-    properties:
-      sprint-status: Completed
-      sprint-number: 3
-      sprint-start: "2026-02-03"
-      sprint-end: "2026-02-14"
-      sprint-goal: "Ship Content OS and Second Brain templates with full schema upgrade (entity_id, relations, displayTemplates, content)"
-      sprint-capacity: 60
-      sprint-velocity: 58
-      sprint-task-count: 14
-      sprint-completed-count: 13
-    content: |
-      # Sprint 3 Retrospective
-
-      **Sprint Goal**: Ship Content OS and Second Brain templates with full schema upgrade.
-
-      **Outcome**: 13/14 tasks completed. Velocity 58/60 hours. One carry-forward: CRM display template polish (moved to Sprint 4).
-
-      ## What Went Well
-      - Schema upgrade process was smooth once ref_map pattern was established for seed entities
-      - Content entities (deal briefs, activity notes, project briefs) raised the quality bar significantly — writing content as a real user, not a demonstrator, produced noticeably better seed data
-      - suggestedRelations architecture creates a graph density pattern: CRM (22 relations) > Content OS (20) > Second Brain (15) — each template's relational profile matches its real-world use
-
-      ## What Didn't
-      - KR tracking fields in the OKR profile need reconsideration — three separate label/target/current property groups is readable but doesn't scale to dynamic KR counts
-      - Missed one content entity for Second Brain (planned 4, shipped 3)
-
-      ## Actions Next Sprint
-      1. Finalize CRM display template polish (carry-forward)
-      2. Begin PM OS template architecture with OKR as first-class entity
-      3. Validate relationship graph rendering with dense seed entity set (26 relations target)
-      4. Decide: static KR properties vs. sub-entity KR model for v2 OKR profile
-
-  - profileSlug: sprint
-    title: "Sprint 4 — Template Validation"
-    properties:
-      sprint-status: Active
-      sprint-number: 4
-      sprint-start: "2026-02-17"
-      sprint-end: "2026-02-28"
-      sprint-goal: "Complete PM OS template JSON, CRM display template polish, and begin onboarding guide outline"
-      sprint-capacity: 55
-      sprint-velocity: 22
-      sprint-task-count: 10
-      sprint-completed-count: 4
-      sprint-linked-okr: "ref:okr:Launch Synap PM OS — Q1 2026"
-
-  - profileSlug: sprint
-    title: "Sprint 5 — Docs & Distribution"
-    properties:
-      sprint-status: Planning
-      sprint-number: 5
-      sprint-start: "2026-03-03"
-      sprint-end: "2026-03-14"
-      sprint-goal: "Ship onboarding guide, record demo video, build landing page, draft launch content"
-      sprint-capacity: 55
-      sprint-velocity: 0
-      sprint-task-count: 8
-      sprint-completed-count: 0
-      sprint-linked-okr: "ref:okr:Grow Template Activations — Q1 2026"
-
-  - profileSlug: task
-    title: Define 5 profile schemas
-    properties:
-      task-status: Done
-      task-priority: Critical
-      task-assignee: "ref:person:Antoine"
-      task-project: "ref:project:Build PM OS Template"
-      task-sprint: "ref:sprint:Sprint 4 — Template Validation"
-      task-due-date: "2026-02-21"
-      task-effort: 4
-      task-type: Feature
-      task-tags: [deep-work]
-
-  - profileSlug: task
-    title: Configure 15 views
-    properties:
-      task-status: Done
-      task-priority: Critical
-      task-assignee: "ref:person:Antoine"
-      task-project: "ref:project:Build PM OS Template"
-      task-sprint: "ref:sprint:Sprint 4 — Template Validation"
-      task-due-date: "2026-02-24"
-      task-effort: 3
-      task-type: Feature
-      task-tags: [deep-work]
-
-  - profileSlug: task
-    title: Write seed entity content
-    properties:
-      task-status: In Progress
-      task-priority: High
-      task-assignee: "ref:person:Antoine"
-      task-project: "ref:project:Build PM OS Template"
-      task-sprint: "ref:sprint:Sprint 4 — Template Validation"
-      task-due-date: "2026-02-27"
-      task-effort: 5
-      task-type: Feature
-      task-tags: [deep-work]
-
-  - profileSlug: task
-    title: Validate relationship graph
-    properties:
-      task-status: Todo
-      task-priority: High
-      task-assignee: "ref:person:Léa Moreau"
-      task-project: "ref:project:Build PM OS Template"
-      task-sprint: "ref:sprint:Sprint 4 — Template Validation"
-      task-due-date: "2026-02-28"
-      task-effort: 3
-      task-type: Feature
-      task-blocked-by: Seed entity content must be complete first
-      task-tags: [deep-work, waiting]
-
-  - profileSlug: task
-    title: Write OKR setup walkthrough
-    properties:
-      task-status: Backlog
-      task-priority: High
-      task-assignee: "ref:person:Antoine"
-      task-project: "ref:project:Publish PM OS Onboarding Guide"
-      task-sprint: "ref:sprint:Sprint 5 — Docs & Distribution"
-      task-due-date: "2026-03-10"
-      task-effort: 3
-      task-type: Content
-      task-tags: [deep-work, async]
-
-  - profileSlug: task
-    title: Record demo video
-    properties:
-      task-status: Backlog
-      task-priority: High
-      task-assignee: "ref:person:Antoine"
-      task-project: "ref:project:Publish PM OS Onboarding Guide"
-      task-sprint: "ref:sprint:Sprint 5 — Docs & Distribution"
-      task-due-date: "2026-03-14"
-      task-effort: 4
-      task-type: Content
-      task-blocked-by: Template must be live in staging before recording
-      task-tags: [deep-work]
-
-  - profileSlug: task
-    title: Draft LinkedIn launch thread
-    properties:
-      task-status: Backlog
-      task-priority: Medium
-      task-assignee: "ref:person:Antoine"
-      task-project: "ref:project:PM OS Distribution Campaign"
-      task-sprint: "ref:sprint:Sprint 5 — Docs & Distribution"
-      task-due-date: "2026-03-12"
-      task-effort: 2
-      task-type: Content
-      task-tags: [async]
-
-  - profileSlug: task
-    title: Schedule newsletter Issue 14 teaser
-    properties:
-      task-status: Backlog
-      task-priority: Medium
-      task-assignee: "ref:person:Antoine"
-      task-project: "ref:project:PM OS Distribution Campaign"
-      task-sprint: "ref:sprint:Sprint 5 — Docs & Distribution"
-      task-due-date: "2026-03-10"
-      task-effort: 1
-      task-type: Content
-      task-tags: [async, quick-win]
-
-  - profileSlug: task
-    title: Design hero section copy
-    properties:
-      task-status: Backlog
-      task-priority: Medium
-      task-assignee: "ref:person:Antoine"
-      task-project: "ref:project:Waitlist Landing Page"
-      task-due-date: "2026-03-07"
-      task-effort: 2
-      task-type: Content
-      task-tags: [async, quick-win]
-
-suggestedRelations:
-  - { sourceRef: "okr:Launch Synap PM OS — Q1 2026", targetRef: "project:Build PM OS Template", type: parent_of }
-  - { sourceRef: "okr:Launch Synap PM OS — Q1 2026", targetRef: "project:Publish PM OS Onboarding Guide", type: parent_of }
-  - { sourceRef: "okr:Grow Template Activations — Q1 2026", targetRef: "project:PM OS Distribution Campaign", type: parent_of }
-  - { sourceRef: "okr:Grow Template Activations — Q1 2026", targetRef: "project:Waitlist Landing Page", type: parent_of }
-  - { sourceRef: "project:Build PM OS Template", targetRef: "task:Define 5 profile schemas", type: parent_of }
-  - { sourceRef: "project:Build PM OS Template", targetRef: "task:Configure 15 views", type: parent_of }
-  - { sourceRef: "project:Build PM OS Template", targetRef: "task:Write seed entity content", type: parent_of }
-  - { sourceRef: "project:Build PM OS Template", targetRef: "task:Validate relationship graph", type: parent_of }
-  - { sourceRef: "project:Publish PM OS Onboarding Guide", targetRef: "task:Write OKR setup walkthrough", type: parent_of }
-  - { sourceRef: "project:Publish PM OS Onboarding Guide", targetRef: "task:Record demo video", type: parent_of }
-  - { sourceRef: "project:PM OS Distribution Campaign", targetRef: "task:Draft LinkedIn launch thread", type: parent_of }
-  - { sourceRef: "project:PM OS Distribution Campaign", targetRef: "task:Schedule newsletter Issue 14 teaser", type: parent_of }
-  - { sourceRef: "project:Waitlist Landing Page", targetRef: "task:Design hero section copy", type: parent_of }
-  - { sourceRef: "sprint:Sprint 4 — Template Validation", targetRef: "task:Define 5 profile schemas", type: relates_to }
-  - { sourceRef: "sprint:Sprint 4 — Template Validation", targetRef: "task:Configure 15 views", type: relates_to }
-  - { sourceRef: "sprint:Sprint 4 — Template Validation", targetRef: "task:Write seed entity content", type: relates_to }
-  - { sourceRef: "sprint:Sprint 4 — Template Validation", targetRef: "task:Validate relationship graph", type: relates_to }
-  - { sourceRef: "sprint:Sprint 5 — Docs & Distribution", targetRef: "task:Write OKR setup walkthrough", type: relates_to }
-  - { sourceRef: "sprint:Sprint 5 — Docs & Distribution", targetRef: "task:Record demo video", type: relates_to }
-  - { sourceRef: "sprint:Sprint 5 — Docs & Distribution", targetRef: "task:Draft LinkedIn launch thread", type: relates_to }
-  - { sourceRef: "sprint:Sprint 5 — Docs & Distribution", targetRef: "task:Schedule newsletter Issue 14 teaser", type: relates_to }
-  - { sourceRef: "task:Define 5 profile schemas", targetRef: "person:Antoine", type: assigned_to }
-  - { sourceRef: "task:Configure 15 views", targetRef: "person:Antoine", type: assigned_to }
-  - { sourceRef: "task:Write OKR setup walkthrough", targetRef: "person:Antoine", type: assigned_to }
-  - { sourceRef: "task:Draft LinkedIn launch thread", targetRef: "person:Antoine", type: assigned_to }
-  - { sourceRef: "okr:Launch Synap PM OS — Q1 2026", targetRef: "person:Antoine", type: assigned_to }
-  - { sourceRef: "okr:Grow Template Activations — Q1 2026", targetRef: "person:Antoine", type: assigned_to }
-
 # App reference — PM OS lands on its views/dashboard.
 app:
   kind: stored
@@ -1095,6 +717,44 @@ playbooks:
 onboarding:
   goal: "Capture the user's goals, the projects in flight, the current sprint, and who's involved — so the workspace mirrors how their team actually plans and delivers."
   framing: "Act as a sharp delivery lead / chief of staff. Tease out what outcomes matter this quarter, what's actively being worked, what's in the current cycle, and who owns what. Translate that into OKRs, projects, a sprint, and people."
+  expertise:
+    starters:
+      - >
+        Don't collect a wishlist of goals — force ONE north-star metric and 2-3 key results that
+        move it. Propose "the single number that means this quarter succeeded" first, then the
+        handful of measurable KRs under it. Five objectives is zero objectives; a team that's aiming
+        at everything is aiming at nothing.
+      - >
+        Capture what's actually in flight and impose a WIP limit as you go. Ask "what's genuinely
+        being worked THIS week" — not the backlog — and if it's more than the team can finish,
+        that's the finding. Too many projects in progress means nothing ships; the map should make
+        the overload visible.
+      - >
+        Every project and KR gets a named owner before anything else. Lead with "who owns this?" —
+        a goal with no owner is a hope, and it will quietly slip. Capture the person on the project
+        the moment you capture the project; ownerless work is the first thing to surface, not the
+        last.
+    blindSpots:
+      - >
+        "Everything is P1" is the prioritization failure that guarantees the wrong things ship. When
+        every project is Critical, priority carries no information and the team defaults to whatever's
+        loudest. Push back on the priority field — force a real ranking, because if you can't say
+        what's LESS important, you haven't prioritized at all.
+      - >
+        A goal with no owner is a hope, and hopes don't ship. Teams write beautiful OKRs with an
+        empty owner field, and the KR that belongs to "the team" belongs to no one. Surface every
+        ownerless objective, project, and KR — accountability is a name, not a shared intention.
+      - >
+        Too much work-in-progress is the silent throughput killer. Founders equate "many things
+        started" with progress, but a dozen 60%-done projects deliver nothing while three finished
+        ones deliver value. Watch the count of In-Progress items and flag when it exceeds what the
+        team can actually close in a cycle.
+    bar: >
+      A great result is a workspace where the line from a single north-star metric down to the task
+      in flight this week is unbroken: one clear objective with measurable KRs, every project and
+      goal owned by a named person, a real priority ranking (not all-P1), and a WIP that matches
+      capacity. You can answer "are we on track, who owns the thing that's slipping, and what should
+      we STOP to ship what matters?" in one look.
   collect:
     - profileSlug: okr
       what: The goals / OKRs that define success this quarter

package/src/radar.yaml

@@ -189,6 +189,40 @@ onboarding:
     THE SCOUT: Act as a sharp market scout. Curious, factual, neutral. Surface who
     else plays here, where the market is moving, and who's worth learning from.
     Always cite a source when you can.
+  expertise:
+    starters:
+      - >
+        Don't just log named rivals — map the CATEGORY. Buyers compare across three
+        tiers: direct competitors, adjacent tools that solve the same job
+        differently, and the status quo ("a spreadsheet", "do nothing"). Propose
+        entries in all three, because the status quo is usually the real competitor.
+      - >
+        Track positioning by CONTRAST, not features. For each rival, capture the
+        one axis where you're deliberately opposite ("they're enterprise-heavy, we're
+        self-serve") — that contrast is what a buyer remembers. If they only give you
+        a feature list, reflect the underlying axis back and propose that.
+      - >
+        Separate LEADING from LAGGING signals. Pricing changes, hiring sprees, and
+        docs/changelog velocity predict where a competitor is going; press releases
+        and funding rounds only confirm where they've been. Prioritize the leading
+        indicators when you propose what to watch.
+    blindSpots:
+      - >
+        "We have no competitors" is a red flag, not a moat — it usually means the
+        category is undefined or the buyer's alternative (a manual workaround) hasn't
+        been named. Push to name what a buyer does TODAY instead of buying anything.
+      - >
+        Founders over-watch the loud incumbent and miss the fast-moving insurgent
+        one tier down. The threat that kills you is rarely the market leader — it's
+        the well-funded startup attacking your exact wedge. Surface the insurgents.
+      - >
+        A trend with no direction or timing is just a headline. Every trend needs a
+        stance: is it rising, steady, or fading, and does it help or hurt you? An
+        untimed "AI is big" tells strategy nothing — force the "so what for us".
+    bar: >
+      The landscape reads like a real map: every rival placed on a contrast axis, the
+      status-quo alternative named, and each trend carrying a direction and a "so what"
+      — so a strategist can see the open lane you should own, not just a list of logos.
   collect:
     - profileSlug: competitor
       what: Rivals and alternatives a buyer would seriously compare you to.
@@ -261,14 +295,3 @@ bento:
     - kind: view
       viewName: Inspirations
       pos: { x: 6, y: 4, w: 6, h: 4 }
-
-seedEntities:
-  - profileSlug: competitor
-    title: "Example Competitor (replace me)"
-    properties:
-      positioning: "An example rival — describe how they position themselves to buyers."
-      strengths: "What they do well (brand, distribution, price, feature depth)."
-      weaknesses: "Where they fall short — your opening."
-      pricing: "e.g. $X/mo per seat"
-      url: "https://example.com"
-      status: watching