Dualiscapax Start $0 Simulation
← Lander Ask Iris Residual Edge Research À La Carte Runtime Onboard
03 · Edge Computing

What you see.

A seat on your device. A workbench that loads locally. A report that never leaves your machine unless you choose. Dualis looks like software that sits next to your books — not a portal that sucks them into our cloud.

People already know what Dualis does (stop money leak). This page is how and where.

How

Architects of an abstract layer — not the plant.

DualisCapax designs a software abstract layer that measures both poles of Residual Law (waste vs residual / walk-back), runs DCLM on-device, and puts Iris as sensors at the seat. We are not builders of the water plant, the clinic, the kitchen, the bus depot, or the hardware. We attach math to systems you already own.

Where

Where we operate — and where we do not.

Where we operate

On the customer's edge/device and in the abstract model layer above real systems. Measurement lives where the books live. The report stays on-device. Outbound, if ever granted, is receipt hashes — not books.

Where we do not

We are not the utility, the hospital, the team, the books, or a cure. Dualis servers do not get customer books. Simulation is not treatment. We never proclaim cures.

Edge invariant (locked)

Customer data/books never touch Dualis servers. Optional auditors may receive poles + receipt hashes only — never the sheet. Dualis is not a cloud vault of customer data.

Math · model

Residual Law poles — plain language.

Two poles at the point of production: waste (leak still open) and residual / walk-back (what you can recover). Dualis models that gap. We do not invent fake closed-form miracles — the structure is conceptual and auditable.

Waste − Recoverable → Leak still open
Dualis share ← only from verified walk-back

If the walk-back is not verified in your books, Dualis is owed nothing. Look and measure stay free.

  1. DCLM Layer [0] — veto first (NO_FORCE / HOST_SAFE), then measure. Unsafe or forced paths fail closed.
  2. Receipt hashes vs books — the books stay on-device; any optional outbound signal is a hash of a receipt, not the ledger itself.
  3. Optional auditor 2-of-3 — poles-only attestation: auditors can see that both poles were measured and that a walk-back matched, without reading customer books.
Product laws: customer data/books never touch Dualis servers; report stays on-device; outbound = receipt hashes only if ever granted.
Next · on your device

Then the workbench.

When you are ready to run the abstract layer on hardware you control:

Open on-device runtime → Start $0 seat → Fuel packs →