Architecture

HyperToken is split into a CRDT domain layer, an engine coordination layer, transport and storage integrations, and example applications. The source entry point is core/index.ts, published as dist/core/index.js; it re-exports the core primitives and Engine.

Area	Source responsibility
core/	Chronicle, immutable tokens, containers, events, sync abstraction, and storage contracts.
engine/	Dispatch, actions, rules, policies, agents, game loop, history, persistence, fork/merge, and network coordination.
network/	WebSocket/WebRTC peer transports, relay and authoritative server implementations, and message encoding.
core/storage/	Memory, filesystem, and IndexedDB adapters.
core/browser/	esbuild browser bundling, shims, and Automerge WASM packaging.
examples/	Blackjack, Cuttle, and Watershed consumers.