Platform Capabilities
Summary
This capability map records what is confirmed in the current source and uses explicit maturity labels to avoid presenting transitional foundations as completed product commitments.
Audience
- Enterprise customers and implementation partners
- Product owners
- Platform administrators
- Solution architects
Reference Content
Maturity labels
| Label | Meaning in this page |
|---|---|
| Implemented | Substantial current implementation is present; release acceptance still applies. |
| Transitional | Functionality exists across the active monolith and/or an extracted service while routing or migration remains in progress. |
| Foundation | A working technical or domain foundation exists, but breadth or end-to-end adoption is not yet established. |
| Planned | Only a skeleton or planning boundary is present; no completed capability is asserted. |
Confirmed capability groups
| Capability group | Status | Confirmed scope and boundary |
|---|---|---|
| Platform and tenant administration | Transitional | Platform metadata, tenant administration, licensing/configuration foundations, and provisioning capability are present. Platform paths coexist with monolith behavior. |
| Identity and access | Transitional | Authentication, roles and permissions, access/refresh tokens, sessions, and security events are implemented in an extracted identity boundary while compatibility paths remain. |
| Employee and organization management | Transitional | Employee and organization domains exist in the monolith and extracted service boundaries. Migration and route cutover remain incremental. |
| Attendance and leave | Transitional | Dedicated attendance and leave services, persistence, APIs, and events are present alongside compatibility and dependent-service paths. |
| Payroll | Transitional | Payroll calculation and processing foundations, read models, APIs, and event integration are present while migration remains active. |
| Recruitment and onboarding | Transitional | Dedicated recruitment domain models, APIs, workflow/document interactions, and lifecycle events are present. End-to-end release acceptance is outside this page. |
| Expense and asset management | Transitional | Dedicated domain services, APIs, workflow/document integrations, and lifecycle events are present while cutover remains configuration-controlled. |
| Performance | Transitional | Review-cycle and appraisal domain foundations, APIs, workflow integration, and lifecycle events are present. |
| Training | Foundation | A dedicated service, persistence model, API surface, and event contracts exist; this page does not claim complete production breadth. |
| Workflow | Foundation | A reusable workflow definition, instance, task, and event foundation exists. Adoption by every business process is not asserted. |
| Documents | Transitional | Document metadata, generation/upload flows, provider abstraction, and read-model processing exist. Storage implementation and rollout remain deployment concerns. |
| Notifications | Foundation | Templates and in-application/email delivery foundations exist. This page does not claim that every delivery channel is complete. |
| Integrations | Foundation | Event consumption, routing, retry, audit, and dead-letter foundations exist. External downstream integrations require solution-specific confirmation. |
| Helpdesk | Foundation | A dedicated service boundary and core persistence/API foundation exist; complete operational coverage is not asserted. |
| Reporting and analytics | Planned | The standalone reporting service is a skeleton. Reporting should not be treated as a completed extracted capability. |
| Standalone HR operations | Planned | The standalone HR operations service is a skeleton; related business functions may currently remain in the monolith or dedicated domain services. |
| Standalone tenant provisioning service | Planned | The standalone service is a skeleton. Tenant provisioning capability currently resides in the platform boundary and must not be conflated with this planned service. |
Statuses reflect code structure and configuration reviewed on 2026-07-14, not contractual availability, deployment state, or production certification.
Related Articles
See Also
Keywords
- Capability maturity
- Product scope
- Implementation status
Revision Information
- Last reviewed: 2026-07-14
- Owner: product-team
- Status: Draft