MyZubster Contributor Network: Independent Projects, Verifiable Evidence, Clear Roles
Open-source collaboration works best when contributors can keep control of their own projects while still proving how their work connects to a wider ecosystem.
That is the direction we are taking at MyZubster.
We are building an evidence-first contributor network where a person can keep their own GitHub repository, local Docker environment, VPS, research package, documentation project, or software prototype. MyZubster connects only what is explicitly documented and consented to: public evidence, reproducible test checkpoints, interfaces, and reviewed project links.
This is important because a GitHub fork, a merged pull request, a public profile, a DAO role, a bounty, and a LIFE-oriented pilot are not the same thing.
The connection model
independent contributor project
→ public evidence
→ documented interface or test fixture
→ reproducible checkpoint
→ reviewed result
→ optional Knowledge / Passport / pilot link
A successful test proves only the exact thing that was tested. It does not automatically prove payment, institutional partnership, production readiness, scientific validation, or membership in a DAO or EU project.
Contributors and projects
Nicola / N4K48 — independent pilot node
Nicola’s N4K48 project is an independent Docker-based MyZubster pilot node. It demonstrates a practical model: contributor-owned runtime, public repository history, reproducible evidence, and bounded read-only interoperability.
The next proposed step is an authenticated and sanitized N4K48 ↔ MyZubster checkpoint. Nicola retains ownership and control of the project.
khongten124 — Open Period Care research and evidence
This work is connected as a research and evidence package. The public contribution supports structured provenance, requirements mapping, and technical review.
It does not claim medical validation, product efficacy, or institutional endorsement.
Aming9303 — gateway, sensors, replication, webhooks
These contributions are relevant to future data and interoperability pilots. They can support a future Circular Water architecture, for example, without implying access to a utility’s systems or data.
wasim-builds — security and local resilience
Wasim is working on a proposed local Tor/HAProxy resilience design. The boundary is clear: isolated configuration, threat model, health checks, rollback, and redacted test evidence first.
No public deployment, production access, reimbursement, or paid work is implied.
foxxx009 — KPI and evidence framework
Their public work helps establish a useful principle: measurable evidence, reproducible tests, and clear status labels are more valuable than vague claims of participation.
Shweta Singh — proposed verifier path
Shweta’s technical-verifier path is still proposed and consent pending. A public fork is useful starting evidence, but it is not enough to claim a completed contribution or verified role.
DAO, Passport, and LIFE: three different states
We are making these boundaries explicit.
- DAO participation requires an opt-in to a specific responsibility. It does not automatically grant financial, deployment, merge, or treasury authority.
- A public Contributor Passport requires explicit publication consent. A GitHub contribution does not automatically create or publish one.
- A LIFE-oriented pilot is an internal candidate track unless there is a real authorized partner, formal consortium, or funding decision.
This matters especially for future cases such as kefir and Circular Water. Independent contributors can build reusable components—data schemas, KPI dashboards, node interoperability, verification tools, and provenance records—before a university, utility, or other partner authorizes real operational data.
Current coordination
We recently opened Contributor Operations v1, with three tightly bounded work lanes:
- Contributor Passport privacy and explicit publication consent.
- N4K48 authenticated interoperability.
- Local-only Tor/HAProxy resilience documentation and review.
The public README status index is being added in PR #1606.
Join the network
If you have an independent project, repository, dataset, test suite, design system, research package, or infrastructure experiment, you do not need to give up control of it to collaborate.
Bring:
- one bounded objective;
- public or authorized evidence;
- a reproducible environment or test plan;
- clear privacy and security boundaries;
- an honest description of what has and has not been tested.
Then we can connect the work responsibly.