Design References
Hexis should borrow proven semantics without copying another framework’s product boundary. These references informed the target contract.
ROS 2 actions
ROS 2 actions model a long-running goal with feedback, a result, and cancellation. Navigation is the canonical example. Hexis adopts that semantic shape for game behavior, then adds script scopes, resource leases, world identity, and Minecraft-thread rules.
What Hexis should not copy is ROS’s distributed transport complexity. Actions are in-process contracts here.
Model Context Protocol tools
MCP tools pair names and human descriptions with input schemas and optional output schemas. That is a useful model for an AI-visible capability registry and structured results.
Hexis actions are not direct model tool calls. The model authors Lua policy; the local action runs at game speed without a model round trip for each tick.
Lua coroutines
The Lua 5.2 coroutine model
supports cooperative suspension and resumption. It is the conceptual basis for
a readable hexis.await surface.
Hexis still needs its own scheduler, budgets, and client-thread gateway. A coroutine alone does not make Minecraft access safe.
CC: Tweaked
CC: Tweaked’s parallel API shows how Lua authors can compose yielding tasks with wait-for-any and wait-for-all semantics. It also demonstrates the value of a searchable, example-rich Minecraft Lua reference.
Hexis intentionally offers higher-level protected behavior than a programmable turtle. The goal is not to force every user to build movement, perception, and recovery from primitives.
Docusaurus Mermaid
Docusaurus’s Mermaid theme provides native diagram blocks for this site. Architecture diagrams are kept beside the prose so changes to ownership and flow can be reviewed with the contract.
Evaluation principle
References justify a design choice; they do not prove it fits Hexis. Navigation and Galatea acceptance tasks remain the deciding evidence.