Status: Draft for first publish wave
Proposed slug: /community/glossary
Page type: system-reference
Owner: Riley
This page gives ApeScape readers and editors a shared vocabulary for first-wave wiki pages. Terms should stay traceable to the docs appendix and should not be expanded beyond what the source set can currently support.
Some definitions below are editorial scaffolding for the wiki package, not player-facing lore or guaranteed in-game terminology.
The ApeScape project and world brand. In the current source set, ApeScape is presented both as a live public website/community hub and as a Unity-first pre-beta game direction.
The ApeScape collection and gameplay concept centered on dungeon floors, discovery, progression, and ownership-related framing. Use this term carefully when a page mixes live collection copy with planned gameplay systems.
The blockchain ecosystem ApeScape publicly references for wallet onboarding, collection positioning, and future expansion language.
A live-roadmap phase label for stronger links between the WordPress/community surface and browser-play or build-related surfaces. This is roadmap language, not proof of a fully live bridge feature.
The public-facing ApeScape website and update surface. This is broader than a gameplay client and includes roadmap, whitepaper, dev-hub, and community-link functions.
A live-roadmap status label used for later-stage ideas that should not be written as guaranteed or release-ready.
A live-roadmap status label that means the public roadmap marks the phase as underway. It does not automatically prove every listed sub-feature is shipped.
A live-roadmap status label used for systems that are being explored or documented directionally rather than presented as implemented.
The upstream source that should win for a specific topic. For first-wave wiki work, source truth depends on topic: public-site status comes from the live site, while deeper Unity/system intent comes from repo-derived references.
The repo-derived plan and project-state layer used to explain ApeScape's deeper engineering direction and system sequencing.
These labels help editors write safely. They are not themselves claims about in-world canon.
Editorial label for the project's present posture after separating verified live-site status from repo-side engineering direction.
A wiki label for repo-derived product or system plans that describe intended Unity implementation but are not yet proven on the live public site.
A wiki editorial label for facts directly supported by the public site or other direct runtime proof in the current source set.
A wiki editorial label for future work that is named in a source but not yet proven live.