AssetShop Minerva
Action · Execute, reverse, record
The write side. Kept separate on purpose.
BUILTExecutes to its own ledger today. No ERP adapter is implemented, and this page says so rather than implying it. Not yet verified by a customer.
Nerio never writes to a system of record. That promise is on eighteen pages of this site and it is why a finance team lets Nerio near an ERP. Minerva is where writing happens, under its own name, with its own boundary, so that promise never has to bend.
What Minerva does
It executes what Nerio has evidenced and a person has authorized. An authorized request becomes a purchase order or an invoice in Minerva's ledger, numbered, sealed into your organization's hash chain, and exportable to your systems. A request that was not authorized cannot be executed by anyone, because Minerva reads the authorization from the record rather than taking the caller's word for it.
It also carries documents between organizations. A purchase order issued by one tenant travels to another, is visible to both and to nobody else, and can be accepted or disputed on the record.
The five rules the code enforces
The authorization chain is read from the record, with the policy version and every clause that routed it. Unapproved, rejected, or unknown requests are refused with the reason.
The compensating action is recorded at the moment of the write, before the write is confirmed. A reversal applies what was recorded then; it is never invented afterward.
Ten thousand dollars by default. An executor and a countersigner, who cannot be the same account and cannot be the person who raised the request.
Executing the same approved request twice is one execution and one document. A retry after a timeout cannot double an order.
Each entry names the hash of the one before it, per organization. The chain is verified as it is read; an altered or missing entry is reported with its position, never served as intact.
Each rule is a test on the service that fails if the rule is removed. Thirty-four tests pass at the build this page describes.
What writes where
| Adapter | Writes to | Status |
|---|---|---|
| Ledger | Minerva's own book of record. The document exists, is numbered per organization, and exports. | BUILT |
| ERP | SAP, NetSuite, Dynamics and others. | Interface only. Not implemented. Refuses with 501 rather than pretending. |
| Business to business | Another organization's Minerva inbox, with a document hash. | BUILT |
When an ERP adapter ships it will be listed here with its status. Until then, the export is the bridge, and the ledger is the record.
Tenancy
Minerva acts for an organization, not a person. Membership is a record with a role on it, and every read and every write is scoped to the caller's organization. Roles: owner, admin, buyer, controller, member. A buyer can execute; a controller can countersign and reverse; nobody can countersign their own request or execute what they countersigned.
Compliance, stated exactly
Minerva implements controls that a SOC 2 or ISO 27001 audit would examine: separation of duties, dual control, immutable chained records, least-privilege roles, reversibility, and idempotency. It does not hold a SOC 2 report, an ISO certificate, or any attestation. Those are an auditor's signature, and no software can grant them to itself. The controls document in the operator kit maps each control to the evidence an auditor would ask for.
Personal data in Minerva is an account id, a role, and the documents an organization chooses to issue. Account deletion on the estate erases the account's own records; documents issued on behalf of an organization remain the organization's, as a purchase order remains a company's record after the buyer leaves.
How Nerio and Minerva connect
One direction. Nerio evidences and a person authorizes; Minerva reads the record and executes. Minerva never writes into Nerio, and Nerio never calls Minerva. The join is the request id, and the proof is the policy version and the clauses on the EOS record that Minerva quotes when it executes.
See Minerva on the platform Start an evaluation Read the trust page
Film
Minerva acts.
Two and a half minutes on the write side: the five rules, the chain, the reversal recorded before the write, dual control, envelopes between organizations, and what is live against what is only built.
Honos: who may authorize what →
Fides: what may cross a boundary →
Forculus: the door between the record and the machine →
The EOS family