Every ArcticScore engagement produces a signed bundle whose integrity can be checked offline, without calling our servers.
verify_bundle.py and VERIFY_BUNDLE.md — a standalone, stdlib-only verifier with plain-English instructions. Anyone holding the bundle can run six verifier integrity checks offline, without contacting ArcticScore. Alteration of the delivered files, record, signature, or timestamp is detectable by the verifier.
Evidence events are linked so a later change is detectable. The exported state is signed and timestamped by an external RFC 3161 authority, and the included verifier checks that the delivered files and record still agree.
An external RFC 3161 authority timestamps the delivered record state. The included token can be checked against the authority’s public certificate, independently of ArcticScore’s system clock.
Every bundle ships with a readable verifier and plain-English instructions. It runs offline without calling ArcticScore, so a buyer or technical reviewer can inspect it and independently check the declared files, linked record, signature, and external timestamp. The result reports pass, fail, or unverified rather than silently accepting an incomplete record.
When the qualified-individual workflow is completed, a bundle can include optional certification artifacts designed to support authentication under FRE 902. The bundle states whether those artifacts are present. Admissibility is determined by the court.
Inside the record, every claim carries its verification status on its face: machine-verified against a fresh evidence pull, attested in writing, contradicted by live evidence, or not yet checked. Nothing is silently upgraded — a fix claim earns its certificate from the evidence or stays marked unverified. And the coverage map states which sources could check which claims, so a reviewer knows what the record covers before relying on it.
We’re a small company. That’s a fair concern. The bundle reduces ongoing vendor dependence by shipping the verification materials with the record:
The verifier doesn’t call us
The timestamps are third-party
The math is checkable
The verifier ships in the bundle
The bundle is yours forever
If a bundle fails verification for reasons within our control, we will correct it under the terms of the applicable agreement. The standalone verifier makes alteration to the delivered bundle detectable by checking its declared files, linked record, signature, and external timestamp. Those checks establish integrity and provenance; they do not decide whether every source assertion is true, whether the assessment scope was complete, or whether a court, carrier, or regulator will accept the result.
The shipped verifier checks the delivered record against its hashes, signatures, chain links, and timestamp token without calling ArcticScore.
See pricing