TOVREK / FT-01
What a DOI metadata evidence check adds
Illustrative explanation only. No Crossref record was retrieved to create this page, no production TOVREK determination is shown, and no DOI request is sent by viewing it. Bracketed items below are placeholders, not verified fields or a claimed API response.
One supported question
Given a Crossref standard-type DOI record, does its current metadata explicitly record the requested DOI?
Example request shape:
entity = crossref:doi:<DOI>,
context = doi, with as_of omitted for current state.
The browser and HTTPS contract also support checking an exact
title predicate. The source may be unavailable or may not
contain the requested fact.
Raw Crossref record versus TOVREK determination
| Layer | What it supplies |
|---|---|
| Crossref source record | A matching DOI and supported metadata fields, such as a title when actually present. Created, deposited and indexed timestamps may be supplied by Crossref; absent fields stay absent. |
| TOVREK bounded check | For one exact supported predicate, a determination constrained by the recorded source fact, with source identity, evidence references, observation/retrieval timing, evidence strength, and explicit unresolved or conflicting details where applicable. |
| What neither establishes | A DOI or deposit timestamp alone does not prove legal force, approval, amendment of the underlying work, or the correctness of a separate downstream action. |
How to interpret the result
- Recorded fact: if the matching Crossref record explicitly contains the requested fact, the result can report source-backed support within that limited metadata scope. That is not independent corroboration.
- Unknown: if required evidence is missing or insufficient,
treat
UNKor unresolved required evidence as no positive confirmation. Do not turn missing data into a negative factual claim. - Conflict: preserve material conflicting statements rather than selecting a convenient answer.
- Time: Crossref's optional created/deposited/indexed
dates describe its metadata record. TOVREK's
observed_at,retrieved_atandresolved_atdescribe its own observation, retrieval and determination; optionalfreshness_untilis not a provider approval date.
The supported runtime is a current-state, single-DOI Crossref metadata check. Open-ended search, historical reconstruction, general AI fact verification and mutation are unsupported.
Run your own free DOI check. Read the HTTPS instructions or trust limitations. The live result, if delivered, is the evidence to inspect; this illustrative page is not evidence about any particular DOI.