The role this site plays
Standards need
an implementation map.
The official repository is where proposals are authored, reviewed, and improved. OpenStandards is where an implementer sees how those parts form a working Metanet system.
Strategic position
Not another BRC browser.
The unfilled job is implementation navigation: deciding which interfaces belong in a build, understanding their dependencies and replacements, and finding code that demonstrates interoperability.
Editorial policy
Source and guidance never masquerade as each other.
- 01
Upstream is authoritative.
Full BRC text, authorship, issues, and change history belong to the official repository. Every mirrored page links to its exact source.
- 02
Status is evidence, not decoration.
When a specification contains a status note, the site surfaces it prominently. We do not infer formal maturity from age, number, or popularity.
- 03
Curation answers implementation questions.
Build paths and “where this fits” notes are original OpenStandards guidance. They are visually separated from normative content.
- 04
Implementations are examples.
Links show that a standard can be implemented; they do not turn one package or vendor into the standard itself.
- 05
Corrections go to the right place.
Specification changes should be proposed upstream. Map, usability, or editorial corrections belong with this site.
Source model
Fast pages, reproducible content.
Every standard page is pre-rendered from a pinned snapshot of bsv-blockchain/BRCs. The published page works without client-side JavaScript; search and copy-link controls add only a small progressive enhancement.
- Indexed commit
39a643ff148a8dcd23ec08986a8ddeb7d5713743- Upstream date
- Sep 1, 2026
- Indexed documents
- 187 BRCs across 12 domains
- Refresh model
- Automated upstream sync with a deterministic build snapshot
Keep the system open
Read, implement, test, improve.
The strongest contribution is interoperable software paired with precise feedback on the specification that enabled it.