Our own payroll is the test.
Payroll runs on Anusuya Workspace every month, for a real workforce across more than one legal entity. Those salaries belong to the people we work with. An amount that is wrong does not stay inside the software: it reaches someone who was depending on it.
That is why correctness in money and people records is treated as a hard requirement. We have made the same commitment we ask a business to consider when it puts its own records here. The work matters before anyone else sees the product.
More than one legal entity is part of our working context. We needed one workspace across both, so that is how Anusuya Workspace was built from the start.
The record carries the work.
Our people and customer work belong in the same business context as the amounts they give rise to. A person joining the company should not become a different record when their salary is due. A customer conversation should still make sense to the colleague who carries it forward.
Employment documents are generated from the person’s record rather than typed again. The name, the joining date and the details behind the document belong to that person. Having someone copy them into another draft is another opportunity for the record and the letter to disagree.
The three areas of the workspace describe this continuity. They are the people who work with us, the customers we work for and the books that record the obligations of both.
A planned cutover for the books.
The books are moving onto Anusuya Workspace. Their cutover is dated and planned rather than rushed. Running in production does not mean pretending that every existing record has already moved.
An existing book of record carries work that has already happened. Bringing it across is its own piece of work, with a beginning, a point of transition and responsibility for what comes through. It deserves the same care as the records we create tomorrow.
We describe that stage plainly because it is part of running a business on software. Payroll is running monthly. The books have a planned cutover. Both belong to the commitment we have made to use what we build.
The responsibility stays close.
This is the ground from which we write about what a wrong salary means and about leaving someone with a way forward. These are standards we have to answer to in our own working day.
The software is used by the people who built it, every working day, and that is why correctness is treated the way it is.