Specification before code
Data model, transaction contracts, status lifecycles and accounting rules are written and reviewed before the code that depends on them exists. A mechanism is specified and certified before a line of code ships against it.
HomeAbout
About
Corva is a new ERP for distribution and wholesale, in active development. This page is what we are building and why, not a company history we do not have yet.
Why
Ask a distributor where their ERP hurts and the answers rhyme. Stock on the screen that is not on the shelf. A month-end spent reconciling the warehouse against the books. An adjustment nobody can explain. A shipment invoiced for something else. None of these are exotic failures. They are what happens when a system lets records be edited independently of the events that should have changed them.
The root cause is architectural. If a screen can update a quantity directly, then the quantity is an opinion. If accounting is a separate step that reads operational tables later, then the books are a reconstruction. Both problems are fixed in the same place: make every business action a single controlled transaction that writes state, ledger, audit and accounting together, and give it no alternative path.
That is the whole idea behind Corva. Everything else on this site (the modules, the accounting engine, the isolation model) is a consequence of taking it seriously.
Who it is for
Corva also runs service businesses from the same core, with jobs and time in place of goods movement. Goods distribution remains its home.
How we build
An ERP is a system of record. The cost of getting it wrong is not a bad afternoon, it is a year of distrusted data, so the discipline is deliberately heavier than a typical product's.
Data model, transaction contracts, status lifecycles and accounting rules are written and reviewed before the code that depends on them exists. A mechanism is specified and certified before a line of code ships against it.
Nothing is considered done because its author is happy with it. Every change is reviewed against a single standard by someone who did not write it.
The rules that matter most (one write path, tenant context required, one balanced posting, no hard deletes) are checked automatically on every change, not left to good intentions.
We would like to hear how your operation actually runs. It is the most useful input we can get right now.
hello@corvaerp.com