docs: lead IP records with attribution answer

registry-ips/TEMPLATE.md

@@ -0,0 +1,43 @@
+# <Registry>: <CIDR range>
+
+## Who is this IP range?
+
+**Short answer:** <Name the registry holder or protocol authority first. If unknown, say “Unknown — investigation pending.” Then state separately who routes or operates it when known.>
+
+Do not begin with CIDR mechanics, routing tables, or long background. The first answer must tell the reader whose range this is—or clearly say that detailed attribution is not yet known.
+
+- **Status:** <Researched | Partial | Placeholder>
+- **Registry:** <IANA | AFRINIC | APNIC | ARIN | LACNIC | RIPE NCC>
+- **Range:** `<network>/<prefix-length>`
+- **Registered resource holder:** <name or unknown>
+- **Observed route origin:** <ASN and name, or none/unknown>
+- **Operator:** <name or unknown>
+- **Classification:** <public unicast | special-purpose | other>
+- **Globally routed:** <yes | no | unknown>
+- **Verified:** <YYYY-MM-DD>
+
+## What is known
+
+<Verified range-level findings. Separate registration, routing, operation, and service responsibility.>
+
+## Investigated addresses
+
+<List notable exact addresses in the range and link their address records.>
+
+## What is not yet known
+
+<Explicit research gaps. Omit only when genuinely complete.>
+
+## Relationship summary
+
+| Axis | Finding |
+|---|---|
+| Registration | <finding> |
+| Registered holder | <finding> |
+| Route origin | <finding> |
+| Operator | <finding> |
+| Service | <finding> |
+
+## Sources
+
+- [Authoritative source](https://example.invalid/), checked <YYYY-MM-DD>