diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 5be5924..a575771 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -9,17 +9,24 @@
# catch-all.
#
-# WHY THESE PATHS NAME TWO OWNERS AND NOT ONE.
+# WHY THESE PATHS NAME TWO ACCOUNTS AND NOT ONE.
#
# They named only @0j0bit until 2026-09-12. That deadlocks: GitHub does not let
# anyone approve their own pull request, and the branch ruleset grants no
# bypass to administrators, so a pull request touching one of these paths and
# authored by its sole code owner could never be merged by anyone.
#
-# Both named accounts have write access, which a code owner must have to count.
-# These lines currently resolve to the same two people as the catch-all, so
-# their present effect is documentary: they record which paths are authorities.
-# If the catch-all ever widens, they narrow again on their own.
+# @0j0bit and @sed-boi are two GitHub accounts controlled by the SAME project
+# owner. Either account may satisfy the code-owner review requirement for a
+# change it did not author -- in practice, changes proposed by the
+# mcl-release-governor App and reviewed as @0j0bit. This is account redundancy,
+# NOT independent two-person review, and nothing here claims separation of
+# duties.
+#
+# Both accounts have write access, which a code owner must have to count. The
+# path lines below name the same accounts as the catch-all, so their present
+# effect is documentary: they record which paths are authorities. If the
+# catch-all ever widens, they narrow again on their own.
* @0j0bit @sed-boi
diff --git a/README.md b/README.md
index d25f0a1..88fa27e 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,46 @@
-# MCL-IP
+
+ 
+
-`mcl-ip` defines an optional IP/network binding for the Machine Contact Layer.
+MCL-IP
+
+MCL over the network you already have — UDP, TCP, or anything that moves a datagram.
+
+
+ 
+ 
+ 
+ 
+
+
+
+ Use the SDK instead ·
+ Specifications ·
+ mcl-link
+
+
+---
+
+> ### Most people should start with the SDK, not here
+>
+> This repository is a **specification**. If you are building a product, start
+> with [**mcl-sdk**](https://github.com/machine-contact-layer/mcl-sdk): its quickstart runs two machines making
+> contact, and the release ships a self-contained developer SDK — one CMake
+> project, no sibling checkout. Come back here when you need to know exactly
+> what a byte means, or when you are writing an independent implementation.
+
+## Why this exists
+
+MCL is not anti-network. When two machines can already reach each other over
+IP, that is usually the right place for the contact to live — and this binding
+is also the most common destination when a contact migrates off a slower
+bootstrap medium.
+
+If your machines are on the same network today, this plus
+[`MCL Base 1`](https://github.com/machine-contact-layer/mcl-sdk) is all you need; nothing here requires discovery,
+a microphone, or a rendezvous step.
+
+**IP-DATAGRAM profile 1 is Stable.**
MCL is not anti-network. IP is a richer transport that peers may use directly or negotiate after first contact over another binding such as MCL-AP.