HR

Your team's records, in your team's memory.

Two kinds of records: `employee` (role, start date, salary, status, who they report to) and `leave_request` (dates, type, approval state on a small board). Hiring closes the loop: a candidate marked hired in Recruiting becomes an employee record here.

Because the records are memory, the everyday questions answer themselves — who joined this year, who's off next week, who reports to whom — in chat, over MCP, from the same rows.

What it does

Employee directory with role, start date, salary and status.
Leave requests on a pending / approved / rejected board.
Reporting lines via employee-to-employee links.
Ask your AI who's away, who's new, who reports to whom.

What it stores

As ordinary objects in your workspace memory — readable by your AI over MCP, browsable like any memory.

employee — A person employed by the company — job_title, start_date, salary, status (active|left).
leave_request — A time-off request — from_date/to_date, leave_type (vacation|sick|other), status (pending|approved|rejected).