If you open the ApeScape Dev Hub right now, you do not see a fake everything is done dashboard. You see a narrow public window into active work, and that is exactly the point.
The current public tracker shows three visible beads, all marked In Progress, spread across multiple phases:
– APE-W001: WordPress community hub cyberpunk theme v2
– APE-N005: Genesis Era NFT collection metadata sync
– APE-A009: ApeChain Pulse integration
That is not a giant public epic wall, and we are not going to pretend it is. The Dev Hub is rank-filtered on purpose.
What matters is the pattern.
The visible work is not random. One bead is pushing the community hub, one is tightening the Genesis Era collection layer, and one is wiring in the ApeChain Pulse reporting surface.
The Dev Hub also makes the workflow explicit. It links the community site to three official repositories:
– ApescapeUnityPreBeta for Unity client and gameplay experiments
– ApescapeUnityPreBeta-beads for milestones and task tracking
– ApescapeUnityPreBeta-docs for architecture, scope, and contributor guides
The other momentum signal is how much supporting context landed alongside the tracker. The live Dev Log now includes posts for the Dev Hub overview, beads workflow explainer, scope between Unity pre-beta and browser prototype, docs repo onboarding, Genesis Era collection notes, and ApeChain Pulse daily report integration.
Taken together, that is a healthier signal than a vague promise list.
What is live now:
– the public Dev Hub on apescape.xyz
– the rank-filtered bead view with three visible in-progress items
– the Dev Log entries explaining workflow and scope
– the ApeChain Pulse footer/report integration on the site
What is still planned or still evolving:
– additional non-public beads beyond the Neon Visitor view
– future Unity systems and deeper MMO functionality
– lore-driven or utility-heavy mechanics not yet confirmed as live
ApeScape is still pre-beta. The browser prototype remains the current playable slice, and the Unity direction is still maturing.