Seal Verification Portal

Independently verify the cryptographic integrity of a Command Legacy CommandLedger™ Chain of Proof seal for an AI-assisted report. No account required.

Request Bulk Verification Package (CommandLedger Chain of Proof)

Request an offline, court-ready verification package covering a 24-hour window

▼

Submit a request for a cryptographically-signed offline verification package covering all sealed records within a specified 24-hour window. Once reviewed and approved by a Command Legacy administrator, you will receive a secure download link by email. The package includes all seal records, ledger digest, KMS key metadata, evidence files, and a self-contained browser dashboard for offline review.

Full Name *

Email Address *

Organization / Affiliation *

Position / Title *

Contact Phone Number *

Window Start — Date & Time (UTC) * Beginning of the 24-hour period you are requesting

Window End — Date & Time (UTC) * Must be within 24 hours of start time Window must be between 1 minute and 24 hours

Justification for Request *

✓ Request Submitted

Your CommandLedger Chain of Proof bulk verification request has been received. A Command Legacy administrator will review your request and, upon approval, you will receive a secure download link at the email address you provided. Allow 1–2 business days for review.

Your request reference:

—

By submitting you confirm this request is for a legitimate legal, investigative, or compliance purpose. All requests are logged and reviewed prior to package delivery.

Enter Seal Details

Seal ID

Feature

Verifying seal integrity — please wait…

Cryptographic Checks

Seal Record

Sealed Retrieval Context

The legal knowledge-graph paths consulted when this answer was generated, sealed alongside the answer. These identifiers and hashes are part of the immutable evidence record.

GPS Location

Conversation Chain

Sealed Content

Officer Query

AI Response (sealed)

How Seal Verification Works

Every AI-assisted report generated through Command Legacy is sealed with a CommandLedger™ Chain of Proof record — a tamper-evident cryptographic stamp that proves exactly what the AI said, when it was said, and which officer received it.

When you submit a Seal ID, four independent checks run against the live Command Legacy ledger. A seal is VERIFIED only when all four pass:

Chain Hash Recomputes SHA-256 over the ledger anchor fields. Any modification to the stored record breaks this hash.

KMS Signature Confirms the HMAC-SHA-256 signature was produced by our AWS KMS hardware security module — impossible to forge without the key.

S3 Evidence File Confirms the original evidence package still exists in immutable S3 Object Lock storage (7-year COMPLIANCE retention).

Content Hash Re-reads the immutable evidence file and re-hashes the original AI response text. Detects any modification to the response after sealing.

CommandLedger™ is built on a DynamoDB hash chain backed by AWS KMS HMAC signing and S3 Object Lock immutable storage. Each seal is independently verifiable by any party with the Seal ID.

Questions? Contact contactus@harborsecuritytechnologies.io