tamper-evident history
Fact sheet version history — aigentcandor.com
Tamper-evident version history. Each row is one version of the published fact sheet for this business: the exact bytes, their fingerprint, and the record that fixes them in time.
Current version v17 · facts attested by Michael Emery on 2026-08-01 · page built 2026-08-01
No version has been anchored yet. Every row below reads timestamp pending, the badge says tamper-evident rather than notarized, and both will change by themselves on the day a version carries a transaction. We would rather publish the weaker true sentence than the stronger one we cannot show you.
| Version | Date | SHA-256 of the fact sheet | Bytes | Anchor | Status |
|---|---|---|---|---|---|
| v15 | 2026-08-01 | 4d6bc69368f4d03a7d7489729366569b19dfa917fbbfc83b637fe1eff184c717 | 14437 | not yet anchored | timestamp pending |
| v16 | 2026-08-01 | a7e507e7c02c33e772bee9b903cba41903e7aa99a25ca67245259a4f08b337ef | 14734 | not yet anchored | timestamp pending |
| v17 | 2026-08-01 | dc51dab6da725683f572312be6a8f5f2d263717eb298c026a37a72d9ee51a8a5 | 14724 | not yet anchored | timestamp pending |
What this page shows, and what it does not
What it shows: a specific sequence of bytes existed, in this operator’s possession, no later than the record that anchors it. Anyone holding a copy of the fact sheet can hash it and compare.
What it does not show: it does not verify anyone’s identity, and it does not attest that the facts inside the file are true. Identity comes from control of the domain — whoever controls aigentcandor.com publishes the file. The facts are the business’s own statement, attested by the named person on the date shown. The anchor contributes time and immutability, and nothing else.
This wording is fixed on purpose. A history that is described as more than it is becomes a liability instead of an asset, so the description does not move.
How to check it yourself
- Download the fact sheet itself:
aigentcandor.com.yaml— the exact bytes that were hashed, served unmodified. That name always resolves to the current version. Every row in the table above also links, from its byte count, to the exact bytes of that version on its own (aigentcandor.com.v17.yamlfor the current one), so a superseded version stays checkable instead of becoming a hash you have to take on trust. - Hash the file exactly as stored —
sha256sum <file>. Nothing is normalised first: no line endings changed, no trailing newline added or removed. A normalisation step would be a private convention you could not reproduce, so there isn’t one. The byte facts recorded with each version (size, byte-order mark, line endings, trailing newline) tell you whether you hold the same bytes. - Open the anchor link and read the record’s data field. It contains a short marked payload: a format identifier, the domain, the version, and the raw thirty-two bytes of the hash. Split on the first three separators from the left; what remains is the hash.
- Compare. If the two hashes match, the file you are holding is the file that was anchored at that moment. If they do not, one of them has been altered — which is the entire point of the exercise.
The full record is published as a machine-readable manifest —
aigentcandor.com.stamps.json — listing every version,
its hash, its byte facts and its anchor, so the check can be scripted rather than eyeballed.
The anchoring path has been exercised end to end on a test network: document MARKETING_NOTES_AGENT_VISIBILITY.md, hash c631e29bd59676d1…, transaction efe40ad0754a85c9… in block 212171. That was a rehearsal on a test network, not a production record, and it is listed here only because a claim about a process should come with the evidence that the process runs.
When a fact changes
The business edits its profile. Every surface — the homepage fact block, the machine-readable fact sheet, the identity card, the structured data — regenerates from that one file in a single run, and a new version appears in the table above. The old version is not deleted. A history that could be quietly rewritten would not be worth publishing.