When not to use HyperToken

Choose another foundation when:

• a trusted server must be the sole author of outcomes or private state;
• the workload is high-frequency physics, media collaboration, or large append-only documents without a compaction/retention plan;
• a mature renderer, presence system, search/reporting stack, or workflow tool is the actual product need;
• strong identity, authorization, fair shuffle, or regulated settlement is a requirement rather than an application feature;
• conflicts cannot be represented, merged, or surfaced to users.

HyperToken is strongest for identifiable token entities, replayable rules, offline-first collaboration, and worlds whose conflicts have domain meaning. An authoritative server can still be used, but it does not remove the need to design projections, validation, quotas, and failure handling.