Why we fuse

Fusion lens

Anduril Lattice and Project Maven fuse sensor feeds across domains (air, land, sea, signal) into a single decision surface. We do the same thing for business operations. Every fact in ValOS shows up in five lenses simultaneously — the vertical it belongs to, the interfaces it crosses, the physical-world hooks it touches, the company-lens variant, the capability binding, and the Missions it participates in. One fact, every dimension visible.

8 interfaces

How facts enter and leave the system.

I3 Site · I5 Engagement · I6 Operator · I7 Document · I8 Schedule

Physical AI hooks

Where the system reaches into the physical world.

val-grid endpoints · OT / IoT · kiosks · field technician mobile

Company-lens variant

Per-deployment / per-vertical specifics, isolated from substrate.

MSP · QMS · manufacturing · collections · field-services · trust-reconciliation

Capability binding

What an engine is allowed to do — ABAC-enforced.

Reads · Builds · Grows · Evolves · Computes

Missions

Multi-agent orchestration. Decision Cards carry the audit chain.

mission.forge.pipeline.spawn.v1 · mission.forge.repo.create.v1 · ...

What-1

One fact, five lenses.

A debt-recovery payment arrives. The system sees it as: I5 Engagement · CL collections · CB Reads · MS settlement.v1. Every downstream surface filters on the lens it cares about.

What-2

Cross-cut by design.

Verticals stack (Ring 3). Lenses cross-cut every vertical. MSP + collections + field-services all use the same I-numbers, the same Capabilities, the same Mission contract. New verticals inherit the cross-cuts for free.

What-3

Audit chain through fusion.

Every Mission writes a Decision Card. Every Card carries its lens tuple. Replaying the fact stream + cards reconstructs exactly who did what across which lenses — institutional knowledge as substrate.

The full integration matrix

Every vertical × every lens, with cross-cut references

open matrix →