Flux Platform Roadmap
Vision
Employ Inc. is replacing the fragmented hiring toolchain with a single AI-native platform. Today, small and mid-market employers stitch together legacy applicant tracking systems, spreadsheets, email threads, and disconnected payroll portals to manage hiring. The result is slow, error-prone, and opaque — hiring managers lose candidates to friction, compliance gaps go unnoticed, and nobody has a clear picture of pipeline health. Employ Inc. owns three established ATS products (JazzHR, Lever, Jobvite) that collectively serve hundreds of thousands of employers. The strategic play is to unify these products onto a single canonical platform via a strangler-fig migration, replacing legacy backends incrementally while preserving existing customer relationships and revenue. The platform’s primary interface is not a traditional dashboard — it is an AI companion. Conversational agents guide users through complex, multi-step hiring workflows using natural language, eliminating the need to learn yet another SaaS UI. The agent understands context, remembers prior conversations, researches candidates, generates job descriptions, schedules interviews, and hands off new hires to payroll — all within a single chat thread. Traditional dashboard views exist as complements to the chat, not replacements for it. Every action available in the UI is also available through conversation, giving employers the freedom to work however they prefer. The first product built on the Flux platform is codenamed Spark — a micro ATS targeting small-business hiring managers who lack dedicated recruiters and need an opinionated, end-to-end workflow rather than a configurable toolkit. The initial go-to-market is through a partnership with Paychex, where Spark’s Hiring Companion is accessible directly from Paychex Flex, creating a seamless bridge from “I need to hire someone” to “they’re on payroll.”Roadmap Structure — Waves × Milestones
Flux’s roadmap uses two constructs that sit on top of each other:- Waves describe functional capability domains. They are persistent, long-lived buckets of cycles that evolve over time. “Wave 0 complete” does not mean Wave 0 is archived — it means its current scope is operational. Waves are not release trains.
- Milestones are dated releases that cherry-pick specific cycles across multiple waves toward a target. “M1: Paychex Pilot Launch — 2026-04-30” pulls cycles from Waves 1, 2, 3, 4, 5, and 6. A milestone ships; waves continue.
milestones/paychex-pilot-launch.md for the active milestone, and superpowers/specs/2026-04-17-paychex-pilot-release-design.md for the design rationale.
Platform Architecture
The Flux platform is organized into layers that separate concerns cleanly, enabling independent evolution of each component while maintaining a coherent end-to-end experience.- Canonical API + Event Platform: A unified data model and event-driven architecture that spans all ATS products. Every entity (employer, job, candidate, application, interview, offer) conforms to a single schema. Domain events are published on every state transition.
- Tenant Router: Multi-tenant routing layer that directs requests to legacy ATS systems during strangler-fig migration or to the modern Flux stack for new and migrated tenants.
- BFAI Platform (AI Layer): SSE streaming, MCP tool serving, LLM coordination, ReAct agent loop, tool dispatch with RBAC policy, prompt routing, full audit logging.
- AI Companions: Conversational agents. V1 is the Employer Hiring Companion (“Spark”). Wave 3 adds the Candidate Agent peer persona. Wave 4 adds the persistent Candidate Match Agent.
- Modern ATS UI: Next.js 15 + React 19 + assistant-ui with generative UI components rendered inline in chat and traditional dashboard views as complements.
- Context Engine: Cerebe cognitive services — memory fabric, meta-learning, knowledge graphs.
- Integration Layer: Indeed / LinkedIn / ZipRecruiter / Appcast / JobGet / Vonq for job distribution; Paychex Flex for payroll; Google Calendar / Outlook for scheduling; Resend / Bird / Apple Business Register for notifications.
Waves (Functional Domains)
| Wave | Title | Status | Domain |
|---|---|---|---|
| Wave 0 | AI Blueprint Foundation | Complete | sage-blueprint stack: ReAct agent, SSE chat, skills, Temporal, observability, CI/CD |
| Wave 1 | Employer Domain | In progress | Employer signup, auth, chat/agent, dashboard, conversation history, contextual sidebar |
| Wave 2 | Job Posting | In progress | Job creation conversationally, JD generation, screening questionnaires, 3-tier distribution (Indeed/LinkedIn/ZipRecruiter/Appcast/JobGet/Vonq) |
| Wave 3 | Candidate | In progress | Identity, portal, agent-native chat, campaign domain, multi-channel engagement (web/SMS/WhatsApp/email/iMessage) |
| Wave 4 | Candidate Selection | In progress | Screening + ranking, persistent Match Agent, Intelligence UI, Fairness, EU AI Act compliance, Select for Hire, Paychex Flex |
| Wave 5 | Platform & Trust | In progress | Pricing, feature flags, evals, observability, security, SOC2 prep, deploy hardening, staging, production infra |
| Wave 6 | Dark Factory SDLC | In progress | Spec-driven dev, Chief Engineer review, autonomous incident response, progressive delivery, AI debt tools, skill-driven automation |
Milestones (Dated Releases)
| Milestone | Title | Target | Status | Draws From Waves |
|---|---|---|---|---|
| M1 | Paychex Pilot Launch | 2026-04-30 | Active | 1, 2, 3, 4, 5, 6 |
| M2 | A2P 10DLC SMS Cutover | post-pilot | Planned | 3 |
| M3 | Full Job Distribution (Tier 2 + Tier 3) | post-pilot | Planned | 2 |
| M4 | Candidate Match Agent GA | post-pilot | Planned | 4 |
| M5 | Candidate Agent Multi-Channel GA | post-pilot | Planned | 3 |
| M6 | Dark Factory Autonomous Ops GA | post-pilot | Planned | 6 |
| M7 | SOC2 Type I | post-pilot | Planned | 5 |
Paychex PRD Alignment
The Hiring Companion PRD defines nine functional requirements (HC-1 through HC-9) that map to our implementation cycles:| PRD Requirement | Description | Status | Implementing Cycles |
|---|---|---|---|
| HC-1 | Define Hiring Need | Done | 203 (intake tools) + 212 (chat wiring) |
| HC-2 | Research Candidate Profiles | Done | 203 (research_candidate_profiles tool) |
| HC-3 | Generate Job Description | Done | 203 (generate_job_description tool) |
| HC-4 | Screening Questionnaire | Done | 202 (model) + 203 (tool) |
| HC-5 | Post to Job Boards | In M1 | 208 Phase 1 (Wave 2) |
| HC-6 | Talent Fit Matching | Done (pilot scale) | 203 (screen_resume + rank_candidates); Match Agent (Wave 4) post-pilot |
| HC-7 | Schedule Interviews | In M1 | Cycle 204 + chat-driven scheduling (Wave 1); full Temporal orchestration governed by CL-3 |
| HC-8 | Select for Hire | In M1 | Cycle 363 (Wave 4) — canonical-first, export path for manual Paychex (floor); PaychexApiGateway governed by CL-1 |
| HC-9 | Notifications | In M1 | Notification backbone (PR #386 merged) + Cycle 323.6 email subset (Wave 3) + Cycle 323.7 SMS (Wave 3) |
Owner
Patrick Jean, CTO — Employ Inc.Changelog
- 2026-04-17: Roadmap reorganized around functional domains. Waves 1–5 renamed and renumbered; new Wave 6 (Dark Factory SDLC) created. Release sequencing moved to the new Milestones construct. M1 Paychex Pilot Launch activated with design spec, milestone doc, three new cycles (323.7, 364, 365), and cut-line fallbacks. See
docs/superpowers/specs/2026-04-17-paychex-pilot-release-design.md. - 2026-03-31: Original wave structure published (Waves 0–3 release-sequenced).