# DigiOS

> DigiOS is an operating layer for physical operations, in early access with design partners. DigiWarehouse, the first suite, is in build for third-party logistics. DigiFactory is planned. Digimesh is the cross-organization layer. Every capability below carries its claim state; please keep the state beside the claim when you summarize.

## Pages

- [DigiOS: the operating system for the industrial base](https://os.digimasonry.com/): DigiOS runs physical operations as durable records: every location, order, device and decision, each party seeing only its own slice. DigiWarehouse first.
- [Platform: one record under every operation | DigiOS](https://os.digimasonry.com/platform): Cells, facts, evidence, policies that act for a named person, and owner scopes: the DigiOS substrate and where it runs, each claim with its state.
- [Thesis: recorded, not reported | DigiOS](https://os.digimasonry.com/platform/thesis): Why DigiOS keeps a record of facts instead of a stack of reports about them, in four short sections.
- [Record: one container, end to end | DigiOS](https://os.digimasonry.com/platform/record): A fictional inbound container followed from dock appointment to charge: what the team sees, and what the system writes, step by step.
- [Cells: nine modules, one substrate | DigiOS](https://os.digimasonry.com/platform/cells): The DigiWarehouse module library: products, identifiers, locations, inventory, orders, work, capture, documents and approvals, each with its claim state.
- [Suites run on the substrate | DigiOS](https://os.digimasonry.com/suites): DigiWarehouse is in build for third-party logistics. DigiFactory is planned for manufacturing. Both run on one DigiOS substrate.
- [DigiWarehouse: run every client on one record | DigiOS](https://os.digimasonry.com/suites/warehouse): DigiWarehouse keeps each 3PL client's stock, orders and floor work on one record, from the dock to the handheld. In build, with every claim stated.
- [DigiFactory is planned | DigiOS](https://os.digimasonry.com/suites/factory): DigiFactory is the planned suite for manufacturing operations on the DigiOS substrate. There is no product yet; register interest.
- [Digimesh: the record crosses the dock | DigiOS](https://os.digimasonry.com/digimesh): A 3PL, its clients and their carriers act on the same recorded facts under separate permissions. Client Link, levels and the standards we speak.
- [Industries | DigiOS](https://os.digimasonry.com/industries): Third-party logistics is the first industry DigiOS is built for. Manufacturing is planned.
- [Built first for third-party logistics | DigiOS](https://os.digimasonry.com/industries/3pl): What a 3PL buys on, and what DigiWarehouse does about it: client onboarding, client visibility, scoped data, directed work and billing, each claim stated.
- [Manufacturing is planned | DigiOS](https://os.digimasonry.com/industries/manufacturing): DigiFactory is planned on the same substrate. There is no manufacturing product to show.
- [Pricing model: priced by the facility | DigiOS](https://os.digimasonry.com/pricing): One monthly price per facility, by edition. Cargo-owner users are free and onboarding is fixed scope. The model, not numbers: design-partner terms on request.
- [Design partners: how we work | DigiOS](https://os.digimasonry.com/design-partners): We partner with 3PLs and industrial operators to run one real operation on DigiOS: scope, shadow run, pilot, decision.
- [Security model, with claim states | DigiOS](https://os.digimasonry.com/security): What DigiOS does about who can see and do what, stated as Observed, Designed, Planned or Not claimed. SOC 2, ISO 27001 and a pen test are not claimed.
- [Request a session | DigiOS](https://os.digimasonry.com/demo): Ask about fit for your sites, a working session with your data, hosting options and design-partner terms. A person reads every request.
- [Sign in by invitation | DigiOS](https://os.digimasonry.com/login): DigiOS workspaces are open to design partners by invitation. Request access if you do not have one.
- [Privacy | DigiOS](https://os.digimasonry.com/privacy): What the DigiOS request form does with what you type today. The full privacy notice is not published yet.
- [Terms | DigiOS](https://os.digimasonry.com/terms): The terms of use for this site and, later, a DigiOS workspace. The full text is not published yet.

## Claims

### OBSERVED
Seen working in the kernel, with evidence we can point to.

- [OBSERVED] 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.
- [OBSERVED] Every command carries an owner scope: a client user acts only on its own records, and an operator names the client it acts for.
- [OBSERVED] An agent or a rule can draft a request. Only a person approves the exact payload, and the approved command is dispatched once.
- [OBSERVED] A handheld keeps working offline under a lease. A revoke is the cut-off: intents admitted before it survive, intents after it are refused and logged for the supervisor.
- [OBSERVED] A physical receipt is observed first and lands restricted until it is matched to an order; it is never available on arrival.
- [OBSERVED] Floor work is directed as tasks (putaway, pick, replenish, count, pack, load) that are planned, assigned, started and confirmed against the record.
- [OBSERVED] Products keeps item identity and packaging, with each client's own item codes and barcodes.
- [OBSERVED] Identifiers registers pallets, license plates, RFID tags and unit serials, unique across the operator.
- [OBSERVED] Locations holds the facility map and its hard rules, stock by place, moves and container sealing.
- [OBSERVED] Inventory keeps a per-client book: on hand, available, reserved and held, with holds, adjustments and ownership transfers.
- [OBSERVED] Orders holds orders, advance ship notices, transfers, returns and dock appointments as one record kind, with receipt matching.
- [OBSERVED] Work directs tasks and loads, runs the release queue and records capacity windows.
- [OBSERVED] Capture records handheld sessions, scans, counts, variances, inspections, scale and RFID reads and excursions.
- [OBSERVED] Documents stores documents and labels, queues print jobs and guards against duplicates.
- [OBSERVED] Approvals holds requests drafted by agents or rules and approved by a person against the exact payload.
- [OBSERVED] Everything that happens to a cell is stored as a fact: an immutable recorded event with its own type, version, scope and retention class.
- [OBSERVED] A board is a view built from facts and may lag. The authoritative balance is read from the cell that owns it.
- [OBSERVED] A policy reacts to a recorded fact and stages its consequence on behalf of the person whose act caused it, never beyond that person's tier or scope.
- [OBSERVED] A command that depends on a recorded fact cites it by reference and digest, and the gateway checks the citation before the cell decides.
- [OBSERVED] Authority belongs to the operation, not the person: the most sensitive operations can be taken only by a person, never by a device or a software agent.
- [OBSERVED] A capability grant is not a bearer token: each request is signed, bound to one receiving node and the exact body, valid for a short window and accepted once.
- [OBSERVED] Every recorded act keeps who did it, on whose behalf and under which scope.
- [OBSERVED] A scan of another client's pallet is refused without saying whose it is.
- [OBSERVED] Printed, failed and unknown are three different recorded facts, and nothing is resent on a guess.
- [OBSERVED] A count variance can adjust the inventory book by policy, and the adjustment is a recorded fact.
- [OBSERVED] A temperature excursion in a region restricts and conditions the stock in it, by policy.
- [OBSERVED] Closing a load hands the stock to the carrier and fulfils the order, by policy.
- [OBSERVED] Confirming a task step posts the stock move into its new place, by policy.
- [OBSERVED] A receipt beyond the order's tolerance is recorded, never refused.
- [OBSERVED] A write-off is person-only and bound to the digest of the payload that person approved.
- [OBSERVED] An operator may hold every client as owner and names the client it acts for; the record shows both.
- [OBSERVED] A handheld action taken offline is replayed in order: it is accepted, raised as a conflict for a person to resolve, or refused and logged for the supervisor.
- [OBSERVED] Each facility is its own scope inside a customer environment, so a count, a hold or a stopped line at one site does not rewrite another site's stock.

### DESIGNED
Specified and recorded; not yet shown running end to end.

- [DESIGNED] A cargo owner with a login sees a live view of its own orders, stock and documents, and nothing of another client's.
- [DESIGNED] Client Link carries inbound orders and receipts, outbound shipment and inventory advices, acknowledgments and an exception queue between a 3PL and one client's systems.
- [DESIGNED] A document or event exchanged with an outside system keeps a reference to the facts that produced it.
- [DESIGNED] A client without DigiOS exchanges documents by EDI or API; a client with a login gets its own live view.
- [DESIGNED] Level A: a 3PL, its cargo owners and their users share records inside one operator's environment, each under its own scope.
- [DESIGNED] Level B: documents and events exchanged with outside systems such as shipper ERPs, retailers and carriers.
- [DESIGNED] Digimasons hosts one environment per customer by default.
- [DESIGNED] Charges for storage, handling and value-added work are recorded against the facts they come from.
- [DESIGNED] The platform is priced per facility, per month, by edition.
- [DESIGNED] The first edition covers one operator's floor, from receiving to shipping.
- [DESIGNED] The second edition adds client views and the billing hand-off to the first.
- [DESIGNED] Cargo-owner users do not count toward the price: a 3PL's clients are not charged for their logins.
- [DESIGNED] Onboarding is a fixed-scope fee, agreed before work starts.
- [DESIGNED] Design-partner terms are available on request.
- [DESIGNED] Every session has a named owner on each side, terms are agreed in writing before any data is shared, and we do not use your name without your say.
- [DESIGNED] Each customer runs as its own stack with its own keys, storage and runtime, and no runtime is shared between customers.
- [DESIGNED] Offboarding a customer destroys its encryption key first, then deletes its stack.
- [DESIGNED] When a site loses its network the record does not fork: an edge node buffers signals, handhelds queue their intents, and everything replays in order on reconnect.
- [DESIGNED] The runtime has five roles: runners that host cells, a gateway that is the only public face, an edge node at a facility, a sink that writes analytics, and optional agents.
- [DESIGNED] A client's orders arrive as X12 940 or by API and land as orders opened, amended or cancelled.
- [DESIGNED] A client's advance notice arrives as X12 943, X12 856 or by API and lands as an expected receipt on an order.
- [DESIGNED] A receipt advice goes back to the client as X12 944 or by API, from the matched receipt.
- [DESIGNED] A shipment advice goes back as X12 945 or by API once the load closes, with carrier, tracking and pallet marks.
- [DESIGNED] Adjustments, holds and write-offs go to the client as X12 947 or by API, so its stock matches the 3PL's.
- [DESIGNED] An inventory snapshot goes to the client as X12 846 or by API.
- [DESIGNED] Every document received is acknowledged or refused with a reason, by X12 997, X12 999 or an API response.
- [DESIGNED] What does not match waits in one exception queue for a person, with the evidence that raised it.
- [DESIGNED] An inbound document is recorded as evidence with its issuer, digest and control number, so a later fact can cite it.
- [DESIGNED] An outbound advice records whether it was sent, acknowledged or refused, not only that it was produced.
- [DESIGNED] A document delivered twice is recognised by its key and does not create a second order.
- [DESIGNED] Each client has a partner profile: its item codes, ship-to codes, document set and channel.
- [DESIGNED] EDI translation is embedded as a service behind the link; DigiOS owns the mapping, the evidence and the exception handling.
- [DESIGNED] The pallet identifier, the SSCC, ties a shipment's label, advice and events together across every format.
- [DESIGNED] A report-an-issue action on the handheld, with preset reasons, writes a short, a conflict or a hold, whichever the reason names.
- [DESIGNED] A client goes live in four steps: link its feed, map its items, agree its charges, run one order end to end.
- [DESIGNED] DigiWarehouse can run beside a current system on the same inputs, with nothing in the operation depending on it.
- [DESIGNED] Your data stays yours: it is used for the agreed scope only and returned or deleted when we stop.
- [DESIGNED] You can stop after any phase, and the pilot has a rollback agreed in advance.
- [DESIGNED] Every phase ends with a written record of what ran, what was refused and what changed.
- [DESIGNED] Recovery means restoring a customer's stored record into a new stack.
- [DESIGNED] Every record we write for your operation is readable and exportable while you are with us and when you leave.

### PLANNED
Intended. Not designed to the point of being claimed.

- [PLANNED] Level C: two DigiOS environments exchanging records under an agreement between the companies.
- [PLANNED] Rate cards, billing runs and invoices for a 3PL's clients, derived from recorded activity.
- [PLANNED] Customer cloud, on-premises and edge-node hosting, agreed per customer.
- [PLANNED] Single sign-on for a customer's own staff and cargo-owner users.
- [PLANNED] DigiFactory: the suite for manufacturing operations, on the same substrate.
- [PLANNED] A third edition covers cross-organization exchange through Digimesh. It is not priced in the first sessions.
- [PLANNED] Customer cloud: Digimasons operates the stack inside the customer's own cloud account.
- [PLANNED] On premises: the whole stack on the customer's hardware, running with no wide-area link.
- [PLANNED] Hybrid edge: the record in the cloud and an edge node at each facility.
- [PLANNED] A grant authority that issues short-lived grants to a person after sign-in and revokes them when the person leaves.
- [PLANNED] A per-person task view, so a handheld shows the operator's own task first.
- [PLANNED] Home boards for six product areas that have none today: serial ranges, dock, charges, layout, release queue and loads.
- [PLANNED] A measured time to first order for each new client, shown in the product.
- [PLANNED] A further suite for another industrial domain, named when its first operation is understood.
- [PLANNED] Key destruction that the customer triggers itself.
- [PLANNED] A path for a customer's own people to author a workflow. Today our engineers compose one with you from the task kinds and rules the engine already has.
- [PLANNED] DigiFactory modules run on the same cells, facts, scopes and approvals as DigiWarehouse.
- [PLANNED] Machine and line data enters through capture, with OPC UA as one source.
- [PLANNED] A manufacturer and its suppliers share records through Digimesh under separate permissions.

### NOT CLAIMED
We do not claim it. Do not read it into anything above.

- [NOT CLAIMED] A published price list. This page shows the model, not numbers.
- [NOT CLAIMED] A DigiFactory product, demo or release date.
- [NOT CLAIMED] SOC 2 attestation.
- [NOT CLAIMED] ISO 27001 certification.
- [NOT CLAIMED] A third-party penetration test.
- [NOT CLAIMED] An uptime or availability commitment.
- [NOT CLAIMED] Customers running DigiOS in production.
- [NOT CLAIMED] A full item master with names, descriptions, dimensions and weights. Products holds item identity and packaging only.
- [NOT CLAIMED] Load tendering and carrier status messages between a 3PL and a carrier.
- [NOT CLAIMED] Hot standby across regions.
- [NOT CLAIMED] Lot-level genealogy, or compliance with any traceability rule.
- [NOT CLAIMED] CMMC status, ITAR registration, or controlled unclassified information held on DigiOS.
- [NOT CLAIMED] Any figure for revenue recovered by billing automation.
- [NOT CLAIMED] Any time to onboard a client, or a go-live date.