Flow — Exact Whole-Field Control Software

Large control fields are usually treated as collections of independent channels. Flow treats the complete field as one addressable state. It identifies the active condition, derives a sparse whole-field action, carries that action through recursive transport, and advances the state only after the corresponding work is acknowledged.

The technology unlock is the Arithmetic Quvit: a finite-field register whose routing, projection, survival, and in-transit actions are derived from the state itself. The Recursive Transport Operator supplies exact route composition. Together they turn one control law into three working software systems: a microfluidic edge controller, a carbon-capture swing-bed controller, and a whole-build solidification controller.

Lattice OS · recursive full-field control

0.6 seconds vs 134 years

Same 256 decisions. Same outputs. 79 octillion addressable field sites.

Log-scale comparison. A dense scan reaches 80.6 seconds and the 128-gigabyte memory limit at 68.7 billion field sites. Lattice OS performs the identical control work in 0.24 seconds there and continues to 79 octillion sites in 0.60 seconds. A perfect dense scan using the combined TOP500 requires at least 134 years at the final extent. — **Five common sizes produced byte-identical outputs.** Measurements used the same Ryzen 9 7950X consumer PC with 128 GB RAM. TOP500 is the published ranking of the world’s 500 fastest supercomputers; the June 2026 systems deliver 18.73 exaflop/s combined. The blue line gives those machines every advantage: one address checked per sustained HPL flop, unlimited memory, and zero communication, synchronization, or control overhead. Exact readings and audit data.

Three data sheets — engagements are direct

μF

Microfluidics

ADDRESS · derive · route · acknowledge

Cloud-independent sparse control for very large active-matrix address spaces. The registered 256×256 fixture round-trips every address uniquely; the standalone edge runtime carries fixed-size packets and bounded state rather than an array-sized bitmap.

1,300,077 commands/s on the registered host loop, up from 51,395 after the same workload was reduced to its one-sparse form. The benchmark measures the delivered software path, end to end, on one host fixture.

[ engagement-direct ] View data sheet →

CO₂

Carbon capture

OBSERVE · load · regenerate · close the ledger

State-derived control for a two-bed vacuum-swing capture process. Each bed transition is replayed through the same exact control path before the simulated plant advances, with separate CO₂ and H₂O conservation ledgers.

21 swaps instead of 29 at the same simulated 2.000 mmHg nominal peak. Under a permanent capacity fault, state-derived control held the fixture at 2.000 mmHg where the timed controller reached 2.629979 mmHg.

[ engagement-direct ] View data sheet →

Whole-build additive manufacturing

SENSE · repair · project · transfer

Conservative solidification control over the entire build: integer enthalpy, occupancy, melt and first-solidification history, antisymmetric face exchange, and explicit source/sink ledgers. The controller acts on the build as one object, not as a queue of isolated voxels.

44.70–48.28% fewer computational ticks than the fastest admissible fixed baseline across four declared software articles, with zero registered quality-ledger violations. A blind actuator-envelope article reached 49.09%.

[ engagement-direct ] View data sheet →

The common machine

The three products do not share a dashboard. They share a control invariant: observation becomes an exact class; the class selects sparse work; acknowledged work advances one exactly-once successor. Recursive transport lets the same state carry its source, direct action, and accumulated route history without expanding into the full field. That is how the edge runtime remains small while the logical address space grows.

[ direct engagement — vetted partners ] Engage by email →

Tell us the field-control problem that becomes too large, too slow, or too brittle when every channel is treated separately. A scoped, direct conversation follows — no tiers, no funnel.

tony@fancyland.net

— Tony Matos