Whole-app UX concept for #220, captured 2026-08-21.
These are exploratory design mockups for discussion and iteration, not a pixel-exact implementation contract. Where the visual board conflicts with current authority, platform, or security contracts, the implementation constraints below are authoritative.
The original board is stored as eight review-friendly tiles preserving the full layout:
| Left | Right |
|---|---|
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
The board covers:
.eyespie share/export;The generated board contains a few exploratory actions/copy that must not be implemented as shown:
.eyespie is a document bundle. Use the native document picker / OS open-in or share flow. Do not expose a Gallery/Photos import source.GameId is non-mutating under the current local-authority contract. Do not offer Keep Both Versions or Replace Existing. Present the conflict and allow the user to cancel/back out unless a future authority-safe conflict contract is explicitly designed..eyespie bundle does contain gameplay data including target embeddings. Signatures provide integrity/provenance, not confidentiality; a recipient who controls their device can inspect bundle contents. Do not present the portable format as an anti-cheat or secrecy boundary..eyespie is the signed portable game format.