Artifact · captured 2026-10-14 09:20Z
https://tawk.to/roadmap
What was published
Tawk to https://roadmaptothesoul.tumblr.com/ https://roadmaptothesoul.tumblr.com/ Message Me Report https://roadmaptothesoul.tumblr.com/ Report https://roadmaptothesoul.tumblr.com/ Submit a report Let us know about the abuse on tawk.to and keep this a safe place for everyone. Can
Custody — each question answered separately
- Does Junctiq hold the bytes? — ProvenStored, then downloaded back and re-hashed to the recorded digest at 2026-10-14 09:20Z.
- Does the origin still serve it? — ProvenRe-checked 2026-10-15 10:20Z: HTTP 200, and the origin served these exact bytes.
- Does any public archive hold it? — UnknownNever checked for this record: no archive-availability row exists for it.
- Is it independently reproducible? — Not measurableNo instrument compares these bytes with a copy Junctiq does not control, so this is not answered either way.
- Has what the publisher served changed since? — ProvenNo. The one later capture, to 2026-10-15 10:20Z, hashed identically.
The record
- SHA-256
- 0dd197ef8c20f8525906d295dcecbfadd766556341d91ba8f2fba76a9a36ad80
- Bytes
- 5,475
- Captured
- 2026-10-14 09:20ZWhen Junctiq fetched these bytes — never the publisher’s date.
- Published
- The source did not state one.
- HTTP
- 200 · text/html
- Retention
- EXCERPT · retention-v0-2026-09-17Rule v0 is a draft (draft pending legal review). A reclassification would be a new capture under a new rule version, never an edit to this one.
Every capture of this page
Compared by digest only. “Differs” is a fact about bytes; it is not a finding that the publisher changed anything.
| Captured | HTTP | Bytes | SHA-256 | Against this one | Held |
|---|---|---|---|---|---|
| 2026-09-18 22:31Z | 200 | 5,475 | 69c2a34db461… | differs | no |
| 2026-09-18 22:47Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-09-21 10:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-09-22 11:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-09-23 12:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-09-24 14:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-09-25 15:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-09-26 16:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-09-27 17:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-09-28 18:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-09-29 19:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-09-30 20:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-10-01 21:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-10-02 22:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-10-03 23:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-10-05 00:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-10-06 01:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-10-07 02:21Z | 200 | 5,475 | 69c2a34db461… | differs | yes |
| 2026-10-08 03:20Z | 200 | 5,475 | 0dd197ef8c20… | identical | yes |
| 2026-10-09 04:20Z | 200 | 5,475 | 0dd197ef8c20… | identical | yes |
| 2026-10-10 05:20Z | 200 | 5,475 | 0dd197ef8c20… | identical | yes |
| 2026-10-11 06:20Z | 200 | 5,475 | 0dd197ef8c20… | identical | yes |
| 2026-10-12 07:20Z | 200 | 5,475 | 0dd197ef8c20… | identical | yes |
| 2026-10-13 08:20Z | 200 | 5,475 | 0dd197ef8c20… | identical | yes |
| 2026-10-14 09:20Z | 200 | 5,475 | 0dd197ef8c20… | this | yes |
| 2026-10-15 10:20Z | 200 | 5,475 | 0dd197ef8c20… | identical | yes |
Provenance
- Artifact
- Excerpt
- Claim
- Commitment
- Resolution
The chain stops at the excerpt. Extracting dated claims from an artifact, committing them and resolving them externally are not built: they wait on Kill Test 1, which is re-measured on 2026-12-16. Until then this record is custody only, and it says so rather than ending quietly where the data ends.