Programmable behavior profiles for embodied robots.

ROBOTBEHAVIORLAYER

Install reusable interaction profiles for service, companion, and hospitality robots.

SoulLink defines how the same robot can feel standard, gentle, or attentive, then maps that behavioral difference into visible motion without rewriting the controller underneath.

Explore Profiles Technical Overview

Profile set3 launch profiles

Standard, Gentle, and Attentive define the first SoulLink behavior catalog for service and companion robots.

Validated tasks2 core scenarios

Object handover and approach-and-stop are the first scenarios used to validate how one robot changes behavior without changing the task plan.

Runtime boundaryProfile -> adapter -> runtime

Behavior profiles are converted into timing, spacing, smoothing, tone, and finish state through the adapter layer.

Programmable behavior profiles for embodied robotsStandard / Gentle / Attentive profiles for service and companion scenesSame robot, same task, visibly different interaction feelBehavior becomes pace, pause, distance, smoothing, tone, and finish stateProgrammable behavior profiles for embodied robotsStandard / Gentle / Attentive profiles for service and companion scenesSame robot, same task, visibly different interaction feelBehavior becomes pace, pause, distance, smoothing, tone, and finish state

care robotshospitality robotshome companionsobject handoverapproach and stop

Product model

One robot. Multiple behavior profiles.Product layer above the controller.

Most robots ship with one default interaction style, or none at all. SoulLink turns that layer into something selectable, reusable, and installable like software.

robot body, multiple behavior profiles

profiles shown in current field footage

launch profiles in the catalog

controller rewrites required to switch profiles

How it works

Choose a profile, apply it, and let the same robot behave differently.

The system should feel productized on the surface while still resolving into explicit runtime parameters underneath.

standardgentleattentive

Choose a profile

Select the interaction style the robot should carry in this scene.

SoulLink turns robot behavior into a reusable product surface instead of leaving it inside scene-specific tuning or controller-side edits.

Profile surface: Standard / Gentle / Attentive

same tasksame robotdifferent feel

Apply it

Use the same robot and task flow while changing how the robot arrives, waits, and finishes.

The task stays intact. What changes is the interaction feel: approach pacing, hold duration, personal distance, smoothing, voice tone, and finish behavior.

Current field footage: object handover / approach and stop

timingspacingsafe bounds

Map it

Translate profiles into motion without replacing the runtime underneath.

SoulLink lives above the controller. Adapters convert profile traits into executable parameters while the robot runtime keeps actuation and hard limits.

Boundary: profile -> adapter -> runtime

Core profile set

Three profiles define the first SoulLink catalog.

They are not marketing labels. Each profile resolves into explicit execution fields and scene behavior.

ProfileNeutral / direct / efficient

Profile 01

Standard

Core profile

Neutral, direct, efficient. Built as the default operating profile for robots that should feel clear and dependable.

RuntimeSoulLink Runtime v0.3+

Scene fitGeneral service / navigation / default robot behavior

Interaction toneNeutral / direct / efficient

Motion traitsShorter pause, tighter spacing, quicker completion

ProfileWarm / patient / soft

Profile 02

Gentle

Field validated

Warm, patient, and calm. Designed for situations where the robot should feel more reassuring and less abrupt.

RuntimeSoulLink Runtime v0.3+

Scene fitCompanion robots / care settings / gentle reception

Interaction toneWarm / patient / soft

Motion traitsLonger pause, wider stop distance, softer finish

ProfileAlert / polished / social

Profile 03

Attentive

Launch profile

Alert, polished, and socially readable. A profile for robots that should feel responsive and presentation-ready in public spaces.

RuntimeSoulLink Runtime v0.3+

Scene fitHospitality / front desk / public guidance

Interaction toneAlert / polished / social

Motion traitsCleaner arrival, brighter cadence, composed exit

Field scenarios

The same task can feel standard or gentle without changing the task plan.

The product language below focuses on what changes in the robot behavior layer: arrival pace, hold timing, personal distance, and finish quality.

Field footage

Validation layer

The filmed comparison keeps the same robot and task framing while switching only the active behavior profile.

Profile schema

Product layer

Each profile is defined through explicit fields such as speed, pause, distance, smoothing, hold duration, finish style, and voice tone.

Adapter boundary

System layer

SoulLink shapes interaction behavior above the controller while runtime actuation and hard safety limits remain below.

Field noteNormal label in video = Standard profile

Scenario 01

Object Handover

The handover sequence stays fixed. The active profile changes closing speed, hold duration before release, and how the robot exits the exchange.

StandardStandard / shorter hold / more direct release

GentleGentle / longer hold / softer exit

Field noteGentle label in video = wider stop + softer settle

Scenario 02

Approach And Stop

The target zone stays fixed. The active profile changes braking timing, personal distance, and how calmly the robot settles near a person.

StandardStandard / later brake / tighter stop

GentleGentle / earlier brake / wider stop

System noteSame task plan, different motion character

Scenario 03

Object Interaction

The object task stays fixed. The active profile changes contact smoothness, movement pace, and how the robot finishes the interaction around the object.

StandardStandard / direct contact / shorter finish hold

GentleGentle / softer contact / smoother finish hold

Field validation

The hero clip is evidence for the behavior layer, not a standalone marketing reel.

The real-robot video shown above stays simple by design. This section explains how to read it and what it demonstrates technically.

How to read the hero clip

The video stays untouched. The explanation lives here.

The in-video labels remain as filmed. On the product side, we interpret those labels as Standard and Gentle behavior profiles and explain the runtime difference through parameters rather than through extra text overlays in the clip itself.

Runtime mapping

Behavior becomes motion through the adapter layer.

The filmed difference is carried by concrete fields such as pace, pause timing, personal distance, and smoothing. The controller keeps low-level actuation and hard safety limits.

FieldStandardGentle

speed_scale1.000.82

pause_ms200420

approach_distance_m0.800.95

end_effector_smoothing0.900.96

profile: gentle_v1
task: object_handover
speed_scale: 0.82
pause_ms: 420
approach_distance_m: 0.95
smoothing: 0.96
adapter: runtime_map_v1
safety: fixed_envelope

Team

Built by AI and product operators, validated with robotics partners.

SoulLink is being shaped as a robotics software product first, with robotics integration capability inside the team to support real robot execution and validation.

Co-founder

Richard

Leads profile architecture, runtime mapping, and the software systems behind turning behavior definitions into motion parameters.

Co-founder

Alice

Owns product strategy, profile framing, and the experience of defining, selecting, and validating robot behavior profiles.

Robotics Integration Partner

Cris

Focuses on hardware-side deployment, robot behavior validation, and execution constraints. He supports the mapping of SoulLink behavior profiles onto physical robot systems, reviews runtime feasibility for real-world tasks, and helps validate profile-driven behavior differences through live robot testing.

Technology

See how a behavior profile becomes motion under the hood.

The technical page explains the profile schema, adapter path, runtime boundary, and field validation approach behind SoulLink.

Open Technology Overview View Runtime Mapping Open Repository