From Static Page to Evidence-Aware Knowledge Explorer: What We Implemented in MyZubster
MyZubster Knowledge Explorer started as a static page listing domains and canonical records.
The content was useful, but the interaction model was too flat: domains, records, evidence states and details all competed for attention in one page.
We rebuilt the explorer as a lightweight, evidence-aware static interface and deployed it to Vercel.
Live page:
https://myzubster-knowledge-myzubster.vercel.app/knowledge.html
The implementation
The deployment remains intentionally simple:
public/
└── knowledge.html
No framework runtime. No additional backend. No database migration.
The page contains:
- responsive CSS;
- a client-side record registry;
- dynamic domain navigation;
- full-text search;
- evidence-state filtering;
- selectable record cards;
- an inline detail panel.
The record model is minimal:
{
id: "MZ-001",
title: "Knowledge Layer — canonical record protocol",
domain: "MyZubster",
state: "PROTOCOL",
description: "Defines the Knowledge Explorer as a catalogue of traceable records..."
}
This is enough to make records searchable, classifiable and inspectable without pretending that the UI is already a full verification system.
Evidence states are part of the data model
The key decision was to make evidence classification explicit:
PERSONAL_PRACTICE
OBSERVATION
EXTERNAL_SOURCE
PROTOCOL
These are not visual tags only.
They communicate what a record is:
- a first-hand practice;
- a documented observation;
- an identifiable external source;
- or a proposed protocol.
A record can be useful without being verified guidance.
That distinction is essential when the catalogue includes technical workflows, community practices, circular-economy proposals and health-adjacent product knowledge.
Filtering records
The page combines domain selection, evidence state and text search in one filtering function:
const list = records.filter((record) =>
(active === "All" || record.domain === active) &&
(!state || record.state === state) &&
`${record.id} ${record.title} ${record.domain} ${record.description}`
.toLowerCase()
.includes(query)
);
This keeps the first version dependency-free and deterministic.
For a small catalogue, a client-side array is enough. For a larger knowledge base, the next step is build-time index generation from versioned source files.
New MyZubster protocol records
We introduced a dedicated MyZubster domain:
MZ-001 — Knowledge Layer — canonical record protocol
MZ-002 — Evidence states — from collection to independent review
MZ-003 — Zorgax — AI assistance with human verification
MZ-004 — Development requests — turning patterns into testable work
MZ-005 — Circular economies — verified contribution model
These records capture the architecture behind the project:
- AI assists with retrieval, structure and connections;
- AI does not determine truth;
- data integrity is not the same as scientific validity;
- observed patterns can become scoped development requests;
- digital evidence alone does not prove a physical-world outcome.
Circular economies and absorbent-product knowledge
We also added a new Circular economies domain:
AHP-001 — Circular Hygiene — evidence pilot framework
AHP-002 — Absorbent-product experience contribution model
AHP-003 — Absorbent materials — test and traceability template
AHP-004 — Circular economies — reproducible pilot catalogue
All are marked PROTOCOL.
This is intentional. They define ways to collect observations, trace materials and structure future tests. They do not claim that recycling performance, safety, comfort or environmental impact has already been independently validated.
A possible contribution path looks like this:
lived experience
→ documented observation
→ repeated pattern
→ DevelopmentRequest
→ prototype or research task
→ independent review
The important part is the boundary: user experience can guide product development without being misrepresented as clinical or scientific proof.
Deployment and validation
Before deployment, we checked the static JavaScript syntax:
node -e '
const fs = require("fs");
const source = fs.readFileSync("public/knowledge.html", "utf8");
const script = source.match(/<script>([\s\S]*?)<\/script>/)[1];
new Function(script);
console.log("JavaScript valid");
'
We then confirmed that the new canonical IDs existed in the file:
grep -n "MZ-001\|AHP-001\|Circular economies" public/knowledge.html
Finally, we created a timestamped backup and deployed through the existing Vercel project:
cp public/knowledge.html \
"public/knowledge.html.bak.$(date +%F-%H%M%S)"
vercel --prod --yes --scope myzubster
What comes next
The current implementation is a practical static layer. The next technical steps are:
- move records to Markdown files with YAML front matter;
- validate record schemas in CI;
- generate the domain index at build time;
- add stable routes for individual records;
- link records to sources, evidence and Development Requests;
- add consent-aware contribution flows;
- add independent review before any record is promoted to verified guidance.
Final thought
The goal is not to build another content directory.
The goal is to build a knowledge interface where uncertainty is visible, evidence is classified and contributions can evolve into testable work.
A static page is only the first layer. The real architecture is the discipline of not confusing a claim, an observation, an AI summary and a verified result.