/demo/wikidata-demand-q131194
Eotyrannus: from a Wikidata lead to one recorded Crossref observation
Case question
Can a public Wikidata identifier be narrowed into one explicitly authorized external source observation without treating the Wikidata statement itself as evidence?
The answer in this case is yes. Wikidata supplied a useful research lead—a DOI attached to Eotyrannus. Counterpedia did not treat that DOI, or any other Wikidata relationship, as evidence. It narrowed the material into a bounded plan, required a separate owner authorization for one provider call, and recorded what Crossref returned.
1 · The information being referenced
The subject is Eotyrannus, and Wikidata carries a DOI for the paper that described it
The materialized Wikidata record identifies Q131194 as Eotyrannus, a genus of Early Cretaceous tyrannosauroids. Among the structured identifiers attached to that record is DOI 10.1006/CRES.2001.0252. That DOI identifies the 2001 paper below.
A preliminary account of a new tyrannosauroid theropod from the Wessex Formation (Early Cretaceous) of southern England
Stephen Hutt, Darren Naish, David M. Martill, Michael J. Barker, Penny Newbery
Cretaceous Research, April 2001 · volume 22, issue 2 · pages 227–242
DOI 10.1006/CRES.2001.0252 ↗2 · How Wikidata was used
Twenty-nine possible leads were reduced to six explicit investigation leads
Counterpedia did not send the Wikidata entity to an external provider wholesale. Its breadth pipeline classified the structured material, then selected a bounded six-item research snapshot. Only one of those six items—the DOI—had an executable provider route. The other five remained contextual graph leads.
29
typed leads
1
documentary identifier
1/11
routable identifier routes
5
bounded neighborhood leads
6
selected leads
1
lead allowed to execute
| Wikidata relation | Observed value | What it means here | Execution role |
|---|---|---|---|
| DOIP356 | scholarly article identifier 10.1006/CRES.2001.0252 | Wikidata carries this DOI for Eotyrannus. It was the only selected lead that had an executable provider route. | authorized Crossref resolution candidate |
| named afterP138 | dawn Q11326182 | One component of the name Eotyrannus is linked by Wikidata to “dawn.” | context only |
| named afterP138 | tyrant Q180095 | The second naming relation links Eotyrannus to “tyrant.” | context only |
| parent taxonP171 | Tyrannosauroidea Q131396 | Wikidata places Eotyrannus under the tyrannosauroid superfamily. | context only |
| time periodP2348 | Early Cretaceous Q752187 | Wikidata associates the taxon with the Early Cretaceous. | context only |
| instance ofP31 | fossil taxon Q23038290 | Wikidata classifies the subject as a fossil taxon. | context only |
3 · What Counterpedia authorized
The permission was one Crossref DOI resolution—not a general research or capture permission
The selected six-lead plan still could not execute anything by itself. A separate owner authorization bound one exact plan to one provider scope and one-call budget. In plain terms, the authorized act was:
Resolve the DOI 10.1006/CRES.2001.0252 through Crossref's native-identifier resolution capability.
- Subject
- Eotyrannus (Q131194)
- Provider
- Crossref
- Provider call budget
- 1 call
- Demand reference
demand:q131194:breadth-canary
The authorization was bound to the complete six-lead snapshot. That matters because it prevents a caller from presenting a different or shortened plan—for example, a one-line object containing only the DOI—and reusing the same grant.
Audit details: exact authorization bindings
- Plan digest
sha256:b7d43195df974b8ccc194976a6f379116a05b23fbd3453bc50b0e578908aa260- Selected-leads digest
sha256:e2b540cf4b32e876d19887519a0604e3ba3cd06d4cb5b93dd924260379dd43bb- Authorization ref
cp.gov.execution/urn:ec664b59-4cdb-4cbb-82f9-c7cd3db4ca6f
4 · What actually happened externally
Source Intelligence made one Crossref call and recorded one provider observation
On 2026-10-05, the packet-pinned operator verified the exact authorized dispatch before opening the network path. It then invoked Crossref's native DOI-resolution capability for 10.1006/CRES.2001.0252. The authorized budget was one provider call, and exactly one provider call was completed.
Operation
native DOI resolution
10.1006/CRES.2001.0252
Provider result
1 ProviderObservation
crossref-obs:resolve:10.1006/CRES.2001.0252
Candidate locator
Result 0 of the provider observation
https://doi.org/10.1006/CRES.2001.0252
Audit details: packet, provider observation, and locator
- Counterpedia producer
f7f5627b39ad30dff61bbe0471ff8e2cfd2125a6- Packet SHA-256
sha256:04d1df7970f20c2e90cf1849c4ac6f2bcf4a25f3e19af155ed2ba9d9a21b99b6- Dispatch SHA-256
sha256:62ebc1ee33a88dd91cc07c57bd20c4430d6f5b87ff51bb15340780f2e1ed8133- SI operator commit
61d4c4612bf2d71b91b1fb476cf623c5f0ba16b5- Observation digest
sha256:8d1b8165990ae8c89b90968a9ac4b1a282392d915243331f72cb3e2e71dc3ece- CandidateLocator ID
sha256:89ff904729b93a9cadade8009fbfedaaa508257fb7c4bd484d684f05a8109d29
5 · What this case establishes—and what it does not
The completed result is a governed discovery observation, not a captured source or verified claim
Established by this case
- ✓ Q131194 was narrowed into a bounded six-lead research plan.
- ✓ The DOI was the one selected lead with a Crossref execution route.
- ✓ An owner authorized exactly one Crossref provider call.
- ✓ The exact authorized packet was verified before execution.
- ✓ Crossref produced one provider observation.
- ✓ Source Intelligence created a CandidateLocator from that observation.
Not established by this case
- — No Acquisition execution occurred.
- — No source bytes were captured or retained.
- — No SourceEdition was created from this observation.
- — No Check procedure was run.
- — No proposition was judged supported or true.
- — Nothing was published as a Counterpedia evidence record.
The practical result is modest but important: Wikidata identified a promising documentary route; governance limited what could be done with it; Crossref was asked exactly once; and Counterpedia retained the provenance of what the provider returned without pretending that discovery itself was evidence.
Replay posture
This page is a static replay of accepted, secret-free facts from the completed case. Rendering it performs no provider lookup, does not consume or recreate the authorization, and cannot run Crossref again.
VERIFIED_REPLAY · network calls during demo: 0 · new authority movement: 0