Player-facing

No unit sits in this category, and that absence is the point.

The Emitter's inventory covers entry points under tools/ and scripts/ — the machinery a developer, an operator or an agent invokes by name. Everything a player sees is rendered by the React client under app/src/game/, which holds no entry points and therefore contributes no unit pages.

The category is kept rather than deleted so that the gap stays visible. A tool that ships something a player sees would belong here, and its absence today is a fact about the inventory's scope rather than about the product.

For the player-facing surface itself, three places carry the answers.

Question	Where it is answered
What shape does data reach a panel in?	app/src/game/data/contract.mjs, the contract every panel is written against
What does a domain word mean?	CONTEXT.md, the glossary the code uses
Why does an unwired surface show a marked absence?	docs/adr/0010-live-surfaces-render-server-truth-or-marked-absence.md

Units in this area

Every unit in player-facing, with the page that documents it.

Unit	What it does