1. The Problem: A Site That Invalidates Its Own Plan

A construction site is a partially structured environment that changes faster than any static configuration can track. Soil that bore a tracked loader in the morning is saturated and shear-prone after an afternoon pour and rain. A reach that was clear yesterday is now blocked by formwork, rebar, or a parked delivery. Surface friction shifts as dust, slurry, and curing compounds accumulate. Human crews move through the same volume the robot occupies, on no fixed schedule. The legacy answer is to program a path and trust the calibration document, which is exactly the assumption the regulatory frameworks named above no longer accept. OSHA 29 CFR 1926, ANSI A92, ISO 18497, and RIA R15.06 increasingly want evidence, captured at the moment of action, that the machine knew its own operating limits and the conditions it actually faced, and either stayed inside those limits or declined. A robot whose only self-model is a factory specification cannot produce that evidence, because its self-model does not change when the site does.

This is the gap Capability Awareness was disclosed to close. The remainder of this article is an enabling description of how a construction robot built on that layer behaves, what it must instrument, and how it composes across a machine, a fleet, and a general contractor.

2. What the Robot Must Carry: An Embodied Capability Envelope

The disclosed mechanism treats a machine's present affordances as first-class state called a capability envelope, a structured object the substrate advertises and continuously updates rather than a benchmark or a permission list. For an embodied construction robot the envelope spans the physical dimensions the disclosure enumerates for robotic substrates: the degrees of freedom of its manipulators, the force and torque limits of its actuators, the reach envelope of its arms, the locomotion capability of its mobility platform, the sensory modalities available through its sensor suite, and the power budget available for sustained operation. Alongside these sit the computational dimensions of the same envelope, including compute class, memory architecture, model access, locality, and execution guarantees, because a perception or planning model that is not loaded is as disqualifying as an actuator that cannot produce the required torque.

Crucially, the embodied capability envelope is architecturally distinct from an Operational Design Domain. An ODD states the environmental conditions a machine was designed for; the capability envelope states what the machine's body and compute can presently do, independent of the environment. A construction robot needs both, and the disclosure treats them as complementary but independent evaluations. The envelope is a living object: when a battery depletes, an actuator heats, a sensor fouls with dust, a hydraulic line loses pressure, or a tool is swapped, the envelope is updated to reflect the substrate's current state. Concrete embodiments of the construction envelope include:

  • A mobile manipulator for drilling or fastening, whose envelope tracks mast reach, drill-axis force capacity, chassis stability on the current grade, and the load on its onboard perception accelerator.
  • A bricklaying or block-setting arm, whose envelope tracks payload at reach, gripper degrees of freedom, placement-accuracy confidence under current vibration, and thermal headroom in sustained cycling.
  • A material-transport platform, whose envelope tracks ground clearance, traction against the present surface, slope tolerance, and state-of-charge against the remaining haul.
  • An autonomous inspection drone operating under FAA Part 107, whose envelope tracks endurance, wind-rejection margin, and the model access required to run the defect-detection pipeline on board.

3. Capability-Native Computation on the Site

Under the disclosed paradigm, deciding whether a task can be done is not a guard clause that precedes the real work. It is the first phase of the real work, a capability-native computation that evaluates the intersection of three structured inputs: the task's formal requirements, the robot's capability envelope, and the current temporal-uncertainty state. A motor objective such as driving a fastener, lifting a panel, or traversing a section of slab carries physical requirements that are matched, dimension by dimension, against the physical envelope: does the manipulator have the degrees of freedom to orient the tool, does the actuator have the force to drive the fastener, does the mobility platform have the clearance and traction to cross the terrain, does the sensor suite include the modality to detect the relevant feature.

The match is deliberately not binary. Each dimension resolves to satisfied, unsatisfied, or conditionally satisfiable, where conditionally satisfiable means the shortfall could be cured by waiting for a forecasted change, reconfiguring the substrate, or decomposing the task so the failing dimension is isolated to a sub-task routable elsewhere. This three-valued matching is what keeps a construction robot from prematurely abandoning a task that becomes doable once the slab cures, the crew clears, or a different tool is fitted.

The per-dimension results compose into one of four bounded outcomes for the task, exactly as the disclosure specifies:

  • Structurally possible: every required dimension is satisfied, and execution synthesis may proceed.
  • Structurally impossible: a dimension is unsatisfied with no conditional path, so the robot reports non-executability rather than attempting it.
  • Structurally deferred: a dimension is conditionally satisfiable within a bounded time horizon, so execution may occur within a forecasted window.
  • Rerouted: a dimension fails on this machine but is satisfied by another substrate the system knows about, so execution moves to that machine.

Every determination is persisted as a structured record carrying the evaluated substrate, the extracted requirements, the retrieved envelope, the per-dimension results, the aggregate outcome, the uncertainty bounds, and, for deferred or rerouted outcomes, the conditions under which the determination may change. That record is the auditable, reproducible artifact a regulator or insurer can read when they ask what the machine knew about its own capability at the moment it acted.

4. Forecasting Envelope Collapse Before It Happens

A construction robot's envelope is time-varying, so a task that is executable now may not be executable for its full duration. The disclosed temporal executability forecasting projects each envelope dimension forward over a defined horizon using scheduled events, observed trends, and declared constraints, then computes the windows in which every required dimension is simultaneously satisfied. The disclosure gives the embodied case directly: a motor objective that requires sustained high-torque actuation may be immediately executable yet become temporally impossible as actuator temperatures approach their thermal limit, and the forecast detects this impending collapse and defers or reroutes the objective before the limit is reached. The same machinery covers a battery that will not last the haul, a sensor degrading as dust accumulates, or a grade that worsens as a trench is opened nearby.

These forecasts are confidence-bounded windows, not point predictions. The system does not assert that capability returns at time T; it asserts a window between an earliest and a latest time at a stated confidence derived from the uncertainty model, and it widens those margins when uncertainty is high. Forecasts are continuously recomputed as the envelope changes, as reservations are made or released, and as observed behavior diverges from the modeled trend, so deferral and routing decisions always rest on current state. The three temporally conditioned states, immediate executability, deferred executability, and temporal impossibility, prevent the pathological retry loop in which a conventional scheduler keeps re-attempting a task on a substrate that will never become capable.

5. Uncertainty, Negotiation, and Genealogy

Capability Awareness carries uncertainty as a first-class propagated variable rather than an error term, and the embodied uncertainty model incorporates the inherent noise of physical state estimation: noisy sensors, non-linear actuator degradation, and partially observable terrain. On a construction site this is the difference between a robot that confidently drives a fastener into a misjudged surface and one that recognizes its placement confidence has collapsed under vibration and dust and declines or escalates. Capability feeds the confidence governor described elsewhere in the disclosure, so any determination short of structurally possible with full dimension satisfaction lowers the machine's execution confidence accordingly.

When a machine's envelope does not fully match a task but a dimension is conditionally satisfiable, the disclosed capability envelope negotiation lets the substrate advertise the specific modifications it could make, such as loading a perception model, activating a dormant sensor, or reserving compute, each with an estimated time and resource cost. The agent weighs the modification cost against rerouting to a machine that already satisfies the requirement, and if it proceeds it issues a governance-approved capability acquisition plan, after which the envelope is updated and the determination re-evaluated. This is how a fleet decides, in real time, whether to retool the machine on hand or send the right machine instead.

Finally, every envelope change is written to a capability genealogy, an append-only, integrity-protected log of when capabilities were added, removed, or modified and what event triggered each change. For construction this is both a maintenance signal, surfacing a slow drift in actuator force or sensor accuracy before it causes an incident, and a forensic record, establishing whether a machine's capability was adequate at the moment a task was dispatched and, if not, when and why it changed. That record is precisely what an OSHA investigation or an insurer's subrogation review demands after an event.

6. Deployment and Composition

The layer is technology-neutral and composes across scope, which lets it follow how construction work is actually organized. Adoption can proceed without changing actuation behavior first: a machine begins emitting a credentialed envelope and capability determinations alongside its existing telemetry, giving the integrator a regression-free baseline and a regulator-facing evidence stream. Next, the planner consumes envelope state as a first-class input, temporal forecasting becomes a gate on task admission, and the deferred, impossible, and rerouted outcomes are wired through existing operator-handoff and fleet-management surfaces, with field validation concentrated on the cases where the new behavior diverges from the legacy stack by declining or rerouting a task it would once have attempted.

Composition then scales the same primitive across levels. A single machine's envelope informs which task it can take now. Machine envelopes compose into a fleet view of which machine has the headroom for the next task and where to reroute when one machine's envelope collapses. Fleet envelopes compose into a site view of which work packages are executable today given the equipment actually on the ground, and into a contractor view spanning multiple sites and subcontractors. Each level uses the same envelope, forecast, and bounded-outcome machinery at a different scope, so the equipment manufacturer, the construction-management software vendor, and the general contractor integrate against one architectural shape rather than re-architecting at every tier.

7. Disclosure Scope

The capability awareness mechanisms described here, the embodied capability envelope, capability-native computation with three-valued per-dimension matching and bounded structurally-possible, structurally-impossible, structurally-deferred, and rerouted outcomes, temporal executability forecasting with confidence-bounded windows, uncertainty propagation, capability envelope negotiation, and capability genealogy, are disclosed in United States Patent Application 19/647,395. The construction-robotics application framing, including the regulatory mapping, the specific machine embodiments, and the deployment and composition pathway, is an enabling application of that disclosed technology to the active-construction domain. No capability metrics or benchmark numbers are asserted beyond what the cited application discloses.