# Pet evidence

## Atlas contract

The retained Clawa fixture establishes Pi Pet's Codex-v2 `1536x2288`, 8×11, `192x208` atlas: nine standard action rows, sixteen clockwise look directions, and the minimal `pet.json` package. Clawa's committed validation reports no errors or warnings.

OpenAI's public Hatch Pet skill confirms deterministic spritesheet creation, validation, visual QA, and `pet.json` packaging for the legacy 8×9 contract: <https://github.com/openai/skills/tree/main/skills/.curated/hatch-pet>

Codex issue #20863 documents that current animation timing, chaining, and activity triggers are hardcoded rather than pet-manifest driven: <https://github.com/openai/codex/issues/20863>

Codex issue #21657 requests click, hover, drag, and first-party action hooks, indicating those interaction APIs are not currently available: <https://github.com/openai/codex/issues/21657>

## Pi and GipPity integration

Pi's extension API provides lifecycle, tool, settlement, and user-message primitives. GipPity Remote already reduces those events into browser activity, carries complete bounded Pi events, accepts synchronized prompts, and owns realtime voice. Pi Pet therefore registers a static miniapp and reaction snapshot instead of reproducing those transports.

The browser-to-Pi prompt bridge and transparent desktop presentation are Pi/GipPity additions, not claims of Codex desktop parity.