Connecting N4K48 and Nicola Comics to MyZubster: Building a Public Zorgax Integration
We are building a new experimental connection inside the MyZubster ecosystem:
Nicola / N4K48 × Nicola Comics × Zorgax × MyZubster
The experiment started locally.
Now we are moving toward something more interesting:
Can an independent contributor build their own project, expose a controlled API, connect it to Zorgax, and become a publicly reachable node of the MyZubster ecosystem?
Nicola / N4K48 is helping us test this model.
And this time we are not interested only in building the integration.
We also want to deploy it, measure it, document it and verify what actually works.
Explore the Projects
MyZubster Marketplace Demos
https://www.myzubster.com/marketplace-demos?utm_source=devto&utm_medium=article&utm_campaign=n4k48_zorgax_pilot&utm_content=marketplace_demos
MyZubster GitHub
https://github.com/MyZubster-Ecosystem/myzubster?utm_source=devto&utm_medium=article&utm_campaign=n4k48_zorgax_pilot&utm_content=myzubster_github
MyZubster Visual Universe
https://github.com/MyZubster-Ecosystem/MyZubster-Visual?utm_source=devto&utm_medium=article&utm_campaign=n4k48_zorgax_pilot&utm_content=visual_universe
Nicola / N4K48 GitHub Profile
https://github.com/nicolaususnicola-lgtm?utm_source=devto&utm_medium=article&utm_campaign=n4k48_zorgax_pilot&utm_content=n4k48_profile
N4K48 × MyZubster
https://github.com/nicolaususnicola-lgtm/myzubster?utm_source=devto&utm_medium=article&utm_campaign=n4k48_zorgax_pilot&utm_content=n4k48_myzubster
Nicola Comics / N4K48 MVP
https://github.com/nicolaususnicola-lgtm/myzubster-mvp?utm_source=devto&utm_medium=article&utm_campaign=n4k48_zorgax_pilot&utm_content=nicola_mvp
N4K48 Metaverse Roadmap
https://github.com/nicolaususnicola-lgtm/myzubster/blob/main/ROADMAP_N4K48_METAVERSE.md?utm_source=devto&utm_medium=article&utm_campaign=n4k48_zorgax_pilot&utm_content=n4k48_roadmap
Public Integration Tracking — MyZubster Issue #1176
https://github.com/MyZubster-Ecosystem/myzubster/issues/1176?utm_source=devto&utm_medium=article&utm_campaign=n4k48_zorgax_pilot&utm_content=integration_issue
Who is N4K48?
N4K48 is Nicola's experimental persistent digital identity inside the MyZubster universe.
The project connects several layers:
Nicola
↓
N4K48
↓
Neon Plaza
↓
Project / Nicola Comics
↓
Zorgax
↓
MyZubster
N4K48 is therefore more than a visual character.
The experiment is trying to connect digital identity, software development, creative work, AI-assisted workflows and verifiable technical activity.
The visual/metaverse environment provides the narrative layer.
The repositories, APIs, Docker services, tests and evidence provide the technical layer.
Keeping those two layers clearly separated is important.
Nicola Comics × MyZubster
The next stage of the experiment uses Nicola Comics as a concrete integration case.
Nicola has created three N4K48 comic panels documenting the journey from a software idea toward AI, MyZubster and the experimental Neon Plaza environment.
Instead of treating the comics only as static images, we are turning the collection into a small structured service.
The pilot exposes a comics catalog through an API.
For example:
GET /api/comics
A Zorgax-facing adapter is also available through:
POST /api/zorgax/ask
The current adapter uses four explicit operations:
gallery
detail
candidate
next_steps
This means Zorgax does not need direct control of Nicola's application.
It asks a controlled interface for specific information.
What Has Already Been Tested?
The Docker-based pilot has already been manually validated locally.
The main workflow reported by the pilot is:
gallery → PASS
detail → PASS
candidate → PASS
next_steps → PASS
The catalog contains three N4K48 comic panels.
The first selected comic is currently classified as:
NFT_CANDIDATE
PROPOSED_FOR_REVIEW
Its rights state remains:
TO_VERIFY
And this distinction is fundamental.
We are not claiming that an NFT has already been minted.
A candidate is not a minted NFT.
A proposed asset is not verified ownership.
A visual is not blockchain evidence.
Contract address, token ID and transaction hash should only be published as verified data when real on-chain evidence exists.
Why the Zorgax Adapter is Read-Only
The current integration deliberately limits what Zorgax can do.
Zorgax can help users:
- discover the comics;
- inspect a comic;
- identify the current candidate;
- understand its evidence state;
- obtain the next recommended steps.
But it does not automatically:
- modify Nicola's catalog;
- execute payments;
- access a wallet;
- mint an NFT;
- change rights information;
- fabricate blockchain evidence.
This gives us an important architectural boundary:
AI assistance
↓
Controlled API
↓
Project data
↓
Human / external verification
AI can help navigate the process without automatically becoming the authority that verifies it.
What Are We Building Now?
The local connection is only the first milestone.
We are now working toward:
LOCAL MVP
↓
PUBLIC HTTPS DEPLOYMENT
↓
PUBLIC ZORGAX CONNECTION
↓
END-TO-END TEST
↓
TRAFFIC / USAGE MEASUREMENT
↓
DOCUMENTED EVIDENCE
Nicola's service currently needs to become reachable through a public HTTPS endpoint.
That allows the public MyZubster/Zorgax environment to communicate with the pilot without accessing Nicola's local computer.
The target architecture becomes:
USER
↓
MYZUBSTER
↓
ZORGAX
↓ HTTPS
NICOLA COMICS API
↓
GALLERY
↓
DETAIL
↓
CANDIDATE
↓
RIGHTS / EVIDENCE
↓
NEXT STEPS
Measuring the Experiment
Another part of this experiment is attribution.
If somebody discovers N4K48 through this DEV.to article, we want to distinguish that traffic from other MyZubster traffic.
That is why the project links in this article use campaign parameters such as:
utm_source=devto
utm_medium=article
utm_campaign=n4k48_zorgax_pilot
Each important destination also receives its own utm_content.
For example:
utm_content=myzubster_home
utm_content=zorgax
utm_content=marketplace_demos
utm_content=n4k48_profile
utm_content=nicola_mvp
This creates a clearer attribution model:
DEV.to article
↓
tracked link
↓
MyZubster / Zorgax
↓
visitor journey
↓
analytics
Where analytics is configured on the destination, this can help us understand which public communication actually sends users into the ecosystem.
We Don't Want Vanity Metrics
Traffic alone is not success.
This distinction matters:
CLICK
≠
VISITOR
≠
ACTIVE USER
≠
ZORGAX REQUEST
≠
SUCCESSFUL API CALL
≠
COMPLETED WORKFLOW
≠
VERIFIED OUTCOME
A DEV.to article could generate clicks without anybody completing the experiment.
So our objective is eventually to understand the complete journey.
For example:
DEV.to
↓
MyZubster
↓
N4K48 discovered
↓
Zorgax opened
↓
Nicola Comics requested
↓
gallery
↓
detail
↓
candidate
↓
next_steps
That is much more useful than simply saying:
"The page received X visits."
We want to know whether the architecture is actually being used.
Why Are We Doing This?
The larger objective goes beyond Nicola Comics.
We want to explore whether MyZubster can support independently maintained projects without forcing everything into one centralized application.
Imagine:
Nicola Comics ──────────┐
Research Lab ───────────┤
Student Projects ───────┤
Agriculture ────────────┤
Circular Economy ───────┼── ZORGAX ── MYZUBSTER
Local Services ─────────┤
Community Projects ─────┤
Creative Projects ──────┘
Each participant could maintain their own:
identity
repository
project
service
API
data
documentation
evidence
while exposing a controlled interface that Zorgax and MyZubster understand.
A Federated MyZubster
This is the architectural idea we are testing.
Instead of:
EVERYTHING
↓
ONE CENTRAL APPLICATION
we can experiment with:
INDEPENDENT PROJECT A ─ API ─┐
INDEPENDENT PROJECT B ─ API ─┤
INDEPENDENT PROJECT C ─ API ─┤
↓
ZORGAX
↓
MYZUBSTER
The independent project remains responsible for its own service.
MyZubster provides the ecosystem.
Zorgax provides discovery, guidance and AI interaction.
Analytics helps us understand usage.
Evidence tells us what has actually been demonstrated.
Evidence First
The most important principle behind this pilot remains:
Do not claim more than the evidence demonstrates.
A local test is a local test.
A deployment is a deployment.
A click is a click.
An API response is an API response.
An NFT candidate is an NFT candidate.
A verified blockchain transaction requires blockchain evidence.
A verified right requires provenance or rights evidence.
A production system requires production evidence.
Our working process is therefore:
OBSERVE
↓
DOCUMENT
↓
BUILD
↓
TEST
↓
DEPLOY
↓
CONNECT
↓
MEASURE
↓
VERIFY
↓
PUBLISH
The Final Goal
The final goal is not simply to put Nicola's comics online.
We want to demonstrate a reusable model where an independent creator, developer, researcher, student or community project can become a connected MyZubster node.
A future participant could bring:
IDENTITY
+
PROJECT
+
GITHUB REPOSITORY
+
PUBLIC SERVICE
+
API
+
ZORGAX CONNECTION
+
ANALYTICS
+
EVIDENCE
and progressively move through clear states:
PROPOSED
↓
IMPLEMENTED
↓
TESTED
↓
DEPLOYED
↓
CONNECTED
↓
MEASURED
↓
VERIFIED
Nicola / N4K48 is helping us test this model with a real project.
The local Nicola Comics × Zorgax workflow gives us the first technical foundation.
The next milestone is clear:
Public HTTPS deployment → public Zorgax connection → end-to-end test → traffic attribution → documented evidence.
If this succeeds, Nicola Comics will give us more than another demo.
It will give us a replicable integration pattern for future MyZubster contributors.
Build → Connect → Deploy → Measure → Verify → Document → Replicate.
Follow and Test the Experiment
Enter MyZubster
https://www.myzubster.com/?utm_source=devto&utm_medium=article&utm_campaign=n4k48_zorgax_pilot&utm_content=final_cta
Explore Marketplace Demos
https://www.myzubster.com/marketplace-demos?utm_source=devto&utm_medium=article&utm_campaign=n4k48_zorgax_pilot&utm_content=final_marketplace_cta
Explore Nicola Comics / MVP
https://github.com/nicolaususnicola-lgtm/myzubster-mvp?utm_source=devto&utm_medium=article&utm_campaign=n4k48_zorgax_pilot&utm_content=final_nicola_mvp_cta
Follow the public integration
https://github.com/MyZubster-Ecosystem/myzubster/issues/1176?utm_source=devto&utm_medium=article&utm_campaign=n4k48_zorgax_pilot&utm_content=final_issue_cta
