docs: lead IP records with attribution answer

registry-ips/000-000-000-000--08--iana.md

@@ -1,5 +1,9 @@
 # IANA range: 0.0.0.0/8
 
+## Who is this IP range?
+
+**Short answer:** IANA reserves this range for protocol-defined “this network” use. It is not assigned to a company, ISP, cloud provider, or ordinary network operator.
+
 - **Registry:** IANA
 - **Range:** `0.0.0.0/8`
 - **IANA name:** This network

registry-ips/001-000-000-000--16--placeholder.md

@@ -1,5 +1,9 @@
 # Placeholder: 1.0.0.0/16
 
+## Who is this IP range?
+
+**Short answer:** Detailed attribution is not known yet. IANA delegates the encompassing `1.0.0.0/8` block to APNIC, but this placeholder does not assert one registrant, route origin, or operator for the whole `1.0.0.0/16` aggregate.
+
 - **Status:** Placeholder — detailed investigation pending
 - **Coverage role:** Fills the address-space gap after `0.0.0.0/8`
 - **Range:** `1.0.0.0/16`

registry-ips/001-001-000-000--24--placeholder.md

@@ -1,5 +1,9 @@
 # Placeholder: 1.1.0.0/24
 
+## Who is this IP range?
+
+**Short answer:** Detailed attribution is not known yet. IANA delegates the encompassing `1.0.0.0/8` block to APNIC, but the exact registrant, route origin, and operator for `1.1.0.0/24` still require investigation.
+
 - **Status:** Placeholder — detailed investigation pending
 - **Coverage role:** Fills the final range immediately before `1.1.1.0/24`
 - **Range:** `1.1.0.0/24`

registry-ips/001-001-001-000--24--apnic.md

@@ -1,5 +1,9 @@
 # APNIC range: 1.1.1.0/24
 
+## Who is this IP range?
+
+**Short answer:** APNIC Research and Development is the registered resource holder; Cloudflare currently originates the route through `AS13335` and operates the documented 1.1.1.1 resolver service.
+
 - **Registry:** APNIC
 - **Range:** `1.1.1.0/24`
 - **RDAP name/type:** `APNIC-LABS` / `ASSIGNED PORTABLE`

registry-ips/README.md

@@ -43,7 +43,9 @@ This is **not yet a list of all global ranges**. The expansion plan is in [`rese
 
 ## Required contents
 
-Every range file must distinguish:
+Use [`TEMPLATE.md`](TEMPLATE.md) for every new range record. The **first section after the title must be `Who is this IP range?`** and must immediately name the registered holder/authority and operator—or explicitly say detailed attribution is unknown.
+
+Every range file must then distinguish:
 
 1. registry and registered resource holder;
 2. special-purpose classification, where applicable;

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>