Otto prepares. A person confirms.

Leave approved in one place does not put that person on the pay run by itself. Payroll still needs them in the run.

Otto assembles the packet from the approved leave, the attendance already on the record, and the salary. That packet sits in the suggestion tray. A named person stamps the run. Two trays, one stamp: if nobody confirms, nothing posts.

Otto can draft a pay run from attendance, leave, and salary. It can draft a leave reservation against policy and balance. It can draft a candidate stage-move and the email that goes with it. It can draft a company policy from a source PDF.

Each of those is a proposal. A proposal does not change the record.

A named person acts on the same record Otto drafted. They can edit before they confirm. A reject leaves no write.

If nobody confirms, nothing posts. Unsupervised writes are out of scope on purpose. The same gate holds in the HR workspace, the employee portal, and MCP apps, whether Claude, ChatGPT, Cursor, or any MCP client. Otto prepares wherever you ask. A person confirms. An MCP call cannot bypass the stamp.

The audit row holds the actor, the timestamp, and the subject, whether employee, candidate, or pay run, plus the before/after or a "rejected." HR can read it later, and where entitled so can the employee. It is not a black box, not a public score, and not a fabricated case study.

Hiring: a stage move, a rejection, a hire packet. Payroll: pay-run draft → confirm → lock. Leave: request → approve or reject. Policies: draft → publish.

The product tour is /platform. The bordro page is /bordro-programi. The teams this loop is built for are on /ajan-ik.

It will not post a pay run, move a candidate to Hired, publish a policy, or change someone's balance. Those writes wait for the stamp.

This is not "AI HR" and not autopilot payroll. Otto prepares work. A person stays accountable. See /ajan-ik for who that person usually is.

In Türkiye most companies close the period outside the firm. Hours, leave, and pay are created inside. Otto builds the packet from those three. A named person, often the accountant, stamps it.

This is not a calculator race. The gross-to-net table lives in the /bordro guide. This page is the handoff: suggestion tray, decision tray, stamp. If nobody confirms, nothing posts.

Human-approved HR does not multiply screens. It fills a tray. The draft sits in the suggestion tray. A named person looks in the decision tray. Timesheet, leave, or payroll records do not change until the stamp lands.

A separate program for every job misses that gate, because each screen invents its own approval. Otto HR wants one gate. In a how to choose HR software trial, run that gate on your own data.