Research
··3 min readHow to see what we have built
Five public addresses you can open today with no account: the standards register, the vocabulary, the source repository, the published standards and a product that uses them, plus three commands to verify the register yourself.
You should not have to take our word for any of this. Everything below is public, needs no account, and can be checked from a browser or a terminal.
Five addresses
1. The standards register
The full list of external standards the platform builds on, grouped by area. Each standard has its own page with what it governs, the version we commit to, who stewards it, when and why we decided, and a link to the specification. Try UCUM, the standard for units of measure.
The same list is available to machines at standards.bundu.org/register/index.json.
2. The vocabulary
The terms Bundu publishes for concepts that schema.org has no word for. Open a term such as Family in a browser to read it, or ask for the machine form and the same address returns JSON-LD. The next article explains how this differs from the register.
3. The source
github.com/bundu-labs/bundu-standards
The public repository. The register is in register/register.yaml, with a generated readable version in register/REGISTER.md. The rule we follow is written at the top of AGENTS.md, and docs/where-things-live.md says which file or system holds which fact.
4. The standards we publish ourselves
Where no global standard exists, we build one and publish it. The Bundu AI Guardrails Standard is an example, and its twelve rules are also terms in the vocabulary.
5. A product that will use them
Mukoko weather is the first product we are applying the rule to. Converting data from other sources to standard names, units and codes before it is stored is in review in the weather codebase and is not yet in production, so today this is the place to watch rather than the proof.
Check it yourself
These three commands need only curl and a hash tool.
1. Ask for the newest commit of the register
curl -s https://standards.bundu.org/register/latest
The answer names a commit and the address of each of the four published files at that commit.
2. Fetch a file at an exact commit
curl -s https://standards.bundu.org/5cd756d48e283a644b3d2b4800b53247a2aa9175/register/register.yaml -o register.yaml
A commit never changes, so the answer is cached for a year.
3. Check it has not been altered
sha256sum register.yaml
For that commit the result should be:
20e928f641918b6526780f9eff263c270610d70a1f088b2f339dd657c753f64e
This is how our own infrastructure repository uses the register. It records the commit and the hash of each file, and refuses a download that does not match. The address you fetch from is a convenience. The hash is what is trusted.
What you will not find yet
In the interest of not overclaiming: the register is complete and public, but a scheduled check that compares the database with it is planned, not running, and the site's own automatic deployment is not yet switched on. The first article, What we have set up, lists what is built and what is only decided.
If you see something wrong
The repository is public, and the register is meant to be argued with. If a standard is missing, out of date, or wrongly described, open an issue there.