From a discussion about evidence systems to a real architecture improvement
A few hours ago we had a valuable discussion about a critical problem in knowledge and verification systems:
How do we prevent a graph from claiming more than its evidence can support?
This question directly influenced the next iteration of the MyZubster architecture.
The key insight:
A verification status is not evidence by itself.
A field like:
verification: confirmed
is only meaningful if the system can explain:
- Who confirmed it?
- How was it verified?
- Which source was checked?
- When was it observed?
- What are the limits of that verification?
What we implemented
Based on this discussion, we introduced a new layer:
Knowledge Claim
|
↓
Evidence Source
|
↓
Knowledge Attestation
|
↓
Verifier + Method + Timestamp
The goal is simple:
The graph should not declare truth.
The graph should preserve the chain of evidence behind a claim.
Contributor Knowledge Passport
At the same time, we built the first version of a Contributor Knowledge Passport.
Instead of representing contributors only through:
- payments
- wallets
- completed tasks
we are creating a model where contributions become connected to:
- rewards
- knowledge records
- evidence
- attestations
- reputation
A contributor is not only someone who receives a reward.
A contributor creates knowledge that can become part of the infrastructure.
Why this matters
Many systems today store outcomes:
"completed"
"verified"
"approved"
but they often lose the history behind those words.
We are experimenting with a different approach:
Every important statement should have provenance.
Not only:
"What happened?"
but also:
"How do we know?"
"Who observed it?"
"What supports this conclusion?"
Thank you to the builders who challenge assumptions
This improvement came from an external technical discussion and a contributor pushing the design question further.
Good architecture is not created by avoiding criticism.
It is created by turning the right questions into better systems.
The next steps:
Contributor
|
↓
Knowledge Contribution
|
↓
Evidence Graph
|
↓
Attestation Layer
|
↓
Reputation
Building in public means sharing not only features, but also the reasoning behind the architecture.
Thanks to everyone contributing ideas, reviews, and challenges.
The best systems are built when knowledge can flow back into the system itself.
opensource #softwarearchitecture #knowledgegraphs #AI #developers #web3 #buildinpublic