Product

An operating system that keeps authority with the operator.

CashewOS runs a local decision core, deterministic policy, kernel enforcement and a signed audit ledger in one system you install on your own host.

The argument

Why the operating system matters

Permission is a system responsibility.

A useful proposal and an authorized action are different things. Policy admits or refuses each proposal, and the kernel enforces the result.

The decision path stays on the machine.

The decision path needs no cloud model service. Operators work at the console or over SSH, and supported requests resolve into bounded proposals.

Evidence travels with the decision.

Policy outcomes land in signed, hash-chained records. Replay a ledger on this page, edit a record and watch verification refuse.

Decision core

A decision core Orbin trained for the operating system.

Orbin trained the decision core from scratch for this system. It ranks only the actions the system offers and generates no open text. Policy decides, and the kernel enforces.

Trained from scratch

Orbin built the training data and trained the model from the first step. Its provenance is reviewed with design partners under NDA.

Bounded by the system

Operators keep the ask command. Exact requests resolve deterministically, and the model ranks only the actions the system offers.

Policy decides, kernel enforces

The model holds no permissions. Policy admits or refuses each proposal, the kernel enforces the result, and the ledger records it.

The decision core can still rank a permitted action that is not the one the operator meant. It adds no authority. Every action it can rank comes from the system's compiled registry, policy admits or refuses it, the kernel enforces only the permission that action carries, and every admitted action is recorded with its request.

Decision responsibilities

Where refusal is enforced

CashewOS separates proposing an action, deciding whether it is allowed, enforcing authority and recording the outcome.

LayerResponsibilityScopeResult
Decision coreRanks candidates the system suppliesLocal executionCandidates defined by the systemProduces a typed proposal.
PolicyEvaluates the proposed actionDeterministic rulesThe admitted operating contractAdmits or denies the proposal.
KernelEnforces capabilitiesSystem boundaryThe authority assigned to the callerRejects operations outside that authority.
AuditRecords decisionsTraceable outcomesRequest and decision correlationProduces records for independent verification.

Deployment

One signed appliance on your KVM host

CashewOS ships as one signed virtual appliance for Linux KVM hosts. It runs with a small footprint and keeps its state across power loss.

  • Signed imageEvery appliance release is signed, and verification refuses an unsigned or untrusted image.
  • Your networkBridged IPv4 and IPv6, administration over SSH with named operator roles, and a default-deny firewall.
  • The same core on every nodeEach appliance runs the same decision core and the same signed audit, with policy scoped to your operation.
  • Your hardwareHardware options are settled with each partner during the pilot.

Release

CashewOS 0.1.0, technical preview

Offered to design partners for controlled evaluation. Commercial releases follow the evaluations that qualify.

  • Reproducible buildsThe same source produces the same image, and each release ships an SBOM.
  • Clean dependency auditVersion 0.1.0 passed a dependency audit with no known vulnerabilities at release, and each release ships its audit result.
  • Signed artifactsVerification refuses to run without a trusted key. Evaluation releases use development signing keys, and production custody is agreed with each partner.

Verified in the technical preview engineering record. Design partners rerun every check on their own host during source inspection.

Under NDA

The engineering detail, for the people evaluating it

The operator guide, the command reference, the audit procedure, the appliance profile and the supply-chain dossier are shared with design partners under mutual NDA. See the documents.

Design partnership

What would you put under a defined operating policy?

Bring a workflow from your NOC, enclave or regulated environment. We will define an evaluation around the actions, permissions and evidence your team needs.

Request design partnershipA person at Orbin replies within two business days.