@333eco/corpus 2.3.3 → 2.3.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +6 -0
- package/dist/corpus.json +298 -152
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -33,6 +33,7 @@ So the check moves into the response:
|
|
|
33
33
|
"doi": "10.5281/zenodo.22217516",
|
|
34
34
|
"opentimestamps": true,
|
|
35
35
|
"deposited_matches_current": true,
|
|
36
|
+
"hostile_review": null,
|
|
36
37
|
"verify": {
|
|
37
38
|
"sha256": "printf '%s' \"$(cat <file>)\" | shasum -a 256 # compare to provenance.sha256",
|
|
38
39
|
"doi": "https://doi.org/10.5281/zenodo.22217516",
|
|
@@ -44,6 +45,11 @@ So the check moves into the response:
|
|
|
44
45
|
The `verify` block is an instruction, not a promise — it tells you exactly what
|
|
45
46
|
to run, so you do not have to trust this sentence either.
|
|
46
47
|
|
|
48
|
+
`hostile_review` is the date of the latest ruled review by an outside reader chosen as
|
|
49
|
+
the one most likely to find the document wrong, whose section structure still matches
|
|
50
|
+
the text served — or `null`, stated rather than omitted. It is derived from the corpus's
|
|
51
|
+
public `reviews.json` (roles only, never names), and a structural revision resets it.
|
|
52
|
+
|
|
47
53
|
⭐ **The demonstration is the contribution.** Anyone can propose provenance-carrying
|
|
48
54
|
retrieval. Serving it over a corpus where the anchors are already years deep in
|
|
49
55
|
the Bitcoin blockchain is a different claim, and it is not one that can be
|