Verification hub · sealed publication
This page carries what a stranger needs in order to check the sealed publication without trusting the issuer, the author, or this website. Each fact below is either present or marked pending. Nothing here is asserted before it is true.
Paper
JFD-WP-2026-001 — The Four Behaviors
File
The_Four_Behaviors_JFD-WP-2026-001.pdf
Extent
10 pages, 867,041 bytes
Masthead byline
K.L. Phillips
Sealed
2026-08-28
This is the digest of the sealed publication. If the file you hold does not hash to exactly this value, you are not holding the sealed publication.
c7e41389ac3439a04147d9e16654fad9573eace01d5563d6114c52d77c953342
Document control number
JFD-20260828-WP-00001
Hash rule
SHA-256 over the delivered PDF bytes verbatim. The artifact was branded before delivery and carries no line-substitution step, so it reproduces by hashing the file exactly as you received it.
Status: recomputed on this host from the delivered PDF and matched. The rail recomputes the digest on the sealing host at seal time; a mismatch between the issuer's value and the host's is recorded as a finding, not quietly corrected.
Listed rather than removed. A digest that was published and then superseded stays visible, so that anyone holding the earlier file can see why their hash does not match instead of concluding the record moved.
938c29539fb1a641090a5cb0137c02954ef4504ba4c68012ca8574d27fde65d7
Superseded before publication. The masthead logo was downscaled for file size; the content is identical. A different file is a different digest, so it was re-sealed rather than quietly reused.
e43545e70665e0b6e9b609d18268ddcb48475231f2683d30823deaecc6efc188
Pre-rebrand artifact. Its OpenTimestamps stamp is void and was discarded. A file that hashes to this is an earlier draft, not the sealed publication.
An OpenTimestamps proof shows that the digest above existed no later than the time it was stamped. It is checked against the Bitcoin blockchain and does not require this website to be online, honest, or still operating.
Proof file
/assets/ots/The_Four_Behaviors_JFD-WP-2026-001.pdf.ots (1393 bytes)
State
anchored in Bitcoin block 964455 (proof taken from the copy already served, 1393 bytes)
Calendars
alice.btc.calendar.opentimestamps.org, bob.btc.calendar.opentimestamps.org
A stamp is complete only once it is included in a Bitcoin block. This page reads that state out of the proof file itself on every build, so it cannot claim an anchor the proof does not carry.
The digest is also appended to the Matchstick ledger as its own event, signed with the published signing identity and hardware co-signed. The event is the second witness: the substrate record is the first.
Event ID
2485051
Event hash
50d78c78e1e3f9c4d5c7e30ab03b5efcb6e669a1d52dcc4acbedef8a5c6ffd5f
Sealed
2026-08-28T15:09:17Z
Signing identity
a1-ledger-ed25519, ed25519+sha256-chain-v1
Hardware co-sign
ATECC608B, A9 primary / A10 failover, via the A3 broker
None of these steps requires our cooperation. Two of them can be completed entirely offline.
STEP 1
Hash the PDF you were given and compare the result, character for character, with the digest published above. This step needs nothing but the file.
sha256sum The_Four_Behaviors_JFD-WP-2026-001.pdf
STEP 2
Check the .ots proof against the Bitcoin blockchain. It establishes that the digest existed no later than the stamped time, independently of anything this site says.
ots verify The_Four_Behaviors_JFD-WP-2026-001.pdf.ots
STEP 3
Look the event up by its identifier and confirm the digest it carries is the same digest you just recomputed. If the two disagree, the seal does not hold and the disagreement is the finding.
STEP 4
Verify the event's signature against the published signing identity, and the hardware co-signature against the chip identity recorded with it. A seal is only as good as the signature a stranger can check.
A seal fixes a file at a time and binds it to a signature. It says nothing about whether the contents are correct, and it is not an endorsement of the argument the paper makes.