People and Calendar
People records
Operational HR records describe role, team, and work context without private support text.
For Companies / People and Calendar
Operational records kept separate from private support.
This surface is for operating context: who is in the organization, what is scheduled, and which handoff is needed. It is not payroll, benefits administration, or a private support archive.
People and Calendar
What belongs here
People and Calendar can hold operational HR context, scheduled moments, and internal coordination state.
People and Calendar
Calendar context
Scheduling context supports coordination and review without turning support into manager notes.
People and Calendar
Clear separation
The company surface is structurally separate from the personal support lane.
Privacy Membrane
Operational does not mean private
People and Calendar are for operational HR records only; private support content remains outside company views.
What belongs here
Roles, teams, and work records.
Calendar context for operational review.
Intranet-style coordination notes.
What does not belong here
Private support content, companion memory, and individual wellness inference do not belong in this surface.
No private conversation text.
No payroll or benefits promise.
No recruiting decision automation.
People and Calendar
Different from ATS/HRIS/HCM suites
Synphoria leaves payroll/benefits, HRIS master data and full ATS ownership to those systems. People and Calendar hold the controlled handoff: operational context, scheduled review, and workspace coordination without importing private support content.
HRIS/HCM remains the source for payroll, benefits, and employee master data.
ATS remains the source for hiring workflow ownership; Synphoria does not rank candidates autonomously.
Raw private content never moves into company/Oracle/People/Calendar/recruiting views.
People and Calendar are operational surfaces, not payroll, benefits administration, or private support access.
What does not belong here
What does not belong here
Private support content, companion memory, and individual wellness inference do not belong in this surface.
Separate from the personal support lane.
Separate from recruiting decisions.
Separate from payroll and benefits systems.
People and Calendar
Keep operations readable without crossing support boundaries.
Review how People and Calendar fit the company operating layer while private support remains excluded.
Category map
Explore the connected system
HR Wellness Intelligence
Company-facing boundary for Wellness, People, reports, and Oracle evidence.
The private companion side that stays outside employer-facing views.
Primary category gateway for support, company signal, and HR workflows.
Safe specimen of aggregate company signal without real employee data.
Feature page for 10+ cohort evidence, aggregate-only signal, and person-level exclusion.
Feature page for executive analytics with source window, confidence, and privacy refusal.