DigiOS runs physical operations as durable records: every location, order, device and decision, each party seeing only its own slice. Written at every scan, count and handoff.
DigiWarehouse, the first suite, runs third-party logistics.
/PLATFORM
Underneath every suite sits the same small set of ideas: cells, facts, scopes and evidence. A new suite reuses them instead of rebuilding them. Step through the nine modules.
Items, packs and barcodes, kept per client.
HOME BOARD · TYPE INDEX
Pallets, plates and serials, unique across the tenant.
HOME BOARD · OPEN BINDINGS
The warehouse map and the rules that guard it.
HOME BOARD · CONTENTS
Each client's book: on hand, held, reserved.
HOME BOARD · AVAILABILITY
Orders, notices and dock appointments as one kind of record.
HOME BOARD · ORDER BOARD
Tasks a person can pick up and a system can check.
HOME BOARD · TASK BOARD
Scans, counts and readings, including those taken offline.
HOME BOARD · EXCEPTION QUEUE
Labels and print jobs, with what printed and what did not.
HOME BOARD · DOCUMENT INDEX
A drafted change, a named approver, one dispatch.
HOME BOARD · PENDING APPROVALS
/SUITES
A suite is a set of jobs on the shared record. DigiWarehouse, in build, takes a 3PL from receiving to shipping; DigiFactory is planned; the next suite is one you could name.
For third-party logistics: each client's stock, orders and work on one record, from the dock to the handheld.
The same record, on the line: work orders, routings and line floors on the same substrate. There is no product yet.
One you could name. We start from the operation you would bring and the records it already keeps.
/COMPARE
Most operations hold the same fact in several systems and then meet to decide which one is right. DigiOS holds it once.
| CAPABILITY | IN A TYPICAL STACK | DIGIOS |
|---|---|---|
| RECORD MODEL | Copies in each system, reconciled by hand. | One record; boards read from it. OBSERVED |
| CLIENT VISIBILITY | Exports and a nightly file. | Each client's own slice of the same record. DESIGNED |
| AUTOMATION AUTHORITY | A service account that can do whatever its key allows. | Agents draft; a named person approves the exact payload. OBSERVED |
| INTEGRATION | One mapping per client, built point to point. | One canonical contract; EDI and REST in, kept as evidence. DESIGNED |
| OFFLINE FLOOR | Scans lost or re-keyed after an outage. | Leases and queued intents; conflicts shown and logged. OBSERVED |
| AUDIT | A log kept beside the data. | The facts are the data and each names who acted. OBSERVED |
Most operations run on three copies of the same fact and a meeting to decide which one is right. A fact that is written once, with a name and a time, stops needing the meeting. One record is the difference between an operation that reconciles and one that negotiates.
/DIGIMESH
A 3PL, its clients and their carriers act on the same recorded facts, each under its own permissions. Nobody mails a copy to be reconciled.
Each client reads its own slice of the 3PL's ledger: its items, orders, stock and documents, and not a line of anyone else's.
Every document that leaves cites the facts behind it, and every one that arrives is kept as evidence. Disputes are settled by following the citations.
A client's act can cause a consequence in the warehouse, and the consequence carries the client's name and no more authority than the client has.
/3PL
A 3PL sells a promise about other people's goods. DigiWarehouse starts from what that promise needs: each client's records kept apart, each client able to check them and, once billing is built, every charge tied to recorded work.
| WHAT A 3PL WEIGHS | WHAT DIGIWAREHOUSE DOES | STATE |
|---|---|---|
| LABOR: TEMPS, TURNOVER, RAMP-UP | THE SYSTEM DIRECTS THE WORK. | OBSERVEDPLANNED |
| INTEGRATION WITH THE CLIENT'S ERP AND EDI | KEEP YOUR ERP. FIX THE HANDOFF. | DESIGNEDDESIGNED |
| CLIENT VISIBILITY | THE CLIENT SEES THE SAME FACT. | OBSERVEDDESIGNED |
| BILLING ACCURACY AND DISPUTES | A CHARGE NEEDS A FACT. | DESIGNEDPLANNED— NOT CLAIMED |
| OFFLINE FLOORS | THE FLOOR KEEPS SCANNING. | OBSERVEDOBSERVED |
/CLAIMS
Every capability on this site wears one of four states: observed, designed, planned or not claimed. Observed means a record, a repo path or a test run you can ask to see.
33
CLAIMS ON THIS SITE
41
CLAIMS ON THIS SITE
19
CLAIMS ON THIS SITE
14
CLAIMS ON THIS SITE
Seen working in the kernel, with evidence we can point to.
Specified and recorded; not yet shown running end to end.
Intended. Not designed to the point of being claimed.
We do not claim it. Do not read it into anything above.
ONE CLAIM FROM EACH STATE, AS THE RECORD STATES IT
A location, an order, a device or a decision is kept as a cell: a record with a declared key and owner, changed only by its own commands, each change recorded as a fact.
evidence · repo-path · erp/ontology/README.mdevidence · record · agentstore:digios-erp.research/freeze-d-erp-149A cargo owner with a login sees a live view of its own orders, stock and documents, and nothing of another client's.
Level C: two DigiOS environments exchanging records under an agreement between the companies.
A published price list. This page shows the model, not numbers.
We take one real operation and run it on DigiOS beside your own process, then compare. You decide each step, and you can stop at any of them.
One client's order feed. One inventory export. We load both and open that client's view beside yours, so you see what the client would.