Prove a change is real
Prove a change is real
See what changed on your site, then prove the record of those changes was not altered after the fact. The chain is witnessed, so the proof is yours to recompute.
What you get: every crawl stored as a witnessed record, a dated log of what changed between crawls, and a verification you can re-run that shows nothing was altered since it was witnessed. A change becomes a fact you can check, not a claim you have to trust.
Ask Quox
Section titled “Ask Quox”Start with the plain question. Ask what moved on the site:
what changed on the site
▤ AOCL │ L1 identity complete · allowed · 0ms
▤ AOCL │ L3 policy gate complete · proceed · 2ms
◐ SEO │ changes ✔ SEO │ changes │ 20 changes, 8 rollup · 2.5s
⛓ AEE │ envelope opened · stream_success
Two crawls changed things in the last few days, and they show a Brain2 to Qortex rename and a retired QuoxTerminal. The crawler classed 6 changes as improvements, 2 as regressions and 12 as neutral. Today's crawl (14 Oct, 08:22 UTC) • Three new URLs: the blog post /blog/calm-agent-safer-agent and two tag pages, /blog/tag/safety and /blog/tag/human-approval . • /blog/all meta description now says 113 articles instead of 112, which matches the new post. Crawl from 12 Oct (07:16 UTC) • Brain2 became Qortex. ◦ /solutions/brain2 was removed (flagged as a regression) and /solutions/qortex was added. ◦ /docs/plugins/qortex was added. ◦ The NotesQ page now calls itself "the notebook layer of Qortex". ◦ /solutions/contactsq is also new. • QuoxTerminal was retired. ◦ The H1 is now "QuoxTerminal is being rebuilt." and the title reads "QuoxTerminal legacy product". ◦ The meta description points people to QUOXON and QuoxCLI. ◦ The page dropped from 2,262 words to 49. ◦ The docs page was retitled "legacy documentation", but its H1 count went from 1 to 2 (the other flagged regression). Worth checking • /docs/plugins/brain2 title: it changed to "Quox · Put AI agents to work, and keep proof of everything", which is the homepage title. The word count rose from 1,652 to 2,030, so the page still has content. It's probably a template or fallback bug. • Brain2 URL redirect: the crawler lists /solutions/brain2 as removed, so I can't tell if it redirects to Qortex. If it returns a 404, you lose any inbound links to it. • Docs H1: the second H1 on the QuoxTerminal docs page is a small fix. I can have the SEO tooling check whether /solutions/brain2 redirects and look into the /docs/plugins/brain2 title.
20.3s · 1 tool · 0 approvals
quox.✔ Machine verified against the CLI on 14 Oct 2026 · test report mv8o0b
Quox read the witnessed change log from your own warehouse: the diff between consecutive crawls, each change tagged to the crawl that recorded it.
Then ask the harder question, the one that separates QuoxSEO from an ordinary SEO tool:
prove the SEO data hasn't been tampered with
▤ AOCL │ L1 identity complete · allowed · 1ms
▤ AOCL │ L3 policy gate complete · proceed · 4ms
◐ QUOX │ cli ✔ QUOX │ cli │ 0 exit code, 12576 duration ms · 14.0s
◐ WARD │ status ✔ WARD │ status │ 4360394 org entries · 14.4s
◐ SEO │ summary ✔ SEO │ summary │ 30 crawls · 16.6s
⛓ AEE │ envelope opened · stream_success
The SEO data checks out as untampered. The verification came back INTACT with all_ok: true . What I checked • I re-ran the server-side verification on the SEO chain. It recomputes three hashes for each crawl: the statement hash, the content hash and the root hash. All 93 crawls passed on all three. • The latest crawl I can see in the summary is #434, run on 14 Oct (902 URLs, 901 OK). Its root hash is 7768566921b8598b3b9c3b21cd9477049ba9d7d64824278e21a0c3dc20ff7957 , and it was witnessed at 08:22 UTC the same day. • The witness system is healthy. It has recorded 0 errors, and its last witnessing was seconds before I checked. The chain holds about 4.4M entries across 3 chains. What this proves and what it doesn't • It proves that none of the stored crawl records have changed since they were witnessed. Altering a URL row, a score or a hash would have broken one of those checks. • It doesn't prove the crawl captured the right data in the first place. It only shows nothing was altered afterwards. • The system verified itself. For independent proof, you could check a single envelope with quox governance ward verify --envelope <id> , but I don't have an envelope id for these crawls yet. Oddities I'd look at (none are signs of tampering) • The verification covers crawl #440 (ward_seq 419), which is newer than the latest crawl in the summary (#434). It's probably a crawl that wasn't shown in the summary, but I haven't confirmed that. • The WARD sequence numbers aren't strictly in order. Crawl 271 has seq 265, but crawl 278 has seq 255. Both still verify. • Some consecutive crawls share a root hash (for example #304 and #317, and #212 and #225). That fits an unchanged site. • Two crawls look like partial runs: #169 on 25 Sep with 1 URL, and #291 on 3 Oct with 500 URLs. Both verify as intact, so these are crawl quality issues, not integrity ones. I can look into the sequence ordering and crawl #440 if you want.
42.8s · 3 tools · 0 approvals
quox.✔ Machine verified against the CLI on 14 Oct 2026 · test report mv8o20
Notice what the answer does, and what it refuses to do. It proves nothing was altered after the records were witnessed. It does not claim the crawl captured the right data in the first place, it says the system verified itself, and it points at an independent check. That line is the point of the whole feature: a signature proves a record is authentic and unchanged, never that the finding was correct.
Do it yourself
Section titled “Do it yourself”The chat answer came from these commands. Run them yourself.
1. What changed
Section titled “1. What changed”quox seo changes~ /solutions/quox-security word_count: 1089 -> 1622 (crawl #564)+ /evidence/feed.jsonl (crawl #564)+ /evidence/explore (crawl #564)+ /blog/we-sent-in-the-dragons (crawl #564)~ /blog/all meta_description: "...116 in total..." -> "...117 in total..." (crawl #564)A + is a URL that appeared, a ~ is a field that changed, each tagged to the crawl that recorded it. These are signed diffs, not a live guess.
2. Prove the record was not altered
Section titled “2. Prove the record was not altered”quox seo verifychain INTACT · 112 witnessed crawls · ALL OKcrawl #1 seq 1 statement ok root okcrawl #2 seq 2 statement ok root ok...crawl #557 seq 520 statement ok root okcrawl #564 seq 527 statement ok root okcrawl #570 seq 532 statement ok root okFor every crawl this recomputes the statement hash, the content hash and the root hash, and checks each crawl’s position in the witness chain. Alter a single URL row, a score or a date in any past crawl and one of those checks breaks. chain INTACT means none of them did.
3. See the hash and chain position for a crawl
Section titled “3. See the hash and chain position for a crawl”quox seo crawls#564 2026-10-24T05:40:12Z complete 913/914 root 5ded3cd32cfe7f5a… ward seq 527#551 2026-10-23T05:49:04Z complete 909/910 root 0fa5fdce83eefcf4… ward seq 514#538 2026-10-22T05:45:55Z complete 909/910 root 0fa5fdce83eefcf4… ward seq 503The root is the crawl’s content hash and ward seq is its position in the witness chain. Two crawls sharing a root hash, like #551 and #538 above, is not a bug: it means the site did not change between them.
What just happened
Section titled “What just happened”You read your own warehouse and then re-verified it. The change log and the verification both ran against crawls your Quox stored and witnessed, with no third-party SEO service in the loop. The verification is a recomputation from the stored records, so it does not depend on taking Quox’s word for anything.
What this proves, and what it doesn’t
Section titled “What this proves, and what it doesn’t”- It proves no stored crawl record changed after it was witnessed. A silent edit to history, a quietly deleted noindex, a score nudged after the fact, breaks a hash and shows up as a failed crawl.
- It does not prove the crawl captured the right data to begin with. Verification is about integrity after the fact, not correctness at capture time.
- The system verified itself. For a check outside Quox, verify a single envelope with
quox governance ward verify, or recompute a crawl’s root hash yourself from the stored record.
Check it yourself
Section titled “Check it yourself”Each crawl’s ward seq is a position in the witness chain, so any crawl can be checked against the record independently. Check a receipt shows how. The same evidence is published and recomputable at quox.ai/evidence/explore.
Nothing to undo: every command here only reads and recomputes.