REI
Adapt-1 Machina: Learning Continuous Control Sequences
5:26 PM | Sep 21, 2026

// Adapt-1 Machina: Learning Continuous Control Sequences

Adapt-1 Machina explores learning continuous control sequences from coarse outcome feedback, without demonstrations or a critic.

Machina continues Adapt-1 Preview with experiments in sequence-based control. Each task defines the observations and available controls. Adapt-1 proposes a sequence from the current observation, then uses execution feedback to revise later attempts.

To access Adapt-1 Machina API documentation: https://docs.reilabs.org/docs/machina

Learning budgets count executed attempts admitted to training. Frozen evaluation measures completion on reserved cases with learning disabled.

Background is available in Adaptive State from Partially Observed Streams. Introducing Adapt-1 Preview describes the earlier release; Emergence Toward Autonomous Structure Discovery discusses structure discovery.

Control proposals

A YAM proposal specifies an ordered sequence for the whole attempt from its starting observation. Each command requests a tool pose and gripper setting. Further learning occurs after execution feedback arrives.

Control and execution: the YAM interface This schematic follows a YAM attempt from the starting observation through execution. Adapt-1 proposes pose and gripper commands. Fixed inverse kinematics converts requested poses to joint targets. Outcome records from the completed attempt enter later learning. Observed context Fixed IK Adapt-1 trajectory learning Control sequence Execution Outcome evidence
The schematic follows a proposal through fixed inverse kinematics and simulated execution. Feedback returns between attempts. High-level YAM commands remain fixed for the duration of an attempt.

The recorded acquisition proposals each contain 20 commands with seven continuous values each. Position and orientation use three coordinates apiece; the remaining value controls the gripper. Execution can terminate before the proposal ends.

Command representation

U=[a0,,aH1],H20 ak=(x,y,z,α,β,γ,g)k

Each schematic column holds one command. The index k identifies its position in the sequence, and H denotes the proposed length. Command durations follow the execution contract. Learned hold durations and larger sequence limits were outside this experiment.

Learning from recorded execution

Adapt-1 retains executed commands with their observed consequences. A later proposal can refer to an earlier attempt and alter selected controls. This reuse begins during acquisition.

Training starts without a supplied successful trajectory or movement demonstrations. The client submits measured execution feedback to the learner.

After acquisition, the protocol evaluates candidates on additional training contexts and tests structural revisions. Contextual refinement learns bounded corrections from the observation at the start of execution.

YAM acquisition uses coarse progress feedback. Updated AIM refinement uses a continuous miss-quality score. The studies change several experimental conditions, leaving the effect of feedback detail on generalization unresolved.

Frozen evaluation computes commands from each observation using unchanged learner state.

Acquiring a YAM manipulation sequence

In MuJoCo, the YAM task requires releasing a red object inside a blue receptacle. Object and receptacle positions vary between layouts. In this setup, three calibrated cameras feed a fixed color-based measurement pipeline, combined with robot-state measurements. Goal images specify the desired arrangement. Hidden simulator object coordinates are excluded from decision inputs.

Acquisition starts with zero retained task records and no loaded task checkpoint. The first completed placement occurs on attempt 1,394.

The acquisition evaluator grades contact, sustained lift, transfer above the receptacle and stable released placement. Completion requires the object to remain placed for one second without robot contact.

YAM acquisition: 62 completed placementsThe upper panel shows cumulative completed placements, sampled at the end of each 256-attempt block and ending at 62 after 7,680 attempts. The lower panel shows contact and sustained lift counts within each block of 256 attempts, ending at 255 contacts and 175 sustained lifts. The final block contributes six placements to the cumulative total. All acquisition attempts, including failures, are counted.Completed placements during acquisitionCumulative total across all 7,680 attempts01632486401,5363,0724,6086,1447,68062placements in total7,680 attemptsContact and sustained liftOutcomes in each 256-attempt block06412819225601,5363,0724,6086,1447,680Contact: 255 / 256Sustained lift:175 / 256Acquisition attempts
Across all 7,680 acquisition attempts, 62 placements complete. The upper curve shows the cumulative placement total at each 256-attempt boundary. The lower curves show contact and sustained lift within each 256-attempt block. The final block contains 255 contacts, 175 sustained lifts and 6 placements. These milestones overlap within an attempt; failed attempts remain included.

The YAM run uses 18,400 learning episodes, including 7,680 acquisition attempts. The table accounts for every training stage. Frozen evaluations are counted separately.

YAM learning budget

One learning episode is an executed task attempt admitted to learning. An episode can contain several commands.

Learning episodes by stage in the recorded YAM run
StageEpisodes
Acquisition7,680
Selection4,032
Deletion / reduction2,240
Ordering2,400
Contextual refinement2,048
Total learning18,400

The acquisition log labels 262 proposals as initial trajectory explorations and 7,418 as revisions of earlier attempts.

The complete verification record contains 19,808 physical episodes and 251,186 executed commands. Training accounts for 240,946 command/state observations. The reserved final layouts use seeds absent from training, and the rounded visual layouts also pass the recorded overlap check.

Candidate selection measures completion on further training layouts. Calibrated landmarks and declared spatial control coordinates allow each candidate to be retargeted to the current observation. Nomination and confirmation use separate training contexts.

Structural revision evaluates removing contiguous command spans and changing when neighboring coordinate changes occur. Contextual refinement starts with zero correction weights and tests bounded offsets to the resulting sequence.

Recorded YAM execution with tool-pose and gripper channels aligned in time.

Reusing an earlier attempt

The experience record ends at the last command that ran. Termination can shorten execution; control bounds can also alter a requested value. The next revision uses that recorded execution.

Parent links identify the earlier attempt used for a revision. Indexed edits locate each changed control value, and preserved-prefix metadata identifies the beginning retained by the proposal.

Parent-linked revision inside a bounded control sequenceStructural illustration of a recorded YAM revision. Highlighted cells locate edits within the action matrix; the unchanged opening commands are marked as a preserved prefix.025101519025101519Revised proposalUᵣParent sequenceUₚ20 ordered commands × 7 control coordinatesCommand positionPrefix preservedcommands 0–2Coordinate-level edits(18, 5) (19, 5)Position / orientation / gripperCommand and coordinate indices.
Two indexed edits; three initial commands preserved.
Schematic of acquisition episode 19 and parent episode 12, using zero-based indices. The revision preserves commands 0–2 and changes coordinate 5 at command positions 18 and 19. The grids show command and coordinate indices; cell heights are illustrative.

Revision evidence and sequence lengths

The raw batch record contains both action arrays. Comparing them confirms the two marked edits. The proposal also records its parent identifier and preserved prefix, so the depicted reuse can be checked directly.

In this run, the selected execution contains 11 commands. The reduction output contains six, and the ordering output contains seven. The operation responsible for the added command remains unresolved in this audit. The complete learner update equations remain outside this trace audit.

Executing tool-pose requests

Fixed inverse kinematics converts a requested tool pose into joint targets. The low-level controller executes those targets with the accompanying gripper setting.

qk=IKfixed(pk,Rk)

In the equation, p and R specify position and orientation; q is the resulting joint target. The robot model and workspace constraints remain fixed during the run.

YAM joint geometry and the requested tool poseA schematic x-z projection of the nominal six-joint YAM chain. The joint frames follow the I2RT model; the pose and gripper outline are illustrative.xzOq₁q₂q₃q₄q₅q₆yₑzₑTool requestp, Rposition and orientationggripper command
An illustrative pose of the YAM joint chain, with the gripper shown separately. The drawing explains the supplied robot geometry.

The objective scores task progress and completed placement. Human likeness, motion smoothness, energy use and path efficiency receive no direct score.

Frozen YAM evaluation

Frozen evaluation on 384 unseen layouts measures placement success at 54.17% (208/384) for the acquired pre-refinement sequence and 60.42% (232/384) after contextual refinement. The paired records contain 70 gains and 46 losses, giving a net increase of 24 placements or 6.25 percentage points. Each pair uses identical starting observations and goals, with learning disabled throughout the comparison.

All 384 paired YAM outcomesEvery line links the recorded outcomes for one unseen layout under the frozen pre-refinement and refined executions. Vertical groups encode outcome stages. Hover or select a case to inspect its record.Before refinementAfter refinement208 / 384 placements232 / 384 placementsPlacementcomplete208Lift, incompleteplacement81No sustainedlift95Placementcomplete232Lift, incompleteplacement101No sustainedlift5170 gains46 losses162 both complete106 both failEach line connects recorded outcomes for one layout.
Select a line or a layout to inspect both recorded outcomes.
Each line connects outcomes for one layout under both frozen executions. Vertical groups identify completed placement, lift without completion and absence of sustained lift. Color marks placement gains and losses. The paired-layout bootstrap gives a 95% interval of +0.78 to +11.72 percentage points for the aggregate change.

Layout 604008: placement gain.

Before refinementPlacement incomplete
After refinementPlacement complete
0.00 s

The replay set’s first gain by seed. Each execution contains seven commands.

Choose the first gain or loss by seed in the replay set. Each pair starts from the same layout. Playback preserves the clips’ timing and holds the shorter recording at its final frame. These clips show selected individual cases.

Paired outcomes and evaluation scope

The remaining pairs comprise 162 shared successes and 106 shared failures.

The bootstrap resamples layouts from this run. Variation across independent training runs remains unmeasured. Cases are arranged for readability; their display positions have no physical meaning. Replay starts and outcomes agree with the recorded comparison.

Aiming across target configurations

AIM uses a sentry simulated in MuJoCo, with finite-speed yaw and pitch joints. The recorded configuration accepts up to eight half-second commands specifying yaw rate, pitch rate and firing. The client supplies structured joint and target observations, and the learner commits the complete sequence before execution. The runtime then rotates the joints and evaluates firing at completed command boundaries.

Every near/far run starts with empty learner state. Acquisition supplies candidate aiming sequences; selection and structural revision produce the base sequence used in contextual refinement. The learned correction maps the initial observation to adjusted commands. Frozen evaluation holds learner state unchanged while varying target configurations within the training range. The single-range protocol trains its own fresh learner.

AIM / FULL LEARNING FILMAcquisition → refinement → frozen test

Full supplied film
The film includes acquisition, refinement and evaluation with learning paused. Training paths are reconstructed from logged outcomes and development checkpoints. The test segment is labelled recorded controller motion. Scores for the independent three-policy comparison below come from its full audit panel.

In the revised near/far runs, the contextual model uses standardized observations with quadratic features. Response-guided candidate corrections receive feedback from measured miss distance. The decoder adds twice the proposed offset to each base command and clips the result to the allowed command range.

The intervention comparison executes the acquired sequence unchanged, then evaluates the contextual policy with matching observations and with observations assigned from another case. Each execution is scored against its actual target.

AIM frozen observation interventionsEach independently trained policy is evaluated on the same 256 cases. Lines connect the results under different observation interventions.Shuffled observationAnother case’s contextFixed acquired sequenceNo contextual correctionMatching observationCurrent case’s context0%25%50%75%100%255/256214/256198/25621 / 18 / 2334 / 35 / 16Seed 0 / Seed 1 / Seed 2
Matching context: 255/256, 214/256 and 198/256 hits.
Each line connects the intervention results for one frozen policy.

Every contextual audit attempt launches a projectile. The recorded task uses a target radius of 22 cm and projectile speed of 10 m/s, with gravity and drag set to zero. These fixed physics apply throughout training and evaluation.

The updated near/far protocol changes the observation representation, proposal search, objective, action decoder and stopping rules. It also uses a larger refinement budget. Those simultaneous changes prevent attribution of the score difference to sample efficiency.

Learning budget and independent evaluation

The recorded near/far runs each contain 1,024 acquisition attempts over eight training targets. During updated refinement, each update evaluates eight candidates across 64 training contexts, producing 512 physical executions.

Full AIM learning budget by stageEach seed begins with 1024 acquisition attempts. Learning-stage totals include selection, deletion, ordering and all refinement executions. Development and final audit are excluded from these bars.010,00020,00030,00040,00050,000Seed 0Acquisition: 1,024 executionsSelection: 40 executionsDeletion: 184 executionsOrdering: 168 executionsRefinement: 18,432 executions19,848Seed 1Acquisition: 1,024 executionsSelection: 80 executionsDeletion: 40 executionsOrdering: 72 executionsRefinement: 49,152 executions50,368Seed 2Acquisition: 1,024 executionsSelection: 24 executionsDeletion: 40 executionsOrdering: 72 executionsRefinement: 49,152 executions50,312AcquisitionSelectionDeletionOrderingRefinement
Bars count physical executions admitted to the five learning stages. Development checks and final evaluation are accounted for separately. Most of the difference in total workload comes from contextual refinement.

Seed 0 records 40 selection, 184 deletion and 168 ordering executions, followed by 36 refinement updates. Seeds 1 and 2 record 80 and 24 selection executions respectively; each also records 40 deletion executions, 72 ordering executions and 96 refinement updates. Development checks add 320 executions for seed 0 and 800 for each remaining seed. Their outcomes guide stopping.

The final audit uses 256 distinct configurations, each evaluated under three independently trained policies. Across 768 attempts per condition, the hit totals are 667 with matching observations, 85 for the acquired fixed sequences and 62 with shuffled observations. The audit was generated after implementation selection and excluded from training and stopping decisions. Earlier development checks used a separate panel.

Matching-observation miss distance by training seed
SeedMean missMedian miss
04.39 cm3.40 cm
112.09 cm7.51 cm
214.58 cm9.91 cm

Under the original near/far protocol, the recorded run reaches 13/64 contextual hits and 9/64 fixed-base hits after 4,608 refinement executions.

Earlier single-range study

The earlier single-range learner trains and evaluates at a target depth of 4 m. Its final 64-case comparison records 58 contextual hits and 11 hits with the acquired fixed sequence. These cases were held out from that learner and reused from the historical V13 evaluation.

Earlier single-range AIM development checksMeasured success on the 32-case development panel at refinement checkpoints from update 0 through update 80.0816243201632486480Successes / 32 development cases29/32Refinement updates
The curve records repeated checks on the same 32 development cases during single-range refinement. The final comparison uses a separate 64-case panel.

The single-range run admits 6,624 physical executions to learning: 1,024 acquisition, 80 selection, 184 deletion, 216 ordering and 5,120 refinement executions. Including evaluation, the execution total reaches 7,105. The request ledger contains 9,059 native requests.

Historical reports list six successes with goal observations permuted, four with horizontal control removed and 25 with vertical control removed on the fixed-distance panel. The evidence bundle lacks the separate intervention trial journals, so these figures remain unverified against individual executions.

Controlling delayed physical effects

Rail uses a carriage whose velocity responds over time to a signed request held for half a second. In Rail B, carriage acceleration also drives a passive suspended load. The velocity servo acts on the difference between requested and current carriage velocity. The learner receives target displacement and initial carriage velocity, with initial swing state in the suspended-load task.

The clips pair an earlier failure with the selected best final Rail B case. Their targets and starting conditions differ. The later case was selected for the smallest maximum of carriage and payload position error over the assessment window.

Contextual refinement adjusts an acquired velocity sequence using the observed starting condition. Rail A scores carriage position and stopping speed. Rail B adds limits on payload motion and swing. Each task has its own learning workload and reserved evaluation panel.

Frozen Rail evaluationsRail A and Rail B are separate 64-case panels. Fixed and contextually refined success counts are displayed with their own full learning budgets.Fixed sequenceContextual executionA; carriage1,420 learning executions22/6444/64B; suspended load1,620 learning executions19/6463/64064 cases
Each frozen comparison runs the acquired fixed sequence and the refined contextual policy on the same reserved cases within that Rail task.

Saved final policies retain six half-second commands in Rail A and eight in Rail B. Neutral velocity requests fill the remainder of each 5.5-second episode. Assessment covers the entire final second, using the maximum position errors and speeds during that interval. Rail B also checks the maximum swing angle and angular speed.

Learning budget and physical assessment

Rail learning-admitted physical executions
StageRail ARail B
Acquisition300500
Structural stages, combined352352
Refinement768768
Total learning1,4201,620

Source reports record 12 refinement updates per Rail task. Individual selection, deletion and ordering counts are unavailable; the table derives their combined count by subtracting acquisition and refinement from the reported learning total. On their separate 64-case final panels, Rail A records 22 fixed-sequence and 44 contextual successes; Rail B records 19 and 63. Paired gains total 22 for Rail A and 44 for Rail B, with zero regressions in either panel.

The request u maps to a carriage target velocity of 0.6u m/s. Physics integration runs at 100 Hz between command boundaries. The suspended-load model calculates pendulum motion from prescribed carriage acceleration and omits payload reaction forces from the carriage equation.

In the selected Rail B case, the maximum carriage and payload errors over the final second are 1.53 mm and 1.41 mm respectively. Aggregate success counts were recomputed from a saved cache. Verification of the original traces at every simulation tick remains unavailable.

Passing physical state between maneuvers

The Harbor C1 harness assigns the Gate → Jump → Stop sequence. Adapt-1 learns the command values for each maneuver. Later maneuvers train from successful upstream arrivals, carrying forward the actual position and velocity along with the scoring state.

In the recorded C1 execution, each half-second command contains drive, turn, brake and jump inputs. Drive and brake can act simultaneously. Jump values at or above 0.5 count as pressed; a takeoff requires an accepted rising edge. The acquired Stop sequence includes an additional accepted takeoff.

Harbor C1: recorded simultaneous controlsDrag the plot to rotate it. Use the time slider to inspect a packet and its held control values. Connections show packet order in control coordinates.RECORDED CONTROL SPACEDrag to rotateDrive +1Turn +1Brake 11GATE / PACKET 010.0–0.5 sDrive0.9479Turn0.2181Brake0.0199Jump0.2902Ring radius encodes jump input.Each point is one held command.Connections show packet order.
Harbor simultaneous held controlsFour measured input channels with a shared time axis, reproduced from reported decoded half-second packets. Accepted takeoffs and zero speed are measured events.GateJumpStopGuardDrive1−1Turn1−1Brake10Jump100123456788.5sAccepted takeoffs: 1.008, 3.008, 5.508 sZero speed from 7.65 s
0.000 s

Select a time to inspect the held controls. Readouts are rounded to three decimal places.

The upper plot uses drive, turn and brake as coordinates, with ring size indicating jump input. Its lines connect successive command packets. The timeline marks accepted takeoffs and the time after which speed stays at zero for the rest of the recording. Drag to rotate the plot, or use playback and scrubbing to inspect the linked views.
Original recorded Harbor C1 trajectory with simultaneous drive, turn, brake and jump timelines
The path image and control plots use the same recorded C1 execution. The simulator models the body as an upright cylinder.

Frozen evaluation records 127 successful courses out of 128 for each of the selected, ordered and contextual variants. The courses contain small variations of the training geometry. All variants produce identical controls and physical traces on each course.

Maneuver learning and handoff accounting

C1 learning-admitted maneuver executions by stage
ManeuverAcquisitionSelectionDeletionOrderingRefinement
Gate51259213624256
Jump5127926424256
Stop76860030424256

Run accounting records 5,120 learning-admitted maneuver executions through 1,822 native decision acknowledgements. The broader total of 6,848 unique maneuver executions includes development checks, training handoff collection and frozen evaluation.

Evaluation reuses the reserved courses across the policy variants, totaling 384 course attempts and 1,152 maneuver executions. Deletion and ordering preserve the selected sequences, and every final contextual query returns zero offsets. The experiment lacks an equal-budget comparison with a single learner controlling the complete course.

After the last Stop command, the executor applies a neutral guard. The recorded case satisfies the stopping condition throughout this interval.

Correcting speed and jump timing

Harbor v4 examines further correction practice on inherited behavior under a separate setup from the C1 experiment. The focused-alley study begins with a retained second-hurdle maneuver within supplied navigation and skill composition. Its reported training budget covers the added correction practice. The client observes incoming position and velocity at the handoff, then applies bounded offsets to speed and jump timing.

Targeted Harbor corrections and local reconnect checksSeparate correction studies. Each comparison has 36 reserved cases; reduced strength and normal-strength rehearsal belong to the same 320-execution study. Reconnect replays the already evaluated corrected cases.ParentCorrectedLocal reconnectFocused alley128 training executions12/3636/3636/36Reduced strength320 training executions24/3636/3636/36Normal-strength rehearsalSame mixed-strength practice34/3636/3636/36Previously evaluated cases; no additional feedback.
The focused-alley panel and the mixed-strength panels cover separate practice studies. Solid connectors link parent and corrected results; dashed connectors link the corrected results to local reconnect checks.

A separate mixed-strength report describes practice with takeoff speed reduced from 5.8 to 4.4 m/s and rehearsal at normal strength. The learned correction varies with starting position; the report finds little dependence on the strength input.

An earlier assisted delivery controller completes 33 of 36 fresh full courses using supplied navigation and interaction around retained components. Its full historical learning budget is unavailable. This evaluation belongs to a separate experiment from C1 and the correction studies.

Practice and reconnect conditions

Focused-alley practice records 128 training executions. On the 36 reserved starts, the parent completes 12 courses and the correction completes all 36, repairing 24 failures with zero regressions. Practice combines a narrower task with incoming-state observations, a declared correction scale and balanced discovery/confirmation groups. The design leaves their individual effects unresolved.

The mixed-strength report records 320 training executions. Corrected execution completes all 36 cases in each evaluation panel; the parent completes 24 at reduced strength and 34 at normal strength. A retained report excerpt supports these figures. The current bundle lacks the underlying trial records.

Reconnect uses a fresh local client process to query the retained policies on previously evaluated starts with feedback disabled. The focused-alley report records exact reproduction of its final corrected panel; the mixed-strength excerpt reports the same for all 72 corrected records. The checks compare returned offsets and executed actions with their recorded trajectories. Server-restart behavior remains untested.

Observation timing during execution

DOOM explores a separate acquisition setup that refreshes observations during an episode. The recording begins from saved learner state with learning active, and the initial cold-start budget is unavailable. This excerpt shows acquisition in progress; the earlier performance comparisons evaluate retained policies with learning disabled.

The configured DOOM controller receives a new observation between windows of up to eight control steps. Its continuous outputs specify forward and sideways movement along with yaw and pitch; additional outputs control firing and interaction. For YAM, the client sends the starting context once for the full attempt.

Proposal boundaries and observation opportunitiesThe YAM row shows its configured acquisition command ceiling on an index axis. DOOM retake 18 executes 8 + 8 + 8 + 6 steps across four proposals, ending the final window at combat completion.YAMAcquisition ceilingOne proposal; up to 20 seven-value commandsDOOMRecorded retake 18Observe 1Observe 2Observe 3Observe 430 executed steps; 2.57 s game timeVertical markers are high-level observations. Low-level execution continues within each window.
Each bar groups commands issued from one observation. The YAM bar shows the configured acquisition ceiling without assigning an elapsed duration. DOOM timing follows the executed commands in retake 18.

The full retake ends when the user stops the episode with navigation and interaction objectives unfinished.

Recorded DOOM combat control inputs across four proposal windows
The trace aligns retake 18’s proposal boundaries with the movement, aim and button inputs held during combat.

Observation windows and executed prefixes

In this recording, each control step spans three game ticks, approximately 86 milliseconds of game time. Retake 18 executes 8 + 8 + 8 + 6 steps across four proposals. Combat completion stops the final window before its last two proposed steps execute.

The wider combat record contains 247 executed windows. Of these, 246 receive admitted learning updates; the remaining window is canceled because its terminal observation is unavailable. That cancellation occurs in retake 6.

What Machina adds to Adapt-1 Preview

Machina adds continuous-control sequence learning to Adapt-1 Preview. Building on the same contextual and temporal learning system, it acquires coordinated executions from its own attempts, revises them using outcome feedback, and retains them for reuse.

adapt-1
Application map

What it produces × how the task unfolds

Connections across time
Temporal organization
Infer / predict
Decide / act

Temporal inference

Anticipate change

  • Forecasting

    Predict how observed conditions evolve.

  • History-aware assessment

    Interpret the present using recent events.

  • Process monitoring

    Track changes across an unfolding stream.

Sequential decision & control

Learn how to act

  • Multi-step workflows

    Coordinate actions toward an outcome.

  • Interactive control

    Observe between execution windows.

Machina

Continuous-control learning

New in Machina

  • Robotic manipulation
  • Maneuvering & load control
  • Game & computer control

Contextual inference

Understand a situation

  • Contextual assessment

    Classify or score the observed situation.

  • Spatial reasoning

    Relate observed positions and goals.

  • Causal analysis

    Learn how variables relate.

Contextual decision

Choose what works

  • Adaptive recommendations

    Use outcome feedback to guide a choice.

  • Inspection decisions

    Choose which observation to gather next.

  • Task routing

    Select the next handler for the current case.