Vendor and Product Reality

Built Robotics, founded in 2016 and headquartered in San Francisco, ships the Exosystem retrofit, a sensor-and-compute kit that mounts onto OEM excavators (Caterpillar, Komatsu, and comparable classes) and converts them into autonomous trenchers and pile drivers. Its publicly described product line includes a robotic pile-driving system aimed at utility-scale solar construction and autonomous trenching for fiber, gas distribution, and related earthwork. The company positions its retrofit approach against OEM-native offerings such as Caterpillar's Cat Command and Komatsu's FrontRunner. Specific customer names, deployment sizes, and corporate transactions are treated here as external market context rather than as established fact, because they are not the subject of this disclosure and are not needed for the architectural comparison that follows.

The technical stack is conventional autonomy: GNSS-RTK localization, multi-modal perception (LiDAR, stereo cameras, radar), a path planner producing trajectories for the excavator's hydraulic actuators, and a supervisor app over LTE that lets a single operator oversee a fleet. Geofences define the operating envelope; a watchdog stops motion if a person is detected within a defined buffer. The site model is updated from machine-collected scans, and dig plans are uploaded as parametric tasks (trench geometry, pile coordinates, target depth) rather than teleoperation primitives. Customers report meaningful productivity gains on repetitive earthmoving tasks where operator fatigue and labor scarcity dominate the cost structure.

What the product does not include, and what is not currently a marketing claim, is structural authority gating of the hydraulic actuation itself. A Built excavator executes its planned trajectory because the planner emitted it and no watchdog interrupted; it does not execute because a credentialed admissibility evaluation against a published policy taxonomy returned a graduated authorization to proceed. That distinction is invisible to a customer measuring productivity. It is not invisible to an underwriter, an OSHA investigator, or a utility owner-operator after a strike on a buried medium-voltage cable.

The Architectural Gap

The gap is a binary actuation posture wrapped around a continuous physical risk surface. The Built planner produces a trajectory, the watchdog gates it on a small set of safety conditions (presence of a person, geofence breach, comms loss), and the hydraulics execute. The decision space is permit-or-suppress; there is no graduated mode set in which the same observed condition can produce a continue, defer, refuse, or partial-execution outcome based on credentialed authority class, evidential weighting of the inputs, and a structured admissibility evaluation. This is the same architectural property the governed-actuation disclosure treats as central for any cyber-physical actuator operating under harm-minimization and reversibility scrutiny.

Construction sites multiply the consequence. A single excavator interacts with buried utilities recorded in 811 locates of varying age, surface workers whose presence is not always within sensor range, geotechnical conditions that change under rain, and adjacent equipment whose movements are not part of the autonomy stack's world model. A binary stop-or-go gate, no matter how well-tuned its perception, cannot express the policy distinction between "credentialed locate confidence high, proceed at full rate," "locate confidence stale, proceed at reduced depth with continuous resistance monitoring," "ground-penetrating radar return ambiguous, defer pending second-source confirmation," and "underground utility credential missing, refuse irrespective of sensor consensus." Without that distinction the operator is forced to encode policy into the geofence and the dig plan rather than into the actuation gate, which means policy violations look identical to planning errors in the audit record.

The structural property the vendor lacks is governance-credentialed graduated commitment with post-actuation verification re-entering the chain. Built can add safety features indefinitely without acquiring this property, because the property is not a feature: it is the shape of the actuation pathway.

What the AQ Primitive Provides

The governed-actuation primitive specifies that every actuator commitment, every hydraulic motion in the Built case, pass through a five-stage chain. First, every input that bears on the commitment arrives as an authority-credentialed observation: the 811 locate is signed by the locating authority with a freshness window; the GPR return is signed by the sensor with a confidence class; the operator override is signed by a credentialed supervisor whose authority scope is published; the geotechnical model is signed by the engineer of record. Uncredentialed inputs are admitted only as advisory and weighted accordingly.

Second, the observations are evidentially weighted by composite factors, authority class, credential continuity, corroboration, governance policy, operational context, producing a structured contribution rather than a binary admit. Third, those contributions feed a composite admissibility evaluation that selects from a defined graduated mode set: continue at planned parameters, defer pending additional evidence, refuse with a structured reason, or partial execution with reduced depth, reduced rate, or restricted envelope. The mode set is enumerable, the selection is deterministic from the inputs, and the policy that produces the selection is itself a credentialed artifact.

Fourth, the selected mode produces a governed actuator commitment with three internal properties: reversibility evaluation (can this hydraulic motion be undone or its consequences mitigated within a bounded window), harm minimization under credentialed configuration (which admissible actuation path minimizes composite projected harm across the entities in the region while satisfying the mode), and post-actuation verification (the actual displacement, force, and resistance signature compared against the predicted envelope). Fifth, every observation, weighting, decision, mode selection, and verification is recorded in lineage, signed by the contributing authorities, and the post-actuation observation re-enters the chain at stage one as input to the next commitment. The recursion is what makes the architecture self-stabilizing rather than a flowchart.

Composition Pathway

Integration with the existing Built stack does not require replacing the planner or the perception pipeline. The Exosystem already produces the inputs the chain needs; what it lacks is the credentialed wrapper around them and the graduated gate at the actuator. A composition pathway adds an authority-credential layer at the input boundary: each sensor stream, each locate import, each operator command is re-emitted as a signed observation with a published authority class. The planner output becomes a proposed mutation rather than a committed trajectory.

A governance evaluator, running on the Exosystem compute or on a paired edge node, performs the weighting and admissibility evaluation against the site's policy artifact (itself signed by the general contractor, the utility owner, and the locate authority). The evaluator emits a graduated mode, which the hydraulic controller honors by selecting the corresponding commitment profile. Post-actuation verification uses the existing IMU, hydraulic-pressure, and bucket-load telemetry compared against the predicted envelope from the mode; deviations become signed observations re-entering the chain. The lineage is written to an append-only store with cross-authority signatures, accessible to the contractor, the owner, the insurer, and the regulator under their respective credential scopes.

The integration burden is modest because the chain is technology-neutral: Built keeps its planner, its perception models, and its supervisor app; the chain wraps the actuation boundary and the input boundary, leaving the interior algorithms untouched. What changes is the structural property of the system, not the implementation of any one component.

Commercial Implication

Built Robotics sits inside an off-highway autonomy market that is converging on regulatory scrutiny: OSHA enforcement of unattended-equipment rules, utility-owner contractual demands for damage-prevention attestation, and insurer pricing of autonomy risk. Each of those pressures favors a structural property the binary stop-or-go architecture cannot supply. A licensing posture toward Built is therefore not a feature deal; it is a substrate license to the architectural property the next generation of the product will need irrespective of which planner or perception stack is shipped.

The disclosure statement is direct: an autonomous-equipment deployment that adds graduated-mode actuation with credentialed inputs, composite admissibility, reversibility-aware commitment, post-actuation verification, and recursive lineage is practicing the governed-actuation architecture disclosed in U.S. Provisional Application No. 64/049,409. That architectural pattern is technology-neutral and is described here without reference to any single vendor's roadmap. A licensing relationship for such a deployment would be structured around the actuation substrate itself rather than any one planner or perception stack. The point for any construction-autonomy builder, Built Robotics included, is that the governed-actuation property is already disclosed and dated, so a builder can evaluate the approach and its variations against a fixed public record rather than reinventing it.

Disclosure Scope

This article is a public disclosure of the Governed Actuation inventive step, disclosed in U.S. Provisional Application No. 64/049,409. The governed-actuation approach described here is intended to be enabling and reasonably broad. A skilled implementer can build it: interpose a credential-and-authority layer at the input boundary so each sensor stream, locate import, and operator command is re-emitted as a signed observation with a published authority class and a freshness window; evidentially weight those observations by authority class, credential continuity, corroboration, and policy context; run a composite admissibility evaluation that selects among graduated response modes (for example accept, gate, defer, solicit, reject, escalate, or a partial-execution mode with reduced depth, reduced rate, or restricted envelope); evaluate reversibility at the commitment point under a pre-emption budget; emit a governed, revocable actuator commitment that minimizes harm under the credentialed configuration; verify the realized actuation against the predicted envelope; and record every observation, weighting, decision, mode selection, and verification into a lineage chain, with the post-actuation observation re-entering the evaluation as input to the next commitment.

The approach is not limited to hydraulic excavators. Contemplated embodiments include, without limitation, other earthmoving and construction machines, retrofit kits and OEM-native controllers, edge-node and on-machine evaluator placements, and any actuator whose commitment can be gated, deferred, or reversed. The evaluator may run on the machine's existing compute or on a paired node, the lineage store may be any append-only signed record accessible under credential scope, and the mode set and policy artifacts may vary with the site, the operator, and the governing authorities.

Named products, companies, standards, and market conditions in this article, including Built Robotics, Caterpillar Cat Command, and Komatsu FrontRunner, are described as external context to situate the comparison. They are third-party marks of their respective owners, are used here nominatively, and are not claims of the filing. Statements about those products reflect publicly available, architecture-level understanding and are generalized where a specific detail is not independently verifiable. Nothing here asserts a certification, contract, incident, or corporate transaction involving any named party. Only the governed-actuation architecture, as disclosed in U.S. Provisional Application No. 64/049,409, is claimed.