People
Every other module needs to know who people are, where they belong, what they are qualified to do and when they are available. The People module keeps that once — registry, org units, access, certifications, leave, rosters and attendance — built around availability and qualifications, not around rating people.
- People registry and org units
- Access derived from role and unit
- Certifications with expiry warnings
- Leave, rosters and attendance anomalies
One registry for every module
Commerce needs to know who owns an account, operations who is qualified to do a job, finance who may approve a budget, and security who may see what. In most companies each of those answers lives in a different system and drifts out of date at a different speed. Hurukan keeps one registry of people and org units, and every module reads it.
Access that follows the structure
Permissions are derived from role and unit rather than assigned by hand, screen by screen. When someone joins, moves or leaves, the change is approved once and applies everywhere, and every grant and revocation is recorded by the Security and Sovereignty layer. Agents act on behalf of people or processes, within the access those people or processes have.
Qualifications that are checked
Certifications, licences and mandatory training are kept with their expiry dates. An agent flags the ones about to lapse to the person and their manager, and when work is scheduled in Operations and Quality, it is checked against who is actually qualified on that day.
Availability without guesswork
Leave requests and approvals, rosters and recorded hours sit in one place, so planning knows who is available. Where attendance records show anomalies — a missing day, hours that do not add up — they are raised for a person to clarify.
How it fits with what you run
Payroll stays in the system or with the provider you already use, and recorded hours and leave are exported to it. The module is built around availability and qualifications, not around rating people: it tells planning who can do the work, and judgement about people stays with their managers.
What the module covers
People registry
Everyone who works for or with the company, once, with their role, unit, contact details and the documents that belong to them.
Org units
Departments, teams and sites, with their managers, so approvals, reports and access follow the real structure of the company.
Access
Permissions derived from role and unit, granted and revoked through approval, and audited like every other change.
Certifications
Qualifications, licences and training with their expiry dates, flagged before they lapse and checked when work is assigned.
Leave and rosters
Leave requests, approvals and rosters in one place, so planning in other modules knows who is actually available.
Time and attendance
Hours recorded against work, with anomalies such as missing entries or unusual patterns flagged for a person to look at.
Works with
Security and Sovereignty
Server-side permissions, an audit of every change, your infrastructure, open source and a written exit.
Ontology
The company's digital model: objects, relations and rules, versioned and growing with the business.
Agentic Logic
Domain agents that act within written limits, with people deciding on critical steps.
Operations and Quality
Planning, work queue, scheduling, hours and subcontracting; inspections, non-conformances, release and certificates.
Decisions and Tasks
One approval inbox for agent proposals with sources and risk, and tasks that always have an owner.
Questions
What does it record about employees?
What an operating company needs to know: who people are, which unit they belong to, what they are qualified for and when they are available. Attendance anomalies go to a person to clarify, and the module is built around availability and qualifications rather than ranking people.
How does it work with payroll?
Payroll stays in the system or with the provider you already use; recorded hours and leave are exported to it.
How is access granted and removed?
Access follows role and unit and is granted through approval. When someone changes role or leaves, the change propagates to every module, and each grant and revocation is in the audit.
Build the company's operating system with us
Hurukan is pre-launch. If you run a company and want a sovereign, agentic system rather than another suite, we would like to hear what you need.