Designed scope
- records and role-based access
- time and requests
- approval workflows
Planned product · enquiries only
People records, time and approvals with role-appropriate access.
01 / Workflow
An employee submits a request, a manager approves it, and authorized data flows to payroll under control.
Every operation retains company identity, actor, and source linkage.
Acceptance requires tests against the actual authorized version, integration, and data.
02 / Scope
03 / API
Connections use authenticated APIs and durable events. Single sign-on does not replace data synchronization, and each service retains its declared authority.
04 / Docs
Commands require an idempotency key, legal company, actor, source, and timestamp. Corrections use linked reversals and never silently rewrite history.
There is no validated application entry yet. The /app route does not redirect until origin, path, license, and release evidence are approved.
No price is published. Commercial, tax, refund, and support policies are unapproved; this page supports enquiries only.
05 / FAQ
No. Its status is planned and the offer is enquiry-only.
No. There is no approved price or checkout.
It describes planned public scope and its boundaries; it does not prove production availability, certification, or acceptance.