actr-hyper 0.3.1

Hyper — Actor platform infrastructure: sandbox, transport, scheduler, WASM engine, signing, AIS bootstrap, persistence & crypto primitives
Documentation

actr-hyper

Hyper — Actor platform layer + runtime infrastructure

Positioning

Hyper is the operating system for Actors: it defines boundaries (Sandbox), provides platform primitives, and carries the full runtime infrastructure (transport, routing, lifecycle management).

An Actor cannot open a database on its own, cannot hold its own private key, and cannot claim to be a certain type — everything must go through Hyper's controlled interfaces.

Responsibilities

Platform Layer (formerly Hyper)

  • Package signature verification (binary_hash + MFR signature)
  • Actor bootstrap (registers with AIS on behalf of the Actor, obtains credential)
  • Storage namespace isolation (independent SQLite space per Actor)
  • Cryptographic primitives (Ed25519 sign/verify, Actor does not hold raw private keys)
  • Runtime lifecycle management (ActrNode lifecycle for Executor execution bodies)

Runtime Infrastructure (formerly actr-runtime)

  • Actor Lifecycle: system init, node start/stop (ActrNode / ActrRef)
  • Message Transport: layered architecture (Wire -> Transport -> Gate -> Dispatch)
  • Communication Modes: in-process (zero-copy) and cross-process (WebRTC / WebSocket)
  • Message Persistence: SQLite-backed Mailbox (ACID guarantees)
  • Observability: logging, distributed tracing (OpenTelemetry, optional feature)
  • WASM Engine: WASM actor execution (optional feature)

Architecture Layers

┌─────────────────────────────────────────────────────┐
│  Platform (Hyper)                                   │  AIS Bootstrap
│  Sandbox / Verify / Storage / KeyCache              │  Package Verify
├─────────────────────────────────────────────────────┤
│  Lifecycle Management (ActrNode → ActrRef)
├─────────────────────────────────────────────────────┤
│  Layer 3: Inbound Dispatch                          │  DataStreamRegistry
│           (Fast Path Routing)                       │  MediaFrameRegistry
├─────────────────────────────────────────────────────┤
│  Layer 2: Outbound Adapters (internal)             │  HostGate
│           (Message Sending)                         │  PeerGate
├─────────────────────────────────────────────────────┤
│  Layer 1: Transport                                 │  Lane (core abstraction)
│           (Channel Management)                      │  HostTransport
│                                                     │  PeerTransport
├─────────────────────────────────────────────────────┤
│  Layer 0: Wire                                      │  WebRtcGate
│           (Physical Connections)                     │  WebRtcCoordinator
│                                                     │  SignalingClient
└─────────────────────────────────────────────────────┘

Non-Goals

Hyper does not understand business logic, does not perform business-level message routing, and is unaware of business relationships between Actors. The hyper_send/hyper_recv provided in WASM mode are network I/O primitives; routing decisions are made by the ActrNode running inside the WASM.