Skip to content
DigiOS.
/THESIS

RECORDED, NOT REPORTED.

Why DigiOS keeps a record of facts instead of a stack of reports about them, in four short sections.

[01]

SOFTWARE THAT OVERWRITES.

An order is edited, a count is replaced, a status is flipped, and the earlier state is gone unless someone remembered to log it. Ask what the stock was last Tuesday and you are reading a guess.

A record that can be edited has no history of its own, so the history is rebuilt from logs kept beside it, and a log is only as complete as the people who remembered to write it. A DigiOS cell changes only through its own commands, one writer at a time, and each change is stored as a fact.

OBSERVED

[02]

RECORDS, NOT ROWS.

A row holds the latest answer. A record holds the answer and what led to it: who wrote it, under whose scope, citing which earlier fact. DigiOS keeps the second kind.

Because every fact names its author, its scope and the facts it cites, a question about last Tuesday has an answer that can be checked. A board that shows today's number is a view built from those facts, and it says how current it is.

OBSERVED

[03]

EVERY PARTY, ONE RECORD.

A 3PL, its client and the client's carrier need the same facts, and none of them should hold the others' keys. Each reads its own slice of one record; nobody reconciles copies.

A client does not need the 3PL's keys to see its own stock; it needs a scope. An operator that serves many clients holds all of them and names the one it acts for, so the record shows both.

OBSERVED DESIGNED

[04]

AUTHORITY WITH A NAME.

A system that acts needs an author. In DigiOS every consequence names the person whose act caused it, and an agent that drafts a change cannot approve it.

The most sensitive operations are person-only by their nature, so a device or a software agent cannot take them even if it holds a grant. A rule that reacts to a fact acts on behalf of the person whose act caused it, and never beyond that person's tier or scope.

Recorded is the difference between a system that says and one that can show.

OBSERVED OBSERVED

/LIMITS

WHAT WE DO NOT CLAIM YET.

Each of these is stated as it is. Each changes only when evidence does.

  • Customers running DigiOS in production.— NOT CLAIMED
  • SOC 2 attestation.— NOT CLAIMED
  • ISO 27001 certification.— NOT CLAIMED
  • CMMC status, ITAR registration, or controlled unclassified information held on DigiOS.— NOT CLAIMED
  • A third-party penetration test.— NOT CLAIMED
  • An uptime or availability commitment.— NOT CLAIMED
  • 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
  • Lot-level genealogy, or compliance with any traceability rule.— NOT CLAIMED
  • Hot standby across regions.— NOT CLAIMED