---
title: "Verify Witnessability Core 1.0 Release Integrity"
description: "Inspect original Core 1.0 files, signed indexes, checksums and the verification guide. Distinguish artifact integrity from authority and conceptual validity."
canonical: "https://witnessability.io/verify/"
representation: "Website reading format; consult linked publications for their exact status and terms."
---

[Witnessability](https://witnessability.io/) / Published records / Core 1.0

# Verify the release. Keep the scope clear.

The published verification guide describes how to check the release artifacts. A successful integrity check is a finding about those artifacts under stated trust assumptions.

Witnessability editorial explanation · 30 October 2026\
Prepared with AI assistance. [Authorship and responsibility](https://witnessability.io/about/#authorship).\
Read the linked publications for their exact definitions and status.

## Use the original verification guide

Download the published guide, checksum manifest, detached signatures and release-authority public key. Establish the key fingerprint through a trust path appropriate to your use. Downloading a key beside a file does not independently authenticate the key owner.

The release index lists 20 approved publication assets. Its checksum manifest covers the other 18 approved assets, excluding the manifest and its own signature. Preserve those scopes rather than treating every file in a directory as the release.

## Check the canonical package and signed records

The canonical Witnessability_Core_1.0_RC2_Ratification_Package_Final.zip is 237677 bytes with SHA-256 9ab6071ee53354dacf9ad7377d5a3fc75dc6a4d310a131ca2335703d35a1b541. It contains 53 regular files: 52 are covered by the internal checksum manifest; the manifest itself is the 53rd file.

The signed release index, License Grant Record and ratification attestation retain their original bytes and separate verification roles. Consult the complete release record and original external verification guide for their scopes and qualifications.

## Interpret the check narrowly

A matching digest relates bytes to a stated baseline. A valid signature relates a signed artifact to a key under the signature scheme and trust assumptions. Neither check establishes that every proposition in the conceptual document is true or independently validated.

## Sources and next steps

- [Original external verification guide](https://witnessability.io/downloads/EXTERNAL-VERIFICATION-GUIDE.md)
- [Checksum manifest](https://witnessability.io/downloads/SHA256SUMS-PUBLICATION.txt)
- [Checksum manifest signature](https://witnessability.io/downloads/SHA256SUMS-PUBLICATION.txt.asc)
- [Release-authority key](https://witnessability.io/keys/)
- [Full WCC 1.0 release record](https://witnessability.io/core/1.0/#release-record)
- [Signed release index](https://witnessability.io/downloads/RELEASE-1.0-INDEX.json)
- [Release index signature](https://witnessability.io/downloads/RELEASE-1.0-INDEX.json.asc)
- [License Grant Record](https://witnessability.io/downloads/LICENSE-GRANT-RECORD-CORE-1.0.md)
- [License Grant Record signature](https://witnessability.io/downloads/LICENSE-GRANT-RECORD-CORE-1.0.md.asc)
- [Ratification attestation](https://witnessability.io/downloads/RATIFICATION-ATTESTATION-FINAL.md)
- [Ratification signature](https://witnessability.io/downloads/RATIFICATION-ATTESTATION-FINAL.md.asc)
- [All original publication assets](https://witnessability.io/downloads/)

## What this does not claim

This page is not an independent key-identity attestation or a certification of conceptual truth. Follow the published release qualifications.