@synap-core/workspace-templates 0.2.2 → 0.4.0

package/src/hr.yaml

@@ -0,0 +1,474 @@
+# HR workspace template
+# The PEOPLE operating system for a company — the team, hiring, performance, and
+# policies in one lens. Displayed as "People". Consumes the Foundation `strategy`
+# domain so hiring, reviews, and onboarding stay anchored to the company's real
+# values (culture), not a generic template.
+
+meta:
+  slug: hr
+  name: HR
+  description: The people operating system — team, hiring, performance reviews, and policies in one place.
+  icon: users-round
+  color: "#E8663D"
+  tags: [hr, people, hiring, team]
+  isPublic: true
+
+workspace:
+  name: People
+  description: The company's people operating system — the team, open roles and hiring pipeline, performance cycles, onboarding plans, and people policies.
+  proposalId: hr-v1
+  subtype: hr
+  visibility: members
+  workspaceType: operational
+  capabilities:
+    - hr.team
+    - hr.hiring
+    - hr.reviews
+  # HR provides the people domain to the rest of the pod, and CONSUMES the
+  # Foundation `strategy` domain — its values become the culture that anchors
+  # hiring bars, review rubrics, and onboarding.
+  sourceRoles:
+    hr: provider
+    strategy: consumer
+
+profiles:
+  - slug: team-member
+    displayName: Team Member
+    icon: user-round
+    color: indigo
+    description: "A person on the team — the core people record."
+    properties:
+      - slug: role-title
+        label: Role
+        valueType: string
+        inputType: text
+        placeholder: e.g. Senior Product Designer
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [active, onboarding, on-leave, offboarding, alumni]
+        constraints: { defaultValue: active }
+      - slug: department
+        label: Department
+        valueType: string
+        inputType: select
+        enumValues: [Engineering, Product, Design, Sales, Marketing, Operations, People, Finance, Other]
+      - slug: employment-type
+        label: Employment Type
+        valueType: string
+        inputType: select
+        enumValues: [full-time, part-time, contractor, intern]
+        constraints: { defaultValue: full-time }
+      - slug: start-date
+        label: Start Date
+        valueType: date
+        inputType: date
+      - slug: email
+        label: Email
+        valueType: string
+        inputType: text
+        placeholder: name@company.com
+        constraints: { format: email }
+      - slug: location
+        label: Location
+        valueType: string
+        inputType: text
+        placeholder: City, Country
+
+  - slug: role
+    displayName: Role
+    icon: briefcase
+    color: amber
+    description: "A position — open req or filled seat — with its job spec."
+    properties:
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [draft, open, interviewing, offer-out, filled, on-hold, closed]
+        constraints: { defaultValue: open }
+      - slug: department
+        label: Department
+        valueType: string
+        inputType: select
+        enumValues: [Engineering, Product, Design, Sales, Marketing, Operations, People, Finance, Other]
+      - slug: seniority
+        label: Seniority
+        valueType: string
+        inputType: select
+        enumValues: [junior, mid, senior, staff, lead, manager, director]
+      - slug: employment-type
+        label: Employment Type
+        valueType: string
+        inputType: select
+        enumValues: [full-time, part-time, contractor, intern]
+        constraints: { defaultValue: full-time }
+      - slug: hiring-manager
+        label: Hiring Manager
+        valueType: string
+        inputType: text
+      - slug: target-start
+        label: Target Start
+        valueType: date
+        inputType: date
+      - slug: job-spec
+        label: Job Spec
+        valueType: string
+        inputType: textarea
+        placeholder: Mission, responsibilities, must-haves, hiring bar...
+
+  - slug: candidate
+    displayName: Candidate
+    icon: user-plus
+    color: cyan
+    description: "A person moving through the hiring pipeline for a role."
+    properties:
+      - slug: stage
+        label: Stage
+        valueType: string
+        inputType: select
+        enumValues: [applied, screening, interview, offer, hired, rejected, withdrawn]
+        constraints: { defaultValue: applied }
+      - slug: source
+        label: Source
+        valueType: string
+        inputType: select
+        enumValues: [referral, inbound, outbound, agency, event, other]
+      - slug: email
+        label: Email
+        valueType: string
+        inputType: text
+        placeholder: name@email.com
+        constraints: { format: email }
+      - slug: phone
+        label: Phone
+        valueType: string
+        inputType: text
+      - slug: resume-url
+        label: Resume
+        valueType: string
+        inputType: url
+      - slug: rating
+        label: Rating
+        valueType: number
+        inputType: number
+        constraints: { min: 0, max: 5 }
+      - slug: notes
+        label: Notes
+        valueType: string
+        inputType: textarea
+
+  - slug: review
+    displayName: Review
+    icon: clipboard-check
+    color: violet
+    description: "A performance review within a company review cycle."
+    properties:
+      - slug: cycle
+        label: Cycle
+        valueType: string
+        inputType: text
+        placeholder: e.g. H1 2026
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [not-started, self-review, manager-review, calibration, shared, complete]
+        constraints: { defaultValue: not-started }
+      - slug: rating
+        label: Rating
+        valueType: string
+        inputType: select
+        enumValues: [exceeds, meets, developing, below]
+      - slug: reviewer
+        label: Reviewer
+        valueType: string
+        inputType: text
+      - slug: summary
+        label: Summary
+        valueType: string
+        inputType: textarea
+
+  - slug: policy
+    displayName: Policy
+    icon: scroll-text
+    color: slate
+    description: "A people policy or handbook section."
+    properties:
+      - slug: category
+        label: Category
+        valueType: string
+        inputType: select
+        enumValues: [leave, benefits, conduct, remote-work, expenses, security, compensation, other]
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [draft, active, under-review, archived]
+        constraints: { defaultValue: active }
+      - slug: owner
+        label: Owner
+        valueType: string
+        inputType: text
+      - slug: effective-date
+        label: Effective Date
+        valueType: date
+        inputType: date
+      - slug: summary
+        label: Summary
+        valueType: string
+        inputType: textarea
+
+  - slug: onboarding-plan
+    displayName: Onboarding Plan
+    icon: rocket
+    color: green
+    description: "A new hire's first-weeks plan, buddy, and checklist."
+    properties:
+      - slug: status
+        label: Status
+        valueType: string
+        inputType: select
+        enumValues: [not-started, in-progress, complete]
+        constraints: { defaultValue: not-started }
+      - slug: start-date
+        label: Start Date
+        valueType: date
+        inputType: date
+      - slug: buddy
+        label: Buddy
+        valueType: string
+        inputType: text
+      - slug: checklist
+        label: Checklist
+        valueType: string
+        inputType: textarea
+        placeholder: Accounts, intro meetings, first task, 30/60/90 goals...
+
+views:
+  - name: Team
+    slug: team
+    type: table
+    scopeProfileSlug: team-member
+    defaultView: true
+    description: Everyone on the team, by role and status.
+    config:
+      columns: [title, role-title, department, status, employment-type, start-date, location]
+  - name: Hiring Pipeline
+    slug: hiring-pipeline
+    type: kanban
+    scopeProfileSlug: candidate
+    groupBy: stage
+    description: Candidates moving through the pipeline, by stage.
+    config:
+      groupBy: stage
+      cardFields: [source, rating, email]
+  - name: Open Roles
+    slug: open-roles
+    type: table
+    scopeProfileSlug: role
+    description: Positions and their hiring status.
+    config:
+      columns: [title, status, department, seniority, hiring-manager, target-start]
+  - name: Reviews
+    slug: reviews
+    type: kanban
+    scopeProfileSlug: review
+    groupBy: status
+    description: Performance reviews across the cycle, by status.
+    config:
+      groupBy: status
+      cardFields: [cycle, rating, reviewer]
+  - name: Policies
+    slug: policies
+    type: table
+    scopeProfileSlug: policy
+    description: People policies and handbook sections.
+    config:
+      columns: [title, category, status, owner, effective-date]
+  - name: Onboarding
+    slug: onboarding
+    type: table
+    scopeProfileSlug: onboarding-plan
+    description: New hire onboarding plans and progress.
+    config:
+      columns: [title, status, start-date, buddy]
+
+# Schema-level relations — give the relation picker domain links from day one.
+entityLinks:
+  - sourceProfileSlug: candidate
+    targetProfileSlug: role
+    type: applying_for
+    label: Applying for
+  - sourceProfileSlug: review
+    targetProfileSlug: team-member
+    type: reviews
+    label: Reviews
+  - sourceProfileSlug: onboarding-plan
+    targetProfileSlug: team-member
+    type: for
+    label: For
+  - sourceProfileSlug: team-member
+    targetProfileSlug: role
+    type: fills
+    label: Fills
+  - sourceProfileSlug: team-member
+    targetProfileSlug: team-member
+    type: reports_to
+    label: Reports to
+
+onboarding:
+  goal: Capture the real shape of the company's people — who's on the team, what roles are open, who's in the pipeline, and how performance is reviewed — so the People workspace reflects the actual org, not a template.
+  framing: >
+    THE HEAD OF PEOPLE: Act as a sharp, warm head of people/talent. You care about
+    two things at once — the humans and the operating system around them. Draw out
+    the real org: who does what, what you're hiring for and why, how candidates move,
+    and how you run performance. Anchor everything to the company's culture — pull the
+    Foundation values and reflect them back as the hiring bar and review rubric.
+    Be direct about gaps (no owner on a policy, a role open with no hiring manager),
+    but never clinical — these are people.
+  expertise:
+    starters:
+      - >
+        Don't ask for a hiring wishlist — propose the first roles by what unblocks
+        the FOUNDER. Whatever the founder is the bottleneck on (sales they can't
+        scale, product they can't ship fast enough, ops eating their week) is the
+        next hire. Reflect their week back and name the role that buys their time
+        back, rather than filling an org chart.
+      - >
+        Hire for the next 12 months, not the dream team. Propose the role at the
+        seniority the company needs NOW — often a scrappy generalist over a
+        specialist VP who'll be bored and expensive. Push back on premature senior
+        hires the stage can't feed with real scope.
+      - >
+        Anchor the hiring bar and review rubric to the company's actual values
+        (pull them from Foundation), not generic competencies. Propose 3–4 concrete
+        "must be true" signals per role derived from those values, so "a great hire"
+        means something specific here rather than "smart and nice".
+    blindSpots:
+      - >
+        Culture is not perks — it's what you REWARD and what you TOLERATE. Founders
+        describe culture as ping-pong and free lunch; the real culture is who gets
+        promoted and what bad behavior goes unchecked. If they answer "culture" with
+        benefits, redirect to: what do you celebrate, and what do you refuse to
+        put up with?
+      - >
+        Onboarding and role clarity beat headcount. A team that doesn't know who owns
+        what will thrash no matter how many people you add. Before proposing new
+        hires, check that existing roles have clear ownership and every new hire has a
+        30/60/90 plan — hiring into ambiguity just scales the confusion.
+      - >
+        An open role with no hiring manager, or a policy with no owner, is a gap
+        hiding in plain sight. Surface these directly: unowned reqs stall for months
+        and unowned policies get ignored. Every role needs a decision-maker; every
+        policy needs someone accountable for it.
+    bar: >
+      The org is honest — real people with clear ownership and no orphaned roles or
+      policies — the open roles map to what actually unblocks the founder at the right
+      seniority for the stage, "a great hire" is defined by concrete signals tied to
+      the company's real values, and every new hire lands into role clarity and a
+      30/60/90 plan rather than ambiguity.
+  collect:
+    - profileSlug: team-member
+      what: The people currently on the team, with their role, department, and status.
+      cardinality: several
+      keyFields: [role-title, department, status]
+    - profileSlug: role
+      what: The positions you're hiring for right now — open reqs with their hiring bar.
+      cardinality: few
+      keyFields: [status, department, seniority]
+    - profileSlug: candidate
+      what: Active candidates worth tracking now, and where they are in the pipeline.
+      cardinality: few
+      keyFields: [stage, source]
+    - profileSlug: review
+      what: The current review cycle and how you run performance (cadence + rubric).
+      cardinality: one
+      keyFields: [cycle, status]
+  openingQuestions:
+    - "Who's on the team today — walk me through the people and what they own."
+    - "What are you hiring for right now, and what does 'a great hire' look like here?"
+    - "How do you run performance — what's your review cadence, and what does it reward?"
+  doneWhen: The core team exists with roles and status, at least one open role with its hiring bar is captured, and a review cycle is defined — ideally with its rubric tied to the Foundation values.
+
+app:
+  kind: stored
+  cellKey: entity-detail
+
+layout:
+  defaultView: Team
+  defaultApp: null
+  pinnedApps: [dashboard, data, intelligence]
+  sidebarItems:
+    - kind: view
+      viewName: Team
+      label: Team
+      icon: users-round
+    - kind: view
+      viewName: Hiring Pipeline
+      label: Hiring Pipeline
+      icon: user-plus
+    - kind: view
+      viewName: Open Roles
+      label: Open Roles
+      icon: briefcase
+    - kind: view
+      viewName: Reviews
+      label: Reviews
+      icon: clipboard-check
+    - kind: view
+      viewName: Onboarding
+      label: Onboarding
+      icon: rocket
+    - kind: view
+      viewName: Policies
+      label: Policies
+      icon: scroll-text
+    - kind: app
+      appId: data
+      label: All Data
+      icon: database
+
+bento:
+  viewName: People Command Center
+  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: 3, h: 2 }
+      config:
+        profileSlug: team-member
+        label: Team
+    - kind: widget
+      widgetType: entity-count
+      pos: { x: 3, y: 2, w: 3, h: 2 }
+      config:
+        profileSlug: role
+        label: Open Roles
+    - kind: widget
+      widgetType: entity-count
+      pos: { x: 6, y: 2, w: 3, h: 2 }
+      config:
+        profileSlug: candidate
+        label: In Pipeline
+    - kind: widget
+      widgetType: entity-count
+      pos: { x: 9, y: 2, w: 3, h: 2 }
+      config:
+        profileSlug: review
+        label: Reviews
+    - kind: view
+      viewName: Hiring Pipeline
+      pos: { x: 0, y: 4, w: 8, h: 5 }
+    - kind: view
+      viewName: Open Roles
+      pos: { x: 8, y: 4, w: 4, h: 5 }
+    - kind: view
+      viewName: Team
+      pos: { x: 0, y: 9, w: 6, h: 4 }
+    - kind: view
+      viewName: Reviews
+      pos: { x: 6, y: 9, w: 6, h: 4 }