Most ERPs lie to themselves. Six tables claim to be the truth and a nightly job tries to stop them from arguing. We did the boring thing instead. We built one log. Everything else is a view of it.
Open the database behind any ERP you've used. You'll find it. A table of invoices. A separate table of stock movements. A separate ledger. A separate AR balance. Each one is a source of truth. Each one is wrong, in its own way, on a long enough timescale.
So nightly, weekly, quarterly, somebody runs a reconciliation job. It writes corrections to make the lies agree. The job has a name. The CFO knows the name. The auditor knows the name. Everyone has learned to live with it. It's fine. It's normal. It's how grown-ups do business.
It is not how grown-ups do business. It is technical debt the accounting profession was forced to inherit because nobody built the alternative. We built the alternative.
The spine is small enough to explain on one page. Most of the engineering is in making sure it stays that way.
The architecture isn't the product. The architecture is what makes the product possible. Here's what you actually get from it.
Every report can be re-asked at any point in the past. “What was our AR aging on March 31?” is a query, not a project. Audit season stops being a season.
When sales says you sold ten of something, finance booked the revenue, the warehouse shipped it, and the GST return reflects it, there is one event behind all four. They cannot disagree.
Every decision the system made (or an AI agent proposed) is in the log, with the state it saw and the rule it followed. You can re-run any moment. You can debug any moment. You can explain any moment to anyone, including yourself in six months.
When something needs to be undone, the spine records the undoing. The original event stays. So does the correction. So does the reason. Your books carry their own history, not a sanitised version of it.
Closing March is not a fortnight of reconciliations. It's an event that locks the views and snapshots them. Reopening is an explicit event too, with audit. No more mystery edits to last quarter.
A new report, a new compliance return, a new business rule — all of them are new views and new invariants over the same log. We don't migrate data to add a feature. We just look at it differently.
The whole reason to build this in 2026 is that an AI agent can now do most of the operational work in your business. The reason it doesn't, today, is that nobody has built a system it can actually work in safely.
On a normal ERP, an agent has the same powers as a human clerk and the same way to misuse them. It can post a journal entry that breaks the books. It can update a master record in a way that silently corrupts a year of history. It can do the right thing nine times and the wrong thing once and you find out at audit.
On the spine, an agent can propose events. The kernel either accepts the event (because it satisfies every invariant) or rejects it (because it doesn't), and tells the agent exactly which rule it broke. The agent re-plans. The kernel checks again. There is no door open for a quiet mistake. The worst an agent can do is fail loudly.
This is what “built for AI” actually means. Not a chatbot in the sidebar. Not a summary at the top of a dashboard. A runtime where an agent can attempt anything, and the spine will only let through what's valid.
Concretely. ACME Pvt Ltd in Pune sells 1,000 widgets to a buyer in Bengaluru at ₹100 each. Inter-state, IGST 18%, invoice value ₹1,18,000. Above the e-way bill threshold, above the e-invoicing threshold. Five events on the log. Everything else falls out.
PaymentReceived event. AR drops to zero. Cash goes up. Books still balance. Accepted.It isn't a database wrapper. It isn't a workflow tool with extra steps. It isn't an opinion about which fields belong on a sales order. It's a runtime — small, total, refusing to forget — that every business operation, human or AI, has to go through.
On top of that runtime, we ship the things you'd expect from an ERP: sales, purchasing, inventory, accounting, payroll, GST, e-invoice, e-way, MSME 45-day, multi-entity. They're modules in a registry. They're small because the runtime does the work.
If you want to know what those modules look like — Books and Compliance are the next two pages.
Twenty minutes is enough. We'll bring a real account, real events, a real audit replay. Your CA can join. Your CFO can join. We'll answer the awkward questions.