JCCC HRIS platform system diagram showing P1 in-scope features and deferred phases P1.5 and P3, plus infrastructure, user roles, and helpful notes.

JCCC HRIS โ€” System Overview by Phase
Auth / Access
People data
Content
Stub (inert placeholder)
Safety / Crisis
P1
MVP ยท Jul 30
๐Ÿ” Login
Google SSO + magic link
Staff allowlist
๐Ÿ‘ฅ Staff Directory
Filterable roster
~130 staff, 9 regions
๐Ÿชช Staff Profiles
Self-service edit
Field-level access tiers
๐Ÿ—‚ Document Vault
Secure file storage
Certs, ID copies
๐Ÿ“ฃ Announcements
One-way feed
Admin โ†’ all staff
๐Ÿ“– Wiki / Docs
TipTap editor
SOPs, trilingual
๐ŸŒ Trilingual UI
JA (default) ยท EN ยท KO
CJK typography
๐Ÿ”ฉ Crisis stubs
Inert hooks for P3
(no live behavior)
P1.5
Fast-follow
โœ… Safety Check-in TBD
ๅฎ‰ๅฆ็ขบ่ช
Staff confirms safety
๐Ÿ’ฌ LINE Channel TBD
Emergency delivery
via LINE
๐Ÿšจ Emergency Theme TBD
UI mode activation
on crisis declaration
๐Ÿ—บ Knowhow Sharing TBD
City-to-city
knowledge exchange
P3
Crisis cmd
๐ŸŽ› Crisis Command TBD
Dynamic RBAC pivot
on crisis level
๐Ÿ“ก Multi-channel Blast TBD
Push ยท SMS ยท LINE
Google Chat override
๐Ÿ“’ Incident Diary TBD
Immutable log
scenario playbooks
โ†”๏ธ Two-way Feedback TBD
Staff โ†” Leadership
response loop
Infrastructure (all phases)
โšก SvelteKit (SSR)
๐Ÿ˜ PostgreSQL / Supabase
๐Ÿ”‘ better-auth
๐Ÿ’พ Supabase Storage
๐ŸŒ Netlify hosting
๐Ÿ”ค Paraglide i18n
Who uses this
๐Ÿ‘คStaffโ€” view directory, manage own profile
๐Ÿ‘ฅTeam Leadersโ€” see team fields
๐Ÿ—‚Operationsโ€” visa, passport, rent
๐ŸขLDHR / NLTโ€” full HR access, announcements
๐Ÿ”—Externalโ€” public directory only
๐Ÿ“ Notes for the team
๐ŸŽฏ
P1 is the firm commitment. Everything in the blue row is what we're building now, targeting end of July. This is the WorkVivo replacement โ€” auth, staff directory, profiles, document vault, announcements, and the wiki.
๐Ÿ’ฌ
P1.5 and P3 are directional, not final. The features shown are our best current thinking โ€” they exist so the P1 architecture doesn't paint us into a corner later. But the exact scope, timing, and even which features we build are open for discussion with the team.
๐Ÿ”ฉ
The "Crisis stubs" in P1 are invisible to users. They're small technical placeholders (a database column, a log table) so that if we do build crisis features later, it won't require a complete rewrite. Nothing actually activates in P1.
๐ŸŒ
Trilingual support is baked into P1. Japanese is the default; English and Korean follow. If a Korean translation isn't ready for launch, the app falls back to Japanese โ€” no rewrite needed to add it later.
๐Ÿ”
Access tiers control what you can see. Not everyone sees the same fields on a staff profile. Sensitive info (visa, passport, emergency contacts) is only visible to the roles that need it โ€” this is enforced at the database level, not just the UI.