Questions about how individual parts of claim 1 might be changed. A question may describe something different from what the claim language recites, or a version of it; no view is offered on which.
1.1Handwheel pulse input
What ifWhat if an operator uses a handwheel to specify the axis and displacement of each candidate move?
Claim language“one or more decision models”
A rotary encoder produces quadrature pulses, and a selector switch routes them to the counter for the selected axis. A fixed scale of 0.01 millimetres per count converts the signed pulse count into a displacement for the downstream motion check.
1.2Constraints inside the planner
What ifWhat if the decision model checks motion constraints inside its own search loop?
Claim language“separate from the one or more decision models”
The planner expands a graph of joint configurations and checks the swept volume and joint travel of each candidate segment during expansion. The same routine assembles the outgoing trajectory from the segments that pass those checks.
1.3Fixed travel stops
What ifWhat if mechanical stops and direct position switches establish the permitted travel of a workshop manipulator?
Claim language“to predict, using at least one world model”
Adjustable steel stops on the guide rail define the physical ends of carriage travel. A cam opens a direction-specific limit switch before the carriage reaches each stop, interrupting drive enable for motion toward that end.
1.4Hardwired threshold circuits
What ifWhat if hardwired comparators check predicted quantities against electrical reference levels?
Claim language“a constraint ledger comprising a plurality of constraint sets”
Digital-to-analog outputs represent the predicted peak wrist load and minimum fixture clearance as separate voltages. Each comparator uses a fixed reference voltage for its threshold, and a logic gate combines the pass signals.
1.5Evaluator generates drive waveform
What ifWhat if the evaluator generates the motor drive waveform directly for motion that passes its checks?
Claim language“issue an actuation release authorization”
The evaluator loads the current setpoint for an accepted motion segment into an on-chip pulse-width modulator. The modulator drives an isolated power stage through a gate driver, and a failed check clears the modulation output.
Section 2 · machine-generated
Variations
Further arrangements of the same subject matter, described here as of the publication date at the foot of this page.
Other field of use
Gated slide handling in a laboratory
A laboratory slide handler proposes a transfer from a storage rack to a microscope stage. A separate gate uses gripper jaw position, rack slot occupancy, and stage position to predict the path of the slide and the clearance around its edges. The gate issues a release only when the destination is empty, the predicted grip force stays within the configured band, and rack clearance stays above the configured minimum. A motor gateway verifies that the release matches the proposed transfer before enabling the gripper and carriage commands.
Component substitution
Interval arithmetic for motion prediction
An interval arithmetic reachability solver replaces the single-trajectory predictor in the gate of a Cartesian gantry. At each time step the solver propagates bounded position and velocity measurements using the proposed acceleration and configured bounds on tracking error. The constraint evaluator checks each resulting position box against fixture boundaries and travel limits. The drive gateway accepts the proposed command block only when its identifier matches an unexpired release issued after all boxes pass.
Parameter or scale variation
Short release windows for a press
A controller proposes a 10-millisecond velocity segment for a servo press with a 100-millimeter stroke. A separate gate samples ram position and load at 1 kilohertz and predicts ram travel and load through the proposed segment and the subsequent controlled stop. The gate releases a segment only when predicted travel stays within the active stroke limits and predicted load remains below 2 kilonewtons. The drive gateway accepts the matching segment for a single 10-millisecond window and initiates the controlled stop if that window ends before it verifies a release for the next segment.
Shared work zone for two manipulators
Two manipulators share a 600-millimeter-wide work zone and submit paired 100-millisecond motion blocks to a separate gate. The gate predicts the swept volume of each arm and its payload over successive 5-millisecond intervals, including a controlled stop from each interval boundary. It issues a joint release only when the predicted volumes maintain at least 50 millimeters of separation and stay clear of fixed fixtures. A common actuator gateway verifies both block identifiers and the shared start time before releasing both blocks together.
Combination with existing systems
Transfer gating with conveyor tracking
A pick-and-place controller receives belt encoder counts and carton locations from a conveyor tracking controller and proposes a transfer to a moving carton. A separate gate projects the carton position and gripper path over the transfer using the timestamped belt speed and the configured acceleration bounds. The gate issues a release only when the predicted placement lies within the carton opening and the gripper clears neighboring cartons throughout the move. The robot drive gateway verifies the transfer identifier and the belt encoder count window carried in the release before enabling the move.
Automated or data-driven variant
Braking estimates from recorded stops
A mobile platform logs initial speed, payload estimate, and encoder-measured stopping distance during scheduled brake tests. An offline process groups the records by speed and payload and publishes a stopping-distance table that adds a configured margin to the longest measured stop in each group. A separate gate evaluates each proposed motion segment by appending the table-based stopping distance to the predicted path and checking the resulting swept area for clearance. The motor gateway verifies a release bound to the segment, and the gate withholds the release when the speed and payload fall outside the tested groups.
Specific version of a part
Dedicated trajectory check controller
A separate microcontroller receives time-stamped joint waypoints from the decision processor over a serial link. It runs the trajectory checks before forwarding the waypoints to the actuator interface.
Sampled forward dynamics simulation
Joint encoders supply initial positions and velocities, and a depth sensor supplies obstacle positions in the workcell. A rigid-body simulator integrates the proposed joint inputs at 2-millisecond intervals over a 500-millisecond horizon and outputs predicted joint and link states.
Table of workcell limits
A flash-resident table groups limit records for joint travel, payload torque and fixture clearance. The evaluator checks each predicted sample against the applicable records and reports the identifier of each failed limit.
Command-bound release token
A release token contains a digest of the approved command, a sequence counter, an expiration time and a message authentication code. The gateway checks the authentication code, compares the digest with the received command and validates the counter and expiration time before forwarding the command to the drive.
Section 3 · quoted from USPTO records
Other work
Passages reproduced word for word from two earlier-published U.S. patent documents, placed beside the language of claim 1. No characterization is offered. Each passage is marked A or B for the document it comes from; ¶ numbers are the paragraph numbers in the USPTO’s published full text of that document.
1.1one or more decision models configured to generate a candidate physical action for a physical platform;
1.2a world model gating module, separate from the one or more decision models, configured to receive the candidate physical action after generation of the candidate physical action by the one or more decision models and before transmission of the candidate physical action to an actuator interface;
The Outputs for the loop 700 include an Actuation Command Governor 750 that fuses Pre-safety actuation commands (703), Predicted hazards (H_lv), Verified safety state (from ZTSV), and Task-constraint envelope outputs (SE_vv). The governor 750 may Approve the actuation, Modify parameters (force, speed, trajectory), Substitute a safer motion primitive, or Abort the action entirely.
B · US 2026/0093213 A1 · ¶ 245
1.3the world model gating module further configured to obtain a current physical-state representation of the physical platform and an operating environment and to predict, using at least one world model, one or more future physical states associated with execution of the candidate physical action;
The temporal dynamics modeling unit 310 can provide a time-evolved latent representation to the future-state predictive module 340 and the causal inference module 320 can provide a cause-effect mapping graph to the counterfactual simulator 330. The Counterfactual simulator 330 can also provide counterfactual future-state vectors to the predictive module 340.
B · US 2026/0093213 A1 · ¶ 221
1.4a consequence evaluation engine configured to evaluate the one or more future physical states against a constraint ledger comprising a plurality of constraint sets;
A constraint check is performed for each operation subsequent to its execution to determine whether data stored in the database affected by the operation is valid, during this constraint checking additional operations and/or constraint checks on the same table are allowed to run in parallel.
A · US 2013/0339312 A1 · abstract
The inputs are fed to an action library and mapping module 410, a risk intervention optimization engine 420 and a safety constraint governor 430. The governor 430 can include a hard constraints engine 431, a soft constraints engine 432, and a legal/ethical constraint layer 433 as shown.
B · US 2026/0093213 A1 · ¶ 229
1.5an authorization interface configured to issue an actuation release authorization in response to determining that the one or more future physical states satisfy the plurality of constraint sets, and to withhold the actuation release authorization in response to determining that at least one of the plurality of constraint sets is not satisfied; and
The governor 430 can include a hard constraints engine 431, a soft constraints engine 432, and a legal/ethical constraint layer 433 as shown. The governor 430 can provide signaling to an intervention authorization module 440 that further feeds a final actuation command generator 450 which provides either an actuation command packet 451, an emergency override signal 452, or a human-in-the-loop notification 453 to the outputs 460 and 470.
B · US 2026/0093213 A1 · ¶ 229
1.6an actuator gateway configured to permit a motor-control command for one or more actuators only in response to verification of a valid actuation release authorization associated with the candidate physical action.
The governor 430 can provide signaling to an intervention authorization module 440 that further feeds a final actuation command generator 450 which provides either an actuation command packet 451, an emergency override signal 452, or a human-in-the-loop notification 453 to the outputs 460 and 470.
B · US 2026/0093213 A1 · ¶ 229
An empty cell means only that no passage was reproduced there.
Statements in these documents
Since no disk I/O is involved and CPU power is abundant, lack of inter-query parallelization of constraint checking can seriously hamper performance.
A · US 2013/0339312 A1 · ¶ 3
The database can be an in-memory database.
A · US 2013/0339312 A1 · ¶ 8
Other traditional methods of diagnostics, safety, and autonomous decision-making fail to make efficient and logical use of all the data that may be available.
B · US 2026/0093213 A1 · ¶ 3
In certain contexts, the embodiments can be deployed within Modular Open Systems Approach (MOSA) and Sensor Open Systems Architecture (SOSA) aligned platforms and may incorporate a resilient magnetoelectric field-based communication subsystem suitable for subterranean, underwater, and RF-challenged environments
B · US 2026/0093213 A1 · ¶ 2
Cite aspatent.fyi, US 2026/0355963 A1, claim 1, first published 2026-11-19T17:33:15-05:00, https://patent.fyi/US20260355963/, SHA-256 66222e13507033a2b85ba28f17b656179604d08c3c73993d8be69618e4bb3c85