Skip to content

Open standards playbook

This playbook decides how the Foundation’s research work becomes an open standard. Sources: the bundu-labs/bundu-standards AGENTS.md (the rule), the .cell issue bundu-standards#107 and owner messages dated below. Reviewed 2026-11-17.

  1. Adopt the global standard; where none exists, write one. Every standard the ecosystem uses is listed in the standards register with the body that maintains it. A Bundu standard is written only for what no existing standard defines, and everything inside it is adopted from others.
  2. A new standard starts as proposed. It is scoped on the owner’s instruction, recorded in an issue in bundu-standards, and listed in the register as proposed. Nothing in it is final until the owner approves the scope. Pages and articles say “proposed” wherever they mention it.
  3. Stress-test before adopting. Each pass runs a prototype against hostile cases, writes down what broke, and turns open questions into a decisions table for the owner. The owner works through the structure before anything is adopted (owner, 2026-11-17: “I need to fully understand and stress test the design and structure”).
  4. A standard lives with the project it maps to. When a standard maps directly to a Foundation project, its spec and prototype move to that project’s organisation, and the register points to it. The .cell maps directly to SiafuDB, so it lives in siafuDB/cell (owner, 2026-11-17). The spec and the project are checked against each other on every change.
  5. The register, the ecosystem record and llms.txt move together. A change to a standard’s status or home updates its register entry, the canonical ecosystem record at standards.bundu.org/ecosystem.jsonld, and the llms.txt of every site that mentions it, in the same round of work.
  6. Proposed is not shipped. Nothing calls a proposed standard live, adopted or in use. Tokens, for example, are a proposed Mukoko project and not on the current roadmap; no page claims token governance (owner, 2026-11-17).
  7. Merges follow the engineering rules. The spec repositories take changes through PRs into staging and release to main, and nothing merges while any check is red or orange (see the Releases playbook).
Step What happened
Need One record an entity owns that works offline, moves between a file and a database unchanged, and keeps its facts and prose from drifting apart. No standard defines it.
Scoped Owner’s instruction, 2026-11-17, bundu-standards#107. Status proposed, version 0.1.0 draft.
Adopted inside it JSON-LD 1.1, schema.org, CommonMark, RFC 8785 (JCS), VC Data Integrity, the Solid Protocol, JWE.
Stress-tested Pass 1: a prototype validator against hostile cases; open questions put to the owner as a decisions table.
Mapped to a project A cell is one entity’s data store, stored in SiafuDB and keyed by its @id; the SiafuDB Graph Sync Protocol carries it from device to cloud to pod.
Home siafuDB/cell, listed in the register at standards.bundu.org/cell.
Still open Size and bundling, encryption at rest, the IANA media type, and where the pod-side code lives.
  1. Check the register: if a global standard covers the need, adopt it and add it to the register instead.
  2. Open an issue in bundu-standards with the need, the standards it would adopt inside it, and the owner’s instruction verbatim.
  3. Add a proposed register entry and a draft spec with its open questions.
  4. Run a stress-test pass with a prototype, and record the results and a decisions table.
  5. If it maps to a Foundation project, give it a home in that project’s organisation.
  6. Update the ecosystem record and every affected llms.txt in the same round.
  7. Leave adoption to the owner.
  • The .cell decisions table from stress-test pass 1.