Nav mesh

Ask: baked-static | dynamic-carve | off.

Ownership

nav-mesh owns agent traversability, path requests, authored traversal links, and nav revisions. Physics/collision stays with the engine or collision-layers; hazards stay hazard-volume; door/quest truth stays with its gameplay owner.

Contract

For every navigation profile publish:

• agent_profile_id
• radius / height / step / slope limits
• movement capabilities such as walk, jump-link, climb-link, swim-link
• current nav_revision

For every path request publish request_id, start/end, profile, nav revision, result and first failure reason.

Static geometry may be baked. Runtime changes may use carving, tiled rebuilds, authored links, or another engine-supported update strategy. Opening a door does not universally require a full rebuild. Update only the connectivity representation the project actually uses.