02
Reusable runtime · SDK
CharaWeave
A character interaction runtime that keeps behavior, memory, surface, host integration, and autonomy as separate boundaries.
Distribution in progress
- Period
- 2024 — present
- Role
- Runtime engineer
Problem
02When character interaction is fused to one application, it becomes difficult to reuse across products and platforms.
Constraints
- Stable contracts must not depend on internal implementation.
- Browser and React bindings should remain opt-in edges.
- A release candidate is not a final public release.
Engineering decisions
- Separate stable, internal, and public package layers.
- Keep a platform-neutral runtime at the center and adapters at the edge.
- Validate clean Vanilla and React consumers independently.
Implementation
- A pnpm workspace for runtime, content, host, browser, React, and policy packages.
- Architecture and documentation checks that enforce package and release boundaries.
- Browser acceptance for lifecycle, motion, presence, and host binding behavior.
Verification / evidence
Runtime playgroundobserved
This page uses a real browser acceptance screenshot showing character policy and runtime diagnostics.
Package boundariesobserved
Stable, internal, and public layers are separated in the repository.
Consumer checksreported
Release evidence records clean Vanilla and React consumer validation.
Result / current state
CharaWeave shows how to build a reusable runtime without turning the portfolio into a client-heavy demo.