Familiar

A body can carry a voice, follow an admitted subject, or perform a bounded task. Familiar keeps the physical body's capabilities, local limits, observations, and consequences attributable. The name recalls a familiar as a bound companion spirit: serving one LichAssistantThe Assistant does not make the chassis its identity or grant power over the physical world.

Body admission establishes the exact capabilities and independent stop path. A finite follow mission then carries its subject designation through loss, speaking presence, and settlement. Cars, drones, rovers, legged robots, manipulators, phones, cards, displays, and other explicit forms need their own admitted controller or device profile.

Robotic Dance sketches a candidate use case: wear motion trackers and lead physical familiars in a shared dance, with research references and a possible Live Kinesis integration.

Contract

familiar.embodiment revision 3 publishes familiar.admit_body@3, familiar.bounded_mission@3, and familiar.follow@3. Additional body-specific PatternsWorkflowsWorkflows may be admitted without changing the body contract.

First admit the body by binding its exact controller/device attachment, form, capability snapshot, safety envelope, relevant geofence, and emergency-stop policy. A mission can then use that immutable FamiliarBody@3 with an objective kind, subject/target designation, budgets, stops, and optional Avatar ProjectionBinding@2. The records distinguish admitted body from performed work: results include FamiliarBody@3, settled FamiliarMission@3, FamiliarObservation@1, FamiliarEffect@1, and exact partial/non-completion.

Familiar excludes weaponization, non-consensual following, unadmitted private-property or restricted-airspace entry, operation beyond signal range without admitted return policy, inferred identity/consent from proximity, and universal physical authority.

Records and lifecycle

Familiar retains the body binding and capability epoch, then follows the mission through objectives, constraints, observation chronology, effects, and final judgment. It relies on other owners for enrollment/credentials, hardware, firmware, motor drivers, PID loops, client implementation, and live control handles; enrollment/credentials specifically remain with the attachment owner. A MAVLink connection, ROS2 node, PWM signal, or sensor stream cannot replace durable mission identity.

The control link contributes observed protocol version, link quality, controller health, firmware revision, start, stop, and loss, tied to its provider epoch. Recovery reads those facts alongside the body journal and mission record; a reconnected handle alone cannot establish what the body did during the gap.

For phones, Ward enrollment precedes Familiar body admission, which precedes Companion's device/session. Both CompositionsAppsApps retain the exact WardSecurity DeskSecurity Desk references. Remote bodies may instead attach through Legion; neither route is universal Familiar law.

Orthogonal axes, one Lich

flowchart TB
    subgraph W["World / body target axis · examples, not an exhaustive set"]
        S["Spectre · VR Habitat / Encounter"]
        B["Blockworld · game world / mission"]
        F["Familiar · physical body / mission"]
    end
    subgraph P["Presentation / interaction axis"]
        A["Avatar · presentation / projection membership"]
        C["Companion · mobile client / device session"]
    end
    A -. "optional projection" .-> S
    A -. "optional projection" .-> B
    A -. "optional projection" .-> F
    F -->|"exact admitted phone body"| C
    A -. "optional presentation through phone" .-> C

These examples are not exhaustive realms. Avatar chooses eligible presentation across targets; each target owns what happens there. Companion owns an independent mobile interaction/session over a phone-shaped Familiar. New capabilities need not distort this map into a closed cosmology.

Core capability before packaging

A ProductPackaged OfferPackaged Offer may package Familiar, Companion, and Avatar, and aan SuiteApp BundleApp Bundle may coordinate their live work. Neither moves body, mission, or safety authority into the client. Familiar does not require a current packaged application.

The first network-disabled mock body supplies simulated GPS, IMU, camera, mic, speaker, battery, recorded path, obstacle, speaking transition, and low-battery landing evidence. It proves the follow/settlement contract, not flight dynamics, actual avoidance, or hardware compatibility. No real drone, vehicle, public airspace, or non-consenting subject enters it.

Revision 3 supersedes revision 2 by naming exact WardSecurity DeskSecurity Desk phone enrollment and advancing body admission/FamiliarBody to @3. Revision 2 had replaced revision 1's universal Legion precondition with owner-qualified attachment. Mission/follow and FamiliarMission advance to @3 for the new body and Avatar bindings. No registry or RunJob RecordJob Record used those retired revisions; history remains unchanged without executable migration.

Enter by question

Embodiment asks which body and capabilities can be admitted. Follow carries one subject designation through a finite mission, loss, and return. Robotic Dance explores the candidate use case of shared physical movement. Return to the Composition Portfolio for other settings in which the LichAssistantThe Assistant may act.