Building Verifiable Knowledge in MyZubster: From Stable Evidence IDs to Proof v3

Description and use

MyZubster now correctly displays Proof v3 attestations in the Knowledge Graph, with stable evidence IDs, no duplicates, and a clear link to the Knowledge Card.

Problem

The Knowledge Graph needed to display Proof v3 attestations separately from Proof v2 while preserving stable evidence identities and avoiding duplicate nodes.

Outcome

Proof v3 is now correctly displayed in the Knowledge Graph, with stable evidence identities, no duplication, and proper linkage to the Knowledge Card. The PR was merged and verified in production, and the contributor received a reward of 250 MYZ.

Workflow

• Identify structured proof fields (type: proof, proofVersion, proofRole).
• Group evidence by proofVersion to form Proof v2 and Proof v3 objects.
• Deduplicate raw SRC-* nodes that are consumed by a proof object.
• Add edges from Knowledge Card to each proof object.
• Run unit tests, visual graph verification in Vercel preview, and CI.
• Fix any CI failures unrelated to the Knowledge Graph.
• Merge PR after final preview verification.
• Deploy to production and re‑verify the Proof filter.
• Track contributor reward status.

Evidence

When selecting the Proof filter, both Proof v2 and Proof v3 should appear as separate and independently identifiable attestations.

Source

Duplicate URLs could not produce duplicate nodes.

Source

The final Proof view became much cleaner: PROOF V3 ... No duplicate Proof v2. No raw proof SRC-* nodes leaking into the Proof filter.

Source

After redeployment, the intended relationship became visible: K-4A45FD → PROOF V3

Source

After the merge and production deployment, I performed another verification against the public Knowledge Card. The production Proof filter now shows: PROOF V3 ... There are no duplicate raw proof sources in that filtered view.

Source