docs: update links to current specs and mark historical docs

- update README.md to link to specs.ipfs.tech for UnixFS and Bitswap
- update README.md to link to kubo repo for implementation-specific specs
- clarify kubo-specific specs are implementation details
- add historical context notes to legacy specs from ~2015
- mark ARCHITECTURE.md as historical (from ~2015)
- fix IPNS Record Creation and Verification link

Author: lidel

ARCHITECTURE.md

@@ -1,5 +1,7 @@
 # ![](https://img.shields.io/badge/status-wip-orange.svg?style=flat-square) IPFS Architecture Overview
 
+> [!NOTE]
+> This document contains historical notes about IPFS architecture from ~2015. For current specifications, please refer to https://specs.ipfs.tech/
 
 **Authors(s)**:
 - [Juan Benet](https://github.com/jbenet)

DWEB_ADDRESSING.md

@@ -1,5 +1,8 @@
 # ![](https://img.shields.io/badge/status-wip-orange.svg?style=flat-square) Addressing on the Decentralized Web
 
+> [!NOTE]
+> This is an incomplete work-in-progress document from the early days of IPFS. For current addressing specifications, please refer to https://specs.ipfs.tech/
+
 **Authors(s)**:
 - [Lars Gierth](mailto:lgierth@ipfs.io)
 

IMPORTERS_EXPORTERS.md

@@ -1,5 +1,8 @@
 # ![](https://img.shields.io/badge/status-wip-orange.svg?style=flat-square) Data Importers & Exporters
 
+> [!NOTE]
+> This is a work-in-progress specification from the early days of IPFS. For current UnixFS and data import specifications, please refer to https://specs.ipfs.tech/unixfs/
+
 **Authors(s)**:
 - David Dias
 - Juan Benet

KEYCHAIN.md

@@ -1,5 +1,8 @@
 # ![](https://img.shields.io/badge/status-wip-orange.svg?style=flat-square) The Keychain
 
+> [!NOTE]
+> This is a work-in-progress specification from the early days of IPFS that was never completed. It remains here for historical reference.
+
 **Authors(s)**:
 - [Juan Benet](github.com/jbenet)
 

README.md

@@ -35,7 +35,7 @@ The specs contained in this and related repositories are:
 
 - **IPFS Protocol:**
   - [IPFS Guide](https://docs.ipfs.tech/) - to start your IPFS journey
-  - [Protocol Architecture Overview](./ARCHITECTURE.md) - the top-level spec and the stack
+  - [Protocol Architecture Overview (Historical Notes from ~2015)](./ARCHITECTURE.md) - the top-level spec and the stack
 - **User Interface (aka Public APIs):**
   - [HTTP Gateways](https://specs.ipfs.tech/http-gateways/) - implementation agnostic interfaces for accessing content-addressed data over HTTP
   - [Routing V1](https://specs.ipfs.tech/routing/http-routing-v1/) - implementation agnostic interfaces for content/peer/IPNS routing over HTTP
@@ -45,31 +45,31 @@ The specs contained in this and related repositories are:
   - [IPLD](https://ipld.io/specs/) - InterPlanetary Linked Data.
     - [DAG-CBOR](https://ipld.io/docs/codecs/known/dag-cbor/) -  binary format, supporting the complete IPLD Data Model, with excellent performance, and suitable for any job.
     - [DAG-JSON](https://ipld.io/docs/codecs/known/dag-json/) - human-readable format, supporting almost the complete IPLD Data Model, and very convenient for interoperability, development, and debugging.
-    - [DAG-PB](https://ipld.io/docs/codecs/known/dag-pb/) - a binary format for specific limited structures of data, which is highly used in IPFS and [UnixFS](./UNIXFS.md).
+    - [DAG-PB](https://ipld.io/docs/codecs/known/dag-pb/) - a binary format for specific limited structures of data, which is highly used in IPFS and [UnixFS](https://specs.ipfs.tech/unixfs/).
     - [CAR](https://ipld.io/specs/transport/car/) - transport format used to store content addressable objects in the form of IPLD block data as a sequence of bytes; typically as an [application/vnd.ipld.car](https://www.iana.org/assignments/media-types/application/vnd.ipld.car) file with a `.car` extension
   - Self Describing Formats ([multiformats](http://github.com/multiformats/multiformats)):
     - [multihash](https://github.com/multiformats/multihash) - self-describing hash digest format.
     - [multiaddr](https://github.com/multiformats/multiaddr) - self-describing addressing format.
     - [multicodec](https://github.com/multiformats/multicodec) - self-describing protocol/encoding streams (note: a file is a stream).
     - [multistream](https://github.com/multiformats/multistream) - multistream is a format -- or simple protocol -- for disambiguating, and layering streams. It is extremely simple.
 - **Files and Directories:**
-  - [UnixFS](./UNIXFS.md)
+  - [UnixFS](https://specs.ipfs.tech/unixfs/)
   - Related userland concepts (external docs):
     - [MFS, Mutable File System, or the Files API](https://docs.ipfs.tech/concepts/file-systems/#mutable-file-system-mfs)
 - **Storage Layer:**
   - [Pinning Service API](https://ipfs.github.io/pinning-services-api-spec/)
-  - [Repo](./REPO.md) - IPFS node local repository spec
-    - [FileSystem Repo](./REPO_FS.md) - IPFS node local repository spec
+  - [Repo](https://github.com/ipfs/kubo/blob/master/docs/specifications/repository.md) - Kubo-specific local repository implementation details
+    - [FileSystem Repo](https://github.com/ipfs/kubo/blob/master/docs/specifications/repository_fs.md) - Kubo-specific filesystem repository implementation
 - **Block Exchanges:**
-  - [Bitswap](./BITSWAP.md) - BitTorrent-inspired exchange
+  - [Bitswap](https://specs.ipfs.tech/bitswap-protocol/) - BitTorrent-inspired exchange
 - **Key Management:**
-  - [KeyStore](./KEYSTORE.md) - Key management on IPFS
+  - [KeyStore](https://github.com/ipfs/kubo/blob/master/docs/specifications/keystore.md) - Kubo-specific key management implementation
   - [KeyChain](./KEYCHAIN.md) - Distribution of cryptographic Artifacts
 - **Networking layer:**
   - [libp2p](https://github.com/libp2p/specs) - libp2p is a modular and extensible network stack, built and use by IPFS, but that it can be reused as a standalone project. Covers:
 - **Records, Naming and Record Systems:**
   - [IPNS](https://specs.ipfs.tech/ipns/) - InterPlanetary Naming System
-    - [IPNS Record Creation and Verification](https://specs.ipfs.tech/ipns/ipns-pubsub-router/)
+    - [IPNS Record Creation and Verification](https://specs.ipfs.tech/ipns/ipns-record/)
     - [IPNS over PubSub](https://specs.ipfs.tech/ipns/ipns-pubsub-router/)
   - [DNSLink](https://dnslink.dev) - mapping DNS names to IPFS content paths
   - [DNSAddr](https://github.com/multiformats/multiaddr/blob/master/protocols/DNSADDR.md) - mapping DNS names to libp2p multiaddrs