Profile surface
Launch profilesStandard / Gentle / Attentive
Behavior fieldsPace / pause / distance / smoothing
Primary tasksObject handover / approach and stop
Deployment modelProfile applied above runtime
SoulLinktechnical architecture
System view
PROFILEADAPTERRUNTIMESAFETY
Technical overview / behavior profile runtime / March 2026
SOULLINK BEHAVIOR RUNTIME
SoulLink joins three layers into one product: a reusable behavior profile, an adapter that maps it into robot runtime values, and a fixed safety boundary below the controller.
System map
The product splits into profile design, execution mapping, and field validation.
SoulLink keeps the product surface readable: define a behavior profile, map it through an adapter, and validate the difference on a real robot without rewriting the controller.
Execution mapping
Runtime fieldsSpeed / hold / finish / tone
Adapter bridgeProfile -> motion parameters
Controller boundaryLow-level control unchanged
Safety boundaryHard limits remain below profile layer
Field validation
Observed profilesNormal / Gentle in filmed clip
Comparison ruleSame robot / same task / same framing
System docsOne-pager / architecture / FAQ
Hardware modePartner-operated robot validation
Key questions
Four questions a technical reviewer asks immediately.
This page answers what SoulLink installs, what it changes, what it leaves untouched, and what the first field clip is supposed to show.
What does SoulLink install?
SoulLink installs a behavior profile on a compatible runtime. That profile defines robot interaction style through explicit fields instead of hidden scene-specific tuning.
What changes after installation?
The active profile changes pace, pause timing, personal distance, smoothing, hold duration, finish style, and optional voice tone while the task plan can stay the same.
What stays outside SoulLink?
Task planning, low-level actuation, controller logic, and hard safety limits remain inside the robot runtime. SoulLink shapes the behavior layer above that boundary.
What does the first field clip show?
The first field clip keeps the same robot, the same task setup, and the same camera framing while switching only the active profile between Standard and Gentle.
Near-term roadmap
What still needs to ship next.
The shape of the product is already clear. The next work is publishing, field access, and broader runtime coverage.
Attach the final hosted field-video URL and public repository links.
Keep the first field validation narrow around object handover and approach-and-stop.
Expand adapter coverage across additional runtimes after the first release.
Validate the same profiles on more than one physical robot stack.
Publish clearer profile-authoring and compatibility documentation.
Open source
Review the technical package behind the behavior layer.
The repository includes the one-pager, architecture notes, profile schema, and supporting technical material behind SoulLink.