Humanus
humanus · Latin — of people
The whole employee lifecycle in one record — hiring, contract, payroll, performance and departure — with the sensitive parts kept in their own gated store.
What it includes
People and records
- Employee record, contracts and documents
- Org chart, teams and office locations
- Onboarding and offboarding as lifecycle processes
- Career paths and benefit plans
- Employee self-service profile
Vault and confidentiality
- A secure vault for sensitive personnel records
- Gated server-side, not hidden in the interface
- Storage metered and quota-controlled
- Full audit of who read what
Payroll and signature
- Payroll runs posted to the ledger
- Payroll OCR for external payslips
- Electronic signature of employment documents
- Qualified signatures up to PAdES B-LTA
- Multi-file signature envelopes
Performance and analytics
- Goals and performance reviews
- People analytics: headcount, tenure, turnover, PTO balances
- Pay equity reporting
- Ten analytics reports, permission-gated
Lifecycle processes
Onboarding and offboarding that actually run.
Not a document called “onboarding checklist” that somebody copies and then forgets. A template you define once becomes a run against one person, with each step owned by someone, in order, and visibly unfinished until it is done.
What a step can be
Something to do
A plain task somebody ticks off — order the laptop, book the induction.
Something to sign
The contract, the annex, the NDA. It goes out for signature and the step completes itself when it comes back signed.
Something to hand in
A qualification, an ID, a bank mandate — uploaded into the employee’s own gated store rather than an inbox.
Something to fill in
A form whose answers stay with the record instead of in a reply nobody can find later.
Waiting on their account
The step that holds until the person can actually sign in, so the rest does not pile up before they exist.
Something done elsewhere
The thing that happens in another system, tracked here so it is not the step everyone forgets.
Signing is a step, not an errand
The run does not advance while a document is unsigned, and it advances by itself the moment it is. Nobody has to notice and tick a box.
Who does it is resolved when it starts
A step can belong to a different person depending on the department the new hire lands in — decided at the moment the run begins, not hardcoded into the template.
Editing a template never rewrites a run
The steps are copied onto the run when it starts. Improving the template for next time cannot quietly change what somebody is halfway through.
One at a time, per person
A second onboarding cannot be opened for someone who already has one running. The database refuses it rather than leaving two half-done lists.
The unfinished ones surface
RR. HH. watches for a step that has gone quiet and for a leaver whose loose ends were never tied — the two failures nobody notices until they matter.
Who watches it
HR
Contracts, absences, working time and the signatures about to expire.
One of the eleven AI employees is assigned to this domain. It reads what a person in that role could read, and files what it finds.