We started MyZubster with a very simple real-world question:
What happens if I give someone my kefir culture, they reproduce it at home, document what they learn, and later become a donor themselves?
That question is becoming a much broader protocol.
MyZubster is being developed as an open knowledge and provenance network where people can share not only physical resources, but also skills, practices and experience.
The basic knowledge loop is:
Share → Try → Observe → Improve → Share again
🥛 From kefir to a traceable community chain
Our first concrete use case is milk kefir.
Instead of simply saying:
Daniel gives kefir to Nicola
we want to represent the process as a sequence of independently traceable events:
Daniel's culture → marketplace listing → Nicola accepts → hand exchange → Nicola confirms receipt → Nicola maintains his own culture → Nicola documents observations → Nicola can later donate his surplus
The project already contains several canonical kefir Knowledge Cards, beginning with KF-001.
The important principle is that we do not silently invent missing information.
If quantities, temperatures, times, outcomes or conditions were not documented, they remain UNKNOWN.
🧠 Knowledge can propagate too
Physical resources are only half of the idea.
Daniel has also been helping Nicola learn practical MyZubster workflows involving GitHub, Docker and project documentation.
We therefore started modelling a second chain:
Daniel → Nicola learns → Nicola reproduces a practice → Nicola can teach another participant → that participant produces independent evidence
This is documented in DEV-001 and DEV-002.
The learner does not inherit the mentor's evidence or verification.
Every new person creates another observable branch of the knowledge graph.
🎨🥊🤸 Now we're expanding beyond software and fermentation
We have just expanded the domain registry with:
ART → ART-*
MUSIC → MUS-*
SPORT → SPT-*
MARTIAL_ARTS → MA-*
and expanded the existing:
SOUNDSYSTEM → SND-*
This means MyZubster can model scenarios such as:
Tekno / Sound System
A sound-system builder offers a session → another person accepts → they assemble or operate part of a system → the result is documented.
Music
A musician teaches another person an instrument, DJ workflow, production technique or performance practice → the learner tries it → evidence can be attached.
Art
An artist teaches drawing, comics, digital art or another technique → the learner creates their own work → authorship and provenance remain separate and traceable.
Calisthenics
A practitioner teaches a bounded progression or movement → another participant attempts it → observations are recorded without turning them into medical claims.
Thai boxing
A practitioner or appropriately documented coach teaches a bounded technique or padwork session → participation and the learner's attempt can be recorded while preserving safety context and any distinction between community practice and formal coaching credentials.
We have already started concrete cards connected to Daniel:
ART-001 — comics practice
SPT-001 — calisthenics practice
MA-001 — Thai boxing practice
🛒 Skills meet the marketplace
This gives the MyZubster marketplace another possible object besides physical goods.
A listing can represent:
physical resource / donation
skill lesson
mentoring
workshop or demonstration
collaboration request
The general skill flow we're designing is:
Teacher → Skill Listing → Learner Accepts → Session → Learner Confirms → Learner Attempts → Evidence → MyZubster Record
And eventually:
A teaches B → B reproduces → B teaches C → C reproduces
This turns knowledge into something that can propagate through a community while retaining provenance.
⛓️ What blockchain means here
We're being deliberately conservative with this word.
A MyZubster event should only be called ONCHAIN_RECORDED when an actual blockchain record exists and we can attach things such as the network and transaction/record hash.
A blockchain transaction can demonstrate that a particular commitment or declaration was recorded.
It does not, by itself, prove:
that somebody mastered a skill;
that a lesson was good;
that somebody is professionally qualified;
that a physical exchange actually occurred exactly as described;
or that every statement committed on-chain is true.
The evidence and the blockchain provenance therefore remain related but distinct.
🧬 Two graphs start interacting
This is where the experiment gets interesting.
We can have a resource graph:
Daniel → kefir → Nicola → new culture → next donor
and a knowledge graph:
Daniel → Nicola → reproduced skill → new learner → new reproduction
Those graphs can intersect without being confused with each other.
A person can simultaneously become a custodian, donor, learner, contributor and eventually mentor.
🔬 Where we are now
The repository currently contains the domain registry, evidence states, Knowledge Cards, knowledge graph tooling, provenance/integrity tooling, collaboration records, reproduction/version records, transaction/recovery logic, the new Resource + Knowledge Transfer Protocol and the new Skill Marketplace Protocol.
Our local test suite was last confirmed green at 110/110 tests before the newest domain/card additions; those latest changes still need the next complete test run before we claim them as green.
The public Knowledge Explorer is here:
MyZubster Knowledge Explorer
The open-source repository is here:
MyZubster Fermentation Kefir on GitHub
The live deployment is currently behind the newest GitHub commits, so the repository is the source to follow for the latest work until the next production deployment.
🚀 What's next?
The next step is moving these concepts from protocol documents into structured runtime records:
Skill Listing → Acceptance → Session → Evidence → Knowledge Graph → optional verifiable on-chain record
Then we can start reproducing the experiment with real participants.
The larger question MyZubster is exploring is simple:
Can a community build a traceable graph not only of what people own or exchange, but of what they actually try, learn, reproduce and pass on to somebody else?
That's what we're building.
Top comments (0)