MyZubster, N4K48 and Neon Plaza
Over the last development cycle, we completed an important step in the evolution of MyZubster:
we connected real GitHub work, participant profiles, visual storytelling and the emerging MyZubster Metaverse into one navigable open-source structure.
The result is not just another profile page.
It is an experiment in connecting:
identity → project → visual world → technical work → evidence → ecosystem
while keeping a clear boundary between storytelling and independently verifiable technical progress.
N4K48 enters Neon Plaza
Nicola's MyZubster identity is represented by the character:
N4K48 // Explorer
His starting point is Neon Plaza, the visual entry layer of the MyZubster Metaverse.
The participant path is now represented as:
text
N4K48
↓
Neon Plaza
↓
Zorgax
↓
Project Planner + AI
↓
technical work
↓
tests / commits / evidence
↓
MyZubster ecosystem
The visual layer makes the journey understandable.
The repository remains the source of truth for what has actually been implemented.
The updated profiles
Daniel Ioni — MyZubster creator
My GitHub profile now includes the visual identity of the MyZubster ecosystem, including Neon Plaza, system architecture, ecosystem adoption, canonical entities and evidence-oriented visuals.
👉 https://github.com/DanielIoni-creator
Nicola — N4K48
Nicola's MVP repository now acts as his visual and technical participant profile.
👉 https://github.com/nicolaususnicola-lgtm/myzubster-mvp
His extended N4K48 profile:
👉 https://github.com/nicolaususnicola-lgtm/myzubster-mvp/blob/main/docs/N4K48.md
And the corresponding character record inside the main MyZubster repository:
👉 https://github.com/MyZubster-Ecosystem/myzubster/blob/main/docs/metaverse/characters/N4K48.md
Neon Plaza inside MyZubster
N4K48 is also presented directly inside the MyZubster Metaverse documentation.
👉 https://github.com/MyZubster-Ecosystem/myzubster/blob/main/docs/metaverse/README.md
This creates a bidirectional connection:
MyZubster
↕
N4K48
↕
Nicola's MVP
The participant repository links to MyZubster.
MyZubster links back to the participant.
The visual universe connects both sides.
Visuals are now versioned with the project
Another important change was moving the new visual material from temporary external references into the MyZubster repository itself.
We imported 14 visual assets covering areas such as:
Neon Plaza, LIFE, ecosystem architecture, canonical entities, system structure, adoption, cyberpunk characters and documentation/evidence.
They are now versioned alongside the project:
👉 https://github.com/MyZubster-Ecosystem/myzubster/tree/main/docs/visuals/drive-import-2026-09-03
The wider MyZubster visual universe remains available here:
👉 https://github.com/MyZubster-Ecosystem/MyZubster-Visual
This means the visual layer can evolve through the same Git workflow as documentation and code.
What is real today?
One principle matters a lot in this experiment:
visual storytelling is not technical evidence.
Neon Plaza, N4K48 and the cyberpunk universe provide navigation, identity and storytelling.
Actual technical progress is demonstrated through repositories, commits, tests, CI results and reproducible implementations.
For example, Nicola's MVP already documents work around observation APIs, JSON persistence, validation, Docker, health checks, Gunicorn, clean shutdown handling and a local AI/RAG stack using Ollama and Qdrant.
The visual profile helps expose that work.
It does not replace the evidence.
Zorgax as the guide layer
Zorgax is becoming the navigation and assistance layer between the participant and the ecosystem.
The idea is that a contributor should not only see a repository.
They should be able to understand:
Where am I?
What am I building?
What is the next mission?
What evidence exists?
What is still only planned?
What can be verified?
This is where the Project Planner + Zorgax path becomes interesting.
Instead of inventing progress or badges, the system can eventually derive progression from real project state.
From GitHub profile to ecosystem identity
Traditional GitHub profiles are good at showing repositories and contribution activity.
We are experimenting with an additional layer:
GitHub identity
↓
visual participant
↓
project role
↓
ecosystem navigation
↓
technical evidence
For N4K48, that means a developer can move conceptually from Neon Plaza to Zorgax, from Zorgax to the Project Planner, and from the planner to actual repository evidence.
For MyZubster, it means contributors can become understandable parts of a larger system without losing the transparency of open source.
What we completed
During this iteration we completed the visual import into MyZubster, the bidirectional N4K48/MyZubster connection, local repository-hosted Neon Plaza imagery, the updated Daniel GitHub profile, the updated Nicola/N4K48 profile and the visual links between participant identity, Zorgax, the Metaverse and technical evidence.
Everything remains based on GitHub-readable artifacts rather than hidden status claims.
Explore
MyZubster Core
https://github.com/MyZubster-Ecosystem/myzubster
MyZubster Visual
https://github.com/MyZubster-Ecosystem/MyZubster-Visual
Daniel Ioni
https://github.com/DanielIoni-creator
Nicola / N4K48
https://github.com/nicolaususnicola-lgtm/myzubster-mvp
N4K48 inside MyZubster
https://github.com/MyZubster-Ecosystem/myzubster/blob/main/docs/metaverse/characters/N4K48.md
Neon Plaza
https://github.com/MyZubster-Ecosystem/myzubster/blob/main/docs/metaverse/README.md
MyZubster is still evolving.
The current direction is to connect open-source development, real-world observations, AI-assisted workflows, participant identities and visual storytelling — while keeping a strict distinction between concept, implementation and verified evidence.
That distinction is what can make a visual ecosystem useful rather than merely decorative.
#opensource #github #ai #webdev
Top comments (0)