# Open Standards

> An independent implementation navigator for open Metanet and BSV standards. It mirrors the official BRC source, maps dependencies, and adds clearly separated implementation guidance, build paths, field recipes, and builder prompts.

## Start here

- [Implementation map](https://openstandards.cash/): Orientation, high-leverage interfaces, and ecosystem implementation resources.
- [Standards catalog](https://openstandards.cash/standards/): Searchable index of every BRC in the current official snapshot.
- [Build paths](https://openstandards.cash/paths/): Task-based standards stacks for common implementation outcomes.
- [Builder workbench](https://openstandards.cash/workbench/): Runnable reference-service recipes, code callouts, and planning prompts.
- [Relationship map](https://openstandards.cash/map/): Layered standards map and dependency context.
- [Glossary](https://openstandards.cash/glossary/): Implementer-oriented definitions with links to the relevant BRCs.

## Useful implementation pages

- [BRC-100 wallet interface](https://openstandards.cash/standards/brc-100/): Vendor-neutral application-to-wallet boundary.
- [BRC-167 CHIRP](https://openstandards.cash/standards/brc-167/): Chunked, hashed, interleaved content resolution.
- [Run your own Wallet Storage](https://openstandards.cash/workbench/wallet-storage/): Local reference Wallet Infrastructure recipe.
- [Run a reference CHIRP host](https://openstandards.cash/workbench/chirp-server/): Local filesystem complete-host recipe.

## Source and editorial policy

- [About Open Standards](https://openstandards.cash/about/): Positioning, source integrity, and editorial boundaries.
- [Official BRC repository](https://github.com/bsv-blockchain/BRCs): Authoritative proposal text, authorship, history, issues, and contribution workflow.
- [BSV TypeScript stack](https://github.com/bsv-blockchain/ts-stack): Maintained packages, reference services, examples, and conformance vectors.

The upstream BRC is authoritative. OpenStandards guidance is independent and visually separated from mirrored source text. A BRC number is not, by itself, a maturity designation; inspect status notes, normative language, implementation links, and conformance evidence before shipping.