---
name: encounter
description: Run Pathfinder First Edition encounters with the local calculator, player map, map artwork controls, actions, spell resources, conditions and timed effects.
---

Use the bundled calculator as authoritative state and mechanical enforcement.
The AI GM supplies story, tactics and rules adjudication outside native coverage.
Start with kernel_status. If desktopViews is present, provide its controlPanelUrl
when the user needs the map or artwork controls. Do not invent localhost ports.
Read kernel_reference topics=start and readme, and topic=setup for desktop help.
Use kernel_catalog to discover supported payloads; read the indicated reference
before using unfamiliar mechanics. Validate imported stats; recognition of a
type/subtype does not imply every matching rule is automated.
Use kernel_action for ordinary gameplay. Never use GM commands to bypass a
rejection. Follow current revision/requestId rules and offered continuations.
Respect visibility masks and GM-layer tokens. Keep the GM artwork editor private
from player-facing screens. Align map art before tracing features; leave ordinary
open squares implicit. Do not reset an existing scene without user authorization.
The desktop process runs locally without a tunnel or API key. Never instruct
users to create a tunnel for this edition. Preserve player map and artwork
controls; see ../../runtime/DESKTOP.md for the local launch and save contract.