docs: make reference registry merge-independent

references/README.md

@@ -26,8 +26,9 @@ Every accepted profile should contain:
 
 ## Registry
 
-| Profile | Status | Ratify version | Platform version | Gate |
-|---|---|---|---|---|
+Each profile owns one entry under [`registry/`](registry/README.md). Keeping
+entries in separate files lets platform references branch from `main` and merge
+independently without competing for a shared table row.
 
 ## Lifecycle
 

references/registry/README.md

@@ -0,0 +1,11 @@
+# Reference profile registry
+
+Each accepted platform profile adds one Markdown file to this directory. The
+entry names the canonical profile, its review or endorsement status, exact
+Ratify and platform versions, and its executable gate.
+
+One file per platform is intentional: platform references can be developed,
+reviewed, and merged independently without editing a shared registry table.
+
+An entry records evidence; it does not imply that the named platform reviewed,
+approved, partnered on, or endorsed the profile unless the entry says so.