build-stamp: b-39301455bb7d
built-at: 2026-09-03T21:02:58.388Z
build-sequence: 11934
current-build-sequence: 11934
site: https://qconsultai.com
verify: https://qconsultai.com/version.json
current-identity: https://qconsultai.com/freshness/current/b-39301455bb7d.txt
current-sequence-identity: https://qconsultai.com/freshness/sequence/11934.txt
bypass-cache: fetch <route>?nocache=<unique value you generate> with request header Cache-Control: no-cache (generate the value yourself; a published ?v= value is cacheable; a nonce cannot bypass deployment propagation)
convergence: require route stamp, canonical, title, and fingerprint to match a stable manifest on two consecutive fetches
cross-check: compare build-sequence here with buildSequence in version.json; a single identity file cannot detect that it is itself cached, so trust the higher sequence and refetch the lower one with a new nonce
verdict: compare build-sequence numerically; a lower number than the live identity files report means your copy is stale, regardless of what any stamped path says
sequence-lookup: /freshness/sequence/<build-sequence you hold>.txt returns current or superseded for that number; version.json sequenceIndex maps sequence to stamp
identity-paths: Only /freshness.txt, /version.json, /freshness/current/<current stamp>.txt, and /freshness/sequence/<current sequence>.txt assert currency; /freshness/<stamp>.txt is a build record and makes no currency claim, so a record left behind by an earlier deployment cannot confirm a stale copy as fresh
superseded-build-stamps: b-90764136e376 b-20c689744ca5 b-c48676983e72 b-584167035f4b
status: build record only — this file makes no currency claim; the authoritative current build is published at https://qconsultai.com/freshness.txt and https://qconsultai.com/version.json