# Decisions and open questions

Status: release notes · Version 0.1.0 · 2026-08-21

## Decisions made for 0.1.0

- The four supplied Commons images are primary visual references and remain untouched.
- The visual system uses a 2:1 isometric basis, 128 × 64 px base tile, 0.25 m world unit and discrete zoom tiers.
- Beauty, relational dignity and place-ness are acceptance constraints, not post-processing.
- Component assets use transparent RGBA and neutral authoring light; Scene environment is resolved by the runtime.
- Portal states are architectural and material, not generic neon interface rings.
- Sources, Avatars, Ki, Allies and Actors retain explicit semantic and visual distinctions.
- Generated Scenes and specimen sheets are system demonstrations, not immutable visual canon.
- The package is engine-neutral by design.

## Documented limitations

- The 50 examples are specimen-sheet regions with full runtime records, not production-cut individual sprites or atlases.
- New Scenes are single painted reference images; they are not layered runtime exports.
- The Apiary reference includes contextual embodied workers. Runtime authors should still preserve canonical distinctions between Avatar, Ally and Actor in metadata and interaction.
- Typography and logo files are present for documentation Site fidelity; production licensing remains the implementer’s responsibility.
- No backend, authentication, multiplayer state or economy is implemented here.

## Questions for the next production pass

- Which zoom tiers and output pixel densities will the first runtime guarantee?
- Which Component families should be mastered as layered source files first?
- What is the canonical motion budget per device class and accessibility mode?
- How are Realm-specific material variants governed without fragmenting base Component identity?
- Which authoring application will own anchor and hit-region editing?
- What provenance format will be shared across human illustration, generated reference art and runtime transformations?

These are explicit next decisions, not silent gaps. Any answer that changes a contract requires a versioned release.