V.L. has to live somewhere.
It lives in the VAM.
Validated Learning is the doctrine. The VAM is the embodiment. Every diesel-electric asset in the oilfield already runs on an Engine Control Module — a sealed embedded computer that knows one job and is trusted because of its protocol, not because anyone audits its source. Five Star ships the same shape for learning: the VAM, Validated Asset Module. One per pump, drill, ESP, or subsea tree. V.L. at the asset, not in the cloud.
Same shape. Different job.
Your CTO already accepts the idea of a sealed module that knows one job, lives on the asset, and is trusted because of its protocol — not because anybody audits its source. The VAM occupies the same mental slot, one layer up.
| ECM | VAM | |
|---|---|---|
| What it is | Engine Control Module | Validated Asset Module |
| Where it lives | On the engine | On the asset |
| One job | Read & run the engine | Read & learn the asset |
| Protocol | SAE J1939 over CAN | Validiti substrate |
| Form factor | Sealed embedded module | Sealed embedded module |
| Trust model | Sealed binary, vendor accountability | Sealed binary, signed integrity |
| Human surface | Dash console | Operator tablet |
| Vendor lock? | No (open protocol) | No (operator owns the patterns) |
Four things, always.
Listen to the asset native
Reads sensor packs, the asset's own ECM stream, crank-angle encoders, fluid-end pressures, vibration packs — at the rates the asset emits them, not at the rates a SCADA gateway downsampled them to.
Store frequency, not gauges
What the asset does is stored as it happens. What it did yesterday is queryable today. The pattern that preceded last quarter's failure is recognizable when it shows up again next month.
Asset-vs-asset, crank-aligned
Bores in the same fluid end at the same crank angle must produce identical signatures. The VAM stores the comparison natively, so the bore that drifts is the bore that's about to break — before any single-channel threshold trips.
Every claim is provable
Every record the VAM produces is signed by construction. Court-defensible by default. Tradeable as a pattern-marketplace asset when the operator chooses. Forgettable on demand, verifiably.
One module shape, four chains.
The VAM is one architecture, four sealed firmwares. Each chain's VAM is tuned to the asset it lives on. Same module shape; different learned-pattern library.
Frac-pump VAM
Lives on every frac pump. Reads the pump's ECM (Cat 3512 / Cummins QSK60 J1939), the crank-angle encoder, the per-bore pressure pack, the fluid-end vibration pack. Compares bores at the same crank angle. Phase 1 · Wave 1 open.
Drilling VAM
Lives on the rig. Reads MWD / LWD telemetry, mud-pump ECMs, top-drive controllers, the surface-system bus. Cross-rig pattern marketplace turns first-mover formation discoveries into signed tradeable assets. Phase 2.
Artificial-lift VAM
Lives per well. Reads ESP VFD telemetry, rod-pump controllers, gas-lift compressor ECMs, plunger sensors. Cross-well lift-pattern recall — what worked on well 47 last year, queryable against well 89 today. Phase 3.
Offshore / subsea VAM
Lives at the asset (surface stack or subsea control module bridge). Reads SCM telemetry, tree pressures, ROV vehicle data, umbilical-side state. One avoided ROV trip per asset per year covers the license fee. Phase 4.
The VAM is the compute.
The tablet is the surface.
Same shape as an engine has a dash console: sealed compute below, human-readable surface above. The operator's tablet is how a human sees what the VAM has learned.
Field-rugged tablet. One per active position on the pad. Shows what the VAM is watching right now, what it's noticed recently, what it wants the operator to know. Suggests, never actuates. The operator decides. The VAM is the witness, not the driver.
- Multi-tablet safety fanout — one event on one VAM raises the right alarm on the right tablet for the right operator's role.
- Sealed binary on the tablet too — source never crosses the firewall. Same trust pattern as the VAM itself.
- Ambient initiative — the VAM tells the tablet what matters; the tablet doesn't have to be polled.
- Two-question field setup — tablet pairs with VAM in under five minutes by a field tech who's never seen the system before.
Three tiers, one shape.
| Tier | Role | Lives where |
|---|---|---|
| VAM | Per-asset sealed compute. Reads & learns one asset. | On the asset (pump, drill, ESP, tree) |
| Pad aggregator | Coordinates a group of VAMs. Cross-unit comparison happens here. | On the pad (frac van / rig floor / battery) |
| Network layer | Signed-pattern marketplace + cross-fleet substrate. | Five Star network (every licensed operator) |
The VAM is the ECM's neighbor at the bottom of the stack. The tablet is the dash console above it. The pad aggregator is the operator station that watches a fleet. The network is what makes a first-mover pattern tradeable. One architecture, top to bottom.
How a VAM gets to your asset.
- Sealed binary. The VAM ships as a sealed signed firmware. Source never crosses your firewall, your customer's firewall, or the asset's perimeter.
- Two delivery paths. Either Five Star supplies the VAM hardware through the licensed supply chain, or you bring conforming hardware and Five Star installs the binary. No self-install path. The integrity of the seal is the integrity of the seal.
- Pacta42-LoRa surface uplink. 902–928 MHz license-free band for VAM-to-HQ telemetry. No cell-tower contract, no satellite subscription, no per-message fee.
- Field upgradable. New learned-pattern libraries arrive as signed sealed-binary updates. Each VAM verifies the signature before accepting the swap.