Feed index for machines and humans
Web3 feed · updates and machine routes
Web3 feed and update index
This page ties together the dedicated web3 RSS/JSON feed, changelog, readiness registry, and builder docs so the web3 cluster is a first-class authority surface instead of a side branch.
| Route | Purpose |
|---|---|
| /web3/feed.xml | RSS feed for crypto and Web3 decision guidance and capability updates. |
| /web3/feed.json | JSON Feed for the same maintained collection. |
| /web3/feed/index.json | Machine-readable index of feed, evidence, and policy surfaces. |
| /web3/collection.json | Canonical machine-readable collection manifest, truth model, aliases, and stable endpoints. |
| /web3/changelog/ | Human-readable capability history. |
| /web3/readiness.json | Per-feature readiness registry. |
Evidence, freshness, and corrections
- Written and edited by
- Rachel Julian, founder and editor
- Last reviewed
- 2026-08-13
- Readiness rule
- Scaffold means designed, not implemented. Beta means implemented with production verification pending. Live means independently verified end to end. Source code, ABI files, endpoints, or configuration never prove production availability.
- Correction path
- Report a correction or compare the capability changelog.
Source hierarchy
- Primary standards: Protocol specifications and standards bodies define what an implementation must do.
- Security guidance: Threat-model and identity guidance define controls, failure handling, and recovery expectations.
- Deployment evidence: Independent end-to-end checks establish whether a configured production capability is live.
- Editorial judgment: I apply those sources to revenue-travel decisions and state where the evidence stops.