Moved pages
Before 1 September 2026 this repository was a README.md and seventeen guides
in a guides/ folder. Every one of those paths is served as a redirect on this
site and is declared in
docs.manifest.json
so the documentation portal serves the same redirect.
Nothing was discarded. Each guide’s content was preserved and, in most cases, split across pages that answer one question each.
| Old path | Now |
|---|---|
/guides/market-safety | Market safety |
/guides/protocol-coverage | Coverage beyond the marketplace |
/guides/bitcoin-data-reliability | Bitcoin and Dogecoin data and fiat prices |
/guides/secure-blockchain-data-access | The public reader boundary |
/guides/marketplace-v1 | Marketplace v1 gates |
/guides/ordex-market | Ordex |
/guides/ordinals-collection-market | Collection markets |
/guides/ordinals-collection-imports | Task: add an Ordinals collection |
/guides/atomicals-and-portfolio | Atomicals and Portfolio |
/guides/portfolio-market-actions | Task: manage assets from Portfolio |
/guides/shared-collection-media | Collection media |
/guides/private-chat-verification | Private chat verification |
/guides/design-and-accessibility | Design and accessibility |
/guides/performance-and-ui-3 | Performance |
/guides/performance-and-ui-4 | Performance |
/guides/release-validation | Release evidence |
/guides/backend-operations-console | Not republished. See below |
The one page that was not republished
Section titled “The one page that was not republished”guides/backend-operations-console.md described an authenticated operations
console for platform operators. It is not part of the public product surface,
and this repository’s own contributing rules exclude operator procedures.
Removing it is not a loss of accuracy: everything in it that a public reader can act on is available in the public health contract, which is documented in full at health and readiness. Operators have their own documentation.
What else changed shape
Section titled “What else changed shape”Three pages were merged rather than moved one to one.
- The two performance guides described consecutive releases of the same work. They are one performance page with the budgets that are actually enforced, and a dated record of what each pass changed.
- Bitcoin data reliability carried two separate contracts, one for chain data and one for the fiat quote. They are now chain data and fiat prices, because they fail differently and a reader usually cares about one of them.
- The old protocol coverage guide described the in-app coverage page. That is still coverage, but the question most readers were bringing to it, “can I trade this”, is now answered by the support matrix, which did not exist before.